Startup RC script odity

[acdingman]

Hi, all-

Thanks in advance for any help you can offer. I'm trying to get JBoss set up on a few Red Hat machines here, for development, and running into a peculiar problem. I've modifed the example jboss rc.d script such that it works on our RHEL 3 machines with our installed JVM, and "service jboss start" works just fine when run manually. "chkconfig --list jboss" also shows that jboss is configured to start in runlevels 3,4, and 5. Looking in the /etc/rc.d/rc?.d/ directories, the apropriate links are in place. However, JBoss is never running after reboot on any of the machines in question. The only entries in log files that mention JBoss are in /var/log/boot.log and /var/log/messages, and indicate sucessful startup.

There is one other java-based program on these machines, the Dantz Retrospect Client, also configured to start up under the same conditions. It always starts.

Does anyone have any idea what might be happening here, and how I can get JBoss to start on boot propperly?

Thanks for any help anyone can offer.

[jcommand]

I am having the same problem... I am running Fedora Core 2 with JBoss 3.2.5.

I can run it fine manually via ./run.sh and I see all the console messages.

If I try to run it service jboss start it seams to startup and the I check to see if its running via ps auwx|grep java and java disappears after 5 seconds.

I have a feeling it is related to the startup script and the redirecting of the output.

start)
 cd $JBOSS_HOME/bin
 if [ -z "$SUBIT" ]; then
 eval $CMD_START > ${JBOSS_CONSOLE} 2>&1 &
 else
 echo "#16:" $SUBIT "$CMD_START > ${JBOSS_CONSOLE} 2>&1 &"
 $SUBIT "$CMD_START > ${JBOSS_CONSOLE} 2>&1 &"
 fi
 ;;

From the output I get:
#16: su - jboss -c cd /usr/local/jboss/bin; /usr/local/jboss/bin/run.sh >/dev/null 2>&1 &

I think its the what is handling the quotes, but I haven't found a solution yet!

Jason

[jcommand]

well... it turned out to be a permission problem with the log folder it was own as root...

I could have sworn I chown'ed it to jboss...

Oh well hope this helps someone else out!

[jcommand]

"jcommand" wrote:
well... it turned out to be a permission problem with the log folder it was own as root...

I could have sworn I chown'ed it to jboss...

Oh well hope this helps someone else out!

and I did I though...

root@cal2 (/usr/local)# ll
total 48608
drwxr-xr-x 13 root root 4096 Jul 15 15:23 .
drwxr-xr-x 15 root root 4096 Jul 15 14:50 ..
drwxr-xr-x 2 root root 4096 Mar 11 21:33 bin
drwxr-xr-x 2 root root 4096 Mar 11 21:33 etc
drwxr-xr-x 2 root root 4096 Mar 11 21:33 games
drwxr-xr-x 2 root root 4096 Mar 11 21:33 include
lrwxrwxrwx 1 jboss jboss 11 Jul 15 10:16 jboss -> jboss-3.2.5
drwxrwxr-x 7 jboss jboss 4096 Jul 15 15:23 jboss-3.2.5
-rw-r--r-- 1 root root 49665476 Jul 14 00:24 jboss-3.2.5.tar.gz
drwxr-xr-x 2 root root 4096 Mar 11 21:33 lib
drwxr-xr-x 2 root root 4096 Mar 11 21:33 libexec
drwxr-xr-x 2 root root 4096 Mar 11 21:33 sbin
drwxr-xr-x 4 root root 4096 Jul 6 12:31 share
drwxr-xr-x 2 root root 4096 Mar 11 21:33 src
root@cal2 (/usr/local)# chown -R jboss:jboss jboss
root@cal2 (/usr/local)# ll jboss/server/default/
total 28
drwxrwxr-x 4 jboss jboss 4096 Jul 15 15:25 conf
drwxrwxr-x 3 root root 4096 Jul 15 15:25 data
drwxrwxr-x 8 jboss jboss 4096 Jul 15 15:23 deploy
drwxrwxr-x 2 jboss jboss 4096 Jul 15 15:23 lib
drwxrwxr-x 2 root root 4096 Jul 15 16:39 log
drwxrwxr-x 3 root root 4096 Jul 15 16:02 tmp
drwxrwxr-x 3 root root 4096 Jul 15 15:25 work
root@cal2 (/usr/local)#

guess chown doesn't follow symbolic links...

root@cal-bits2 (/usr/local)# chown -R jboss:jboss jboss-3.2.5
root@cal-bits2 (/usr/local)# ll jboss/server/default/
total 28
drwxrwxr-x 4 jboss jboss 4096 Jul 15 15:25 conf
drwxrwxr-x 3 jboss jboss 4096 Jul 15 15:25 data
drwxrwxr-x 8 jboss jboss 4096 Jul 15 15:23 deploy
drwxrwxr-x 2 jboss jboss 4096 Jul 15 15:23 lib
drwxrwxr-x 2 jboss jboss 4096 Jul 15 16:39 log
drwxrwxr-x 3 jboss jboss 4096 Jul 15 16:02 tmp
drwxrwxr-x 3 jboss jboss 4096 Jul 15 15:25 work
root@cal-bits2 (/usr/local)#

now it works...