[lug] SIGTERM on boot

[Zulaware]

HA HA! Some joker had set the default run level at 5 and I was expecting 
it to be 3, since there is never a console attached to this machine. The 
only reason I found out is because some file transfers had filled up the 
root directory, so a bunch of X errors started showing up in the log. I 
apparently never closely correlated the timing of the log entries, as 
the SIGTERMs I was seeing were from the shutdown process. Duh.

--M

Hugh Brown wrote:

>On Fri, 2004-05-07 at 13:14, Zulaware wrote:
>  
>
>>Hi everybody,
>>
>>I'm trying to get a RH7.3 box to start up three instances of tomcat and 
>>apache on boot  up. I've done this on several machines already, but on 
>>this particular one, all four processes seem to start up, then get a 
>>SIGTERM (according to apache/tomcat logs) and shut down. If I start them 
>>by running the /etc/rc3.d/ scripts, they all start up fine and persist, 
>>but when I reboot, there is nothing.
>>
>>Any ideas what would be terminating these or how I can track it down? 
>>There is nothing in /var/log/messages. Everything that seems pertinent 
>>in the root environment look OK
>>
>>Thanks,
>>
>>Michael Wegener
>>    
>>
>
>In addition to the logger statements, I've always add 5-10 second sleeps
>in the tomcat start up scripts so that things are truly started by the
>time they run.  You can also do a search for debug= in the server.xml
>and up the debugging output to see if you get any more useful
>information.
>
>I'd also make sure that all instances of tomcat are listening on
>different ports/interfaces.
>
>Hugh 
>
>_______________________________________________
>Web Page:  http://lug.boulder.co.us
>Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20040512/a0cb7e57/attachment.html>