tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Mixon" <>
Subject RE: Tomcat 5.0.28 hangs on boot
Date Fri, 04 Nov 2005 22:47:36 GMT

Assuming you are on some form of *nix and your script starts with something
like ...
  #! /bin/sh
... you can probably put the following statement right after it ...
  set -o xtrace 
This will trace the script to standard output.

But come to think of it, if this is at boot time it may not work - not sure
how to re-direct this to a file - unless you have one script call the other

/etc/init.d/ contents:
   /etc/init.d/ 2>&1 >/tmp/startTomcatAtBoot.log

/etc/init.d/ contents:
  #! /bin/sh
  set -o xtrace    
  ... Remainder of Tomcat startup script

Then file /tmp/startTomcatAtBoot.log should have the traced output from the
second script.

Also, if you want to resort to brute force logging, you might be able to
sprinkle a number of "touch /tmp/tomcat_step-x" statements throughout the
script that starts tomcat (where x is 1,2,3, ...). This would help you
figure out where things were going South. Not elegant but it works.

HTH - Richard

-----Original Message-----
From: Preston CRAWFORD [] 
Sent: Friday, November 04, 2005 3:20 PM
Subject: Re: Tomcat 5.0.28 hangs on boot

One more question. Is there any way for you to log out an init script like
this to see where it's getting hung up? As a java developer I'm wanting to
Log4J this. :-)


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message