From: Ernst Blofeld on
OS X 10.4 server--I've got web logs turned on, but it's not starting,
and I can't figure out why.

OS X Server includes blojsom, a Tomcat-based webapp for blogs. Launchd
is supposed to be starting it at boot; there is a
com.apple.blojsom.plist in /System/Library/LaunchDaemons (see bottom of
post). This is box-stock from the install.

/var/log/system.log and asl.log shows blojsom is not starting:

System.log:
Jan 27 11:17:59 foo launchd: com.apple.blojsom: will restart in 10
seconds
Jan 27 11:18:11 foo launchd: com.apple.blojsom: respawning too quickly!
throttling
Jan 27 11:18:11 foo launchd: com.apple.blojsom: too many failures in
succession

asl.log:
[Time 2006.01.24 22:50:41 UTC] [Facility launchd] [Sender launchd] [PID
-1] [Message com.apple.blojsom: respawning too quickly! throttling]
[Level 4] [UID -2] [GID -2] [Host

There are no obvious errors in /Library/Tomcat/logs or the blojsom
webapp logs.

What is launchd bitching about?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.apple.blojsom</string>
<key>OnDemand</key>
<false/>
<key>Program</key>
<string>/Library/Java/Home/bin/java</string>
<key>ProgramArguments</key>
<array>
<string>java</string>

<string>-Djava.endorsed.dirs=/Library/Tomcat/common/endorsed</string>
<string>-classpath</string>

<string>/Library/Java/Home/lib/tools.jar:/Library/Tomcat/bin/bootstrap.jar</string>

<string>-Dcatalina.base=/Library/Tomcat/blojsom_root</string>
<string>-Dcatalina.home=/Library/Tomcat</string>

<string>-Djava.io.tmpdir=/Library/Tomcat/blojsom_root/temp</string>
<string>org.apache.catalina.startup.Bootstrap</string>
<string>start</string>
</array>
<key>ServiceIPC</key>
<false/>
<key>UserName</key>
<string>appserver</string>
</dict>
</plist>

From: William Mitchell on
"Ernst Blofeld" <blofeld42(a)hotmail.com> writes:

> OS X 10.4 server--I've got web logs turned on, but it's not starting,
> and I can't figure out why.
>
> OS X Server includes blojsom, a Tomcat-based webapp for blogs. Launchd
> is supposed to be starting it at boot; there is a
> com.apple.blojsom.plist in /System/Library/LaunchDaemons (see bottom of
> post). This is box-stock from the install.
>
Have you tried starting it from the commandline?


--
Bill Mitchell
Dept of Mathematics, The University of Florida
PO Box 118105, Gainesville, FL 32611--8105
mitchell(a)math.ufl.edu (352) 392-0281 x284
From: Tom Harrington on
In article <1138391488.354250.117940(a)g44g2000cwa.googlegroups.com>,
"Ernst Blofeld" <blofeld42(a)hotmail.com> wrote:

> OS X 10.4 server--I've got web logs turned on, but it's not starting,
> and I can't figure out why.
>
> OS X Server includes blojsom, a Tomcat-based webapp for blogs. Launchd
> is supposed to be starting it at boot; there is a
> com.apple.blojsom.plist in /System/Library/LaunchDaemons (see bottom of
> post). This is box-stock from the install.
>
> /var/log/system.log and asl.log shows blojsom is not starting:
>
> System.log:
> Jan 27 11:17:59 foo launchd: com.apple.blojsom: will restart in 10
> seconds
> Jan 27 11:18:11 foo launchd: com.apple.blojsom: respawning too quickly!
> throttling
> Jan 27 11:18:11 foo launchd: com.apple.blojsom: too many failures in
> succession
>
> asl.log:
> [Time 2006.01.24 22:50:41 UTC] [Facility launchd] [Sender launchd] [PID
> -1] [Message com.apple.blojsom: respawning too quickly! throttling]
> [Level 4] [UID -2] [GID -2] [Host
>
> There are no obvious errors in /Library/Tomcat/logs or the blojsom
> webapp logs.
>
> What is launchd bitching about?

This kind of error indicates that the launchd configuration says that
the program should start up and keep running, but that the program is
actually exiting (almost immediately, from the look of it).

If launchd has been told that the program should keep running, it will
attempt to restart it. If the program keeps exiting, launchd will
eventually give up on it.

Your launchd plist includes this:

<key>OnDemand</key>
<false/>

It indicates that the job should be kept continuously running.

Not having used 10.4 server, I couldn't say why this is happening to you.

--
Tom "Tom" Harrington
Macaroni, Automated System Maintenance for Mac OS X.
Version 2.0: Delocalize, Repair Permissions, lots more.
See http://www.atomicbird.com/
From: Ernst Blofeld on

William Mitchell wrote:
> Have you tried starting it from the commandline?

Yes--in fact it starts up from the command line, though it does
not handle authentication to login into the blogs--the I/O for
the password prompt looks like it's going to the command line.

(I removed the "java" string on the theory that the program is already
fully specified and you don't need to provide it as a commad line
argument;
in either case the blojsom process does not start.)

foo:/System/Library/LaunchDaemons root# /Library/Java/Home/bin/java
-Djava.endorsed.dirs=/Library/Tomcat/common/endorsed -classpath
/Library/Java/Home/lib/tools.jar:/Library/Tomcat/bin/bootstrap.jar
-Dcatalina.base=/Library/Tomcat/blojsom_root
-Dcatalina.home=/Library/Tomcat
-Djava.io.tmpdir=/Library/Tomcat/blojsom_root/temp
org.apache.catalina.startup.Bootstrap start
Starting service Tomcat-Standalone
Apache Tomcat/4.1.29-LE-jdk14
Jan 27, 2006 12:45:29 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /127.0.0.1:1279
Jan 27, 2006 12:45:29 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/41
config=/Library/Tomcat/blojsom_root/conf/jk2.properties

From: Ernst Blofeld on

Ernst Blofeld wrote:
> William Mitchell wrote:
> > Have you tried starting it from the commandline?
>
> Yes--in fact it starts up from the command line,

It looks like a permissions problem on the startup--the user
specified for launchd to run the process as, appserver, exists, but
appears to not have the permissions to start the process.

<key>UserName</key>
<string>appserver</string>

 |  Next  |  Last
Pages: 1 2
Prev: Urgent Help Needed - Backslash?
Next: Wi-Fi question