Re: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem
Thanks for all the help. Finally I am able to start tomcat as a daemon by using nohup. Samy Rengasamy. -Original Message- From: Jay van der Meer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 9:25 AM To: [EMAIL PROTECTED] Subject: Re: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem We had the same problem and also tried the other suggestion for nohup, which did not work. After much tracing we found a signal was being thrown (I do not remember the number now) from the IBM JDK. The only solution we came up with was a long delay before starting tomcat. Our basic process is now: 1. In the rc3.d we run a script to do su -l tomcat -c /usr/local/sbin/tomcatrun.sh followed by a sleep 10s 2. In tomcatrun.sh we first redirect the output followed by a sleep 45s then /usr/loca/jakarta-tomcat-4.0.3/bin/catalina.sh run Hope this helps. On Monday 15 April 2002 15:31, you wrote: I had the same problem and I still have the same problem. I tried all trace/debug options Tomcat startup just aborts after echoing the classpath and catalina_home environment variables. I posted the scenario earlier and have not got a solution working for me. Samy Rengasamy. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 11:43 AM To: [EMAIL PROTECTED] Subject: Re: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem Donna, I've run into similar problems in the past when I forget that at system start time, there's usually no PATH environment variable defined, so the scripts I write tend to fail. To get more debugging information, you can put a set -x command right after the #!/whatever line you have in the /etc/init.d/tomcat script. That might help figure out what's really going on. Mark Post -Original Message- From: Donna Awald [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:58 AM To: [EMAIL PROTECTED] Subject: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem I have installed the tar version of Tomcat 4.03 and want to incorporate it in the /etc/init.d start up process. I took the skeleton script and modified it for Tomcat. I can successfully start it manually with the /etc/init.d/tomcat start command, and stop it with the /etc/init.d/tomcat stop command. I placed the appropriate links in rc3.d directory via the insserv command and the comments in the tomcat start script. When I shutdown reboot the system, the tomcat script runs but tomcat is not started. I placed many echoes throughout the script to verify the commands are being issued but the processes never start. Has anyone run across this before? I have tried the following scenarios in the startup script: startproc /tomcat/bin/startup.sh . /tomcat/bin/startup.sh /tomcat/bin/startup.sh /tomcat/bin/catalina.sh start startproc /tomcat/bin/catalina.sh start each of these worked when I issue the commands manually using /etc/init.d/tomcat start, but not during reboot time. I have SuSE Linux running on Intel platforms with the same version of Tomcat and using the equivalent one to the first one above works fine. (start_daemon instead of startproc) So, I am really perplexed as to why it is not working. Any help you could give would be greatly appreciated. Thanks, Donna Awald
Re: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem
My script is... return=$rc_done case $1 in start) . /etc/profile.d/javaprof.sh #JAVA_HOME=. nohup /usr/local/jakarta/tomcat/bin/startup.sh ;; ...working fine. nohup is right command :) WBR, Sergey
Re: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem
I am running the 2.4.7 kernel, and have the exact same problem. I think it may have something to due with being started too soon. I was going to put a sleep command in, just to see if it helped, but I haven't gotten around to it yet. Regards John Gustavson Enterprise Central Software Services (ECSS) 570 Washington Street - 2nd floor New York, New York, 10080-6802 Telephone: 1-212-647-3793 Fax: 1-212-647-3321 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Donna Awald [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:58 AM To: [EMAIL PROTECTED] Subject:SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem I have installed the tar version of Tomcat 4.03 and want to incorporate it in the /etc/init.d start up process. I took the skeleton script and modified it for Tomcat. I can successfully start it manually with the /etc/init.d/tomcat start command, and stop it with the /etc/init.d/tomcat stop command. I placed the appropriate links in rc3.d directory via the insserv command and the comments in the tomcat start script. When I shutdown reboot the system, the tomcat script runs but tomcat is not started. I placed many echoes throughout the script to verify the commands are being issued but the processes never start. Has anyone run across this before? I have tried the following scenarios in the startup script: startproc /tomcat/bin/startup.sh . /tomcat/bin/startup.sh /tomcat/bin/startup.sh /tomcat/bin/catalina.sh start startproc /tomcat/bin/catalina.sh start each of these worked when I issue the commands manually using /etc/init.d/tomcat start, but not during reboot time. I have SuSE Linux running on Intel platforms with the same version of Tomcat and using the equivalent one to the first one above works fine. (start_daemon instead of startproc) So, I am really perplexed as to why it is not working. Any help you could give would be greatly appreciated. Thanks, Donna Awald
Re: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem
Donna, I've run into similar problems in the past when I forget that at system start time, there's usually no PATH environment variable defined, so the scripts I write tend to fail. To get more debugging information, you can put a set -x command right after the #!/whatever line you have in the /etc/init.d/tomcat script. That might help figure out what's really going on. Mark Post -Original Message- From: Donna Awald [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:58 AM To: [EMAIL PROTECTED] Subject: SLES7 for S/390 and Tomcat 4.03 Automating Startup Problem I have installed the tar version of Tomcat 4.03 and want to incorporate it in the /etc/init.d start up process. I took the skeleton script and modified it for Tomcat. I can successfully start it manually with the /etc/init.d/tomcat start command, and stop it with the /etc/init.d/tomcat stop command. I placed the appropriate links in rc3.d directory via the insserv command and the comments in the tomcat start script. When I shutdown reboot the system, the tomcat script runs but tomcat is not started. I placed many echoes throughout the script to verify the commands are being issued but the processes never start. Has anyone run across this before? I have tried the following scenarios in the startup script: startproc /tomcat/bin/startup.sh . /tomcat/bin/startup.sh /tomcat/bin/startup.sh /tomcat/bin/catalina.sh start startproc /tomcat/bin/catalina.sh start each of these worked when I issue the commands manually using /etc/init.d/tomcat start, but not during reboot time. I have SuSE Linux running on Intel platforms with the same version of Tomcat and using the equivalent one to the first one above works fine. (start_daemon instead of startproc) So, I am really perplexed as to why it is not working. Any help you could give would be greatly appreciated. Thanks, Donna Awald
