Re: Stopping of tomcat failed.
Hi. >>>>>>kill `cat /usr/local/apache/httpd.pid` >>>>>>if [ -f /etc/init.d/functions ]; then >>>>>>daemon "/usr/local/tomcat/bin/shutdown.sh" >>>>>>else >>>>>>/usr/local/tomcat/bin/shutdown.sh > /dev/null >>>>>>fi The formal way of stopping apache is sending signal by 'kill' command. But, does not this way of stopping apache cause the failure of stopping tomcat ? I'm worrying that apache may stop without care about tomcat. And, is there any relation with the follows ? "A process" is apache ? >> 'hangin process' - A process which become orphon (very rare!). And joins >> under 'init' process, that becomes hard to be >killed. (I think there might be lots of nice terms to refer to these kind >processes) Yasunori Taniguchi wrote: >Hi Manivannan, > >> 'unclosed sockets' - some client application interacting with your tomcat >> forgets to close the connection. (like >browsers etc) . Or the tomcat doesnt close connection to the database. So, >this unclosed connections results in 'unclosed >sockets' > >If 'unclosed sockets' was a cause and tomcat's stop process was failed, is >there no bad influence on re-start of tomcat >and running of web applications ? > > >[EMAIL PROTECTED] wrote : >>hi Yasunori, >> welcome. >> 'unclosed sockets' - some client application interacting with your tomcat >> forgets to close the connection. (like >browsers etc) . Or the tomcat doesnt close connection to the database. So, >this unclosed connections results in 'unclosed >sockets' >> 'hangin process' - A process which become orphon (very rare!). And joins >> under 'init' process, that becomes hard to be >killed. (I think there might be lots of nice terms to refer to these kind >processes) >> >> >>-- >>Manivannan Palanichamy >>http://geocities.com/manivannan57 >> >> >> >> >> >> >>-Original Message- >>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>To: Tomcat Users List >>Sent: Tue, 18 Apr 2006 10:00:06 +0900 >>Subject: Re: Stopping of tomcat failed. >> >> >>[EMAIL PROTECTED] wrote: >>>yes, the 'unclosed sockets', 'hanging process' and the likes are some >>>notable >>root causes. >> >>Sorry. I don't know about 'unclosed sockets', 'hanging process'. >>Are they bugs ? >>Please tell me the informations about them. >> >> >>[EMAIL PROTECTED] wrote: >>>yes, the 'unclosed sockets', 'hanging process' and the likes are some >>>notable >>root causes. >>> >>>-- >>>Manivannan Palanichamy >>>http://geocities.com/manivannan57 >>> >>> >>> >>> >>> >>> >>>-Original Message- >>>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>>To: Tomcat Users List >>>Sent: Mon, 17 Apr 2006 20:27:38 +0900 >>>Subject: Re: Stopping of tomcat failed. >>> >>> >>>Thanks for your reply ! >>> >>>[EMAIL PROTECTED] wrote: >>>>I understand your problem. This happens sometimes. Instead of runnign >>>shutdown.sh, you can manually kill the tomcat >>>instance using the following steps: >>> >>>What is the cause of this problem's ? >>>And. >>>Is there any bad influences ? >>>For example, garbage file or process is left, etc. >>> >>> >>>[EMAIL PROTECTED] wrote: >>>>I understand your problem. This happens sometimes. Instead of runnign >>>shutdown.sh, you can manually kill the tomcat >>>instance using the following steps: >>>>1. type this command: ps -ax | grep 'endorse'[an ugly way of >>>finding the tomcat process! ] >>>> and find out its process id. (For example the Pid: 3435) >>>>2. then kill the pid using kill command like: kill -9 3435 >>>>(where 3435 is your tomcat instance process id.) >>>> >>>>Then, telnet to the tomcat port, sure, it wont reply. This is how it can be >>>shutdown indirectly. >>>> >>>>(If still not working, the worst solution is to restart you machine.) >>>> >>>>Good luck/ >>>> >>>> >>>> >>>>-- >>>
Re: Stopping of tomcat failed.
Hi Manivannan, > 'unclosed sockets' - some client application interacting with your tomcat > forgets to close the connection. (like browsers etc) . Or the tomcat doesnt close connection to the database. So, this unclosed connections results in 'unclosed sockets' If 'unclosed sockets' was a cause and tomcat's stop process was failed, is there no bad influence on re-start of tomcat and running of web applications ? [EMAIL PROTECTED] wrote : >hi Yasunori, > welcome. > 'unclosed sockets' - some client application interacting with your tomcat > forgets to close the connection. (like browsers etc) . Or the tomcat doesnt close connection to the database. So, this unclosed connections results in 'unclosed sockets' > 'hangin process' - A process which become orphon (very rare!). And joins > under 'init' process, that becomes hard to be killed. (I think there might be lots of nice terms to refer to these kind processes) > > >-- >Manivannan Palanichamy >http://geocities.com/manivannan57 > > > > > > >-Original Message- >From: Yasunori Taniguchi <[EMAIL PROTECTED]> >To: Tomcat Users List >Sent: Tue, 18 Apr 2006 10:00:06 +0900 >Subject: Re: Stopping of tomcat failed. > > >[EMAIL PROTECTED] wrote: >>yes, the 'unclosed sockets', 'hanging process' and the likes are some notable >root causes. > >Sorry. I don't know about 'unclosed sockets', 'hanging process'. >Are they bugs ? >Please tell me the informations about them. > > >[EMAIL PROTECTED] wrote: >>yes, the 'unclosed sockets', 'hanging process' and the likes are some notable >root causes. >> >>-- >>Manivannan Palanichamy >>http://geocities.com/manivannan57 >> >> >> >> >> >> >>-Original Message- >>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>To: Tomcat Users List >>Sent: Mon, 17 Apr 2006 20:27:38 +0900 >>Subject: Re: Stopping of tomcat failed. >> >> >>Thanks for your reply ! >> >>[EMAIL PROTECTED] wrote: >>>I understand your problem. This happens sometimes. Instead of runnign >>shutdown.sh, you can manually kill the tomcat >>instance using the following steps: >> >>What is the cause of this problem's ? >>And. >>Is there any bad influences ? >>For example, garbage file or process is left, etc. >> >> >>[EMAIL PROTECTED] wrote: >>>I understand your problem. This happens sometimes. Instead of runnign >>shutdown.sh, you can manually kill the tomcat >>instance using the following steps: >>>1. type this command: ps -ax | grep 'endorse'[an ugly way of >>finding the tomcat process! ] >>> and find out its process id. (For example the Pid: 3435) >>>2. then kill the pid using kill command like: kill -9 3435 >>>(where 3435 is your tomcat instance process id.) >>> >>>Then, telnet to the tomcat port, sure, it wont reply. This is how it can be >>shutdown indirectly. >>> >>>(If still not working, the worst solution is to restart you machine.) >>> >>>Good luck/ >>> >>> >>> >>>-- >>>Manivannan Palanichamy >>>http://geocities.com/manivannan57 >>> >>> >>> >>> >>> >>> >>>-Original Message- >>>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>>To: Tomcat Users List >>>Sent: Mon, 17 Apr 2006 19:48:35 +0900 >>>Subject: Re: Stopping of tomcat failed. >>> >>> >>>[EMAIL PROTECTED] さんは書きました: >>>>Are you running apache along with tomcat? >>>>(I mean apache on port 80 and tomcat on 8080) ? >>> >>>I'm running apache on port 13000. >>>Is there a setting of port for tomcat ? >>> >>>I can use web application on port 13000. >>>I think it means apache and tomcat are running correctly. >>> >>> >>>> >>>>-- >>>>Manivannan Palanichamy >>>>http://geocities.com/manivannan57 >>>> >>>> >>>> >>>> >>>> >>>> >>>>-Original Message- >>>>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>>>To: Tomcat Users List >>>>Sent: Mon, 17 Apr 2006 13:05:24 +0900 >>>>Subject: Re: Stopping of tomcat failed. >>>> >>>> >>>>Hi. >>>>
Re: Stopping of tomcat failed.
[EMAIL PROTECTED] wrote: >yes, the 'unclosed sockets', 'hanging process' and the likes are some notable >root causes. Sorry. I don't know about 'unclosed sockets', 'hanging process'. Are they bugs ? Please tell me the informations about them. [EMAIL PROTECTED] wrote: >yes, the 'unclosed sockets', 'hanging process' and the likes are some notable >root causes. > >-- >Manivannan Palanichamy >http://geocities.com/manivannan57 > > > > > > >-Original Message- >From: Yasunori Taniguchi <[EMAIL PROTECTED]> >To: Tomcat Users List >Sent: Mon, 17 Apr 2006 20:27:38 +0900 >Subject: Re: Stopping of tomcat failed. > > >Thanks for your reply ! > >[EMAIL PROTECTED] wrote: >>I understand your problem. This happens sometimes. Instead of runnign >shutdown.sh, you can manually kill the tomcat >instance using the following steps: > >What is the cause of this problem's ? >And. >Is there any bad influences ? >For example, garbage file or process is left, etc. > > >[EMAIL PROTECTED] wrote: >>I understand your problem. This happens sometimes. Instead of runnign >shutdown.sh, you can manually kill the tomcat >instance using the following steps: >>1. type this command: ps -ax | grep 'endorse'[an ugly way of >finding the tomcat process! ] >> and find out its process id. (For example the Pid: 3435) >>2. then kill the pid using kill command like: kill -9 3435 >>(where 3435 is your tomcat instance process id.) >> >>Then, telnet to the tomcat port, sure, it wont reply. This is how it can be >shutdown indirectly. >> >>(If still not working, the worst solution is to restart you machine.) >> >>Good luck/ >> >> >> >>-- >>Manivannan Palanichamy >>http://geocities.com/manivannan57 >> >> >> >> >> >> >>-Original Message- >>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>To: Tomcat Users List >>Sent: Mon, 17 Apr 2006 19:48:35 +0900 >>Subject: Re: Stopping of tomcat failed. >> >> >>[EMAIL PROTECTED] さんは書きました: >>>Are you running apache along with tomcat? >>>(I mean apache on port 80 and tomcat on 8080) ? >> >>I'm running apache on port 13000. >>Is there a setting of port for tomcat ? >> >>I can use web application on port 13000. >>I think it means apache and tomcat are running correctly. >> >> >>> >>>-- >>>Manivannan Palanichamy >>>http://geocities.com/manivannan57 >>> >>> >>> >>> >>> >>> >>>-Original Message- >>>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>>To: Tomcat Users List >>>Sent: Mon, 17 Apr 2006 13:05:24 +0900 >>>Subject: Re: Stopping of tomcat failed. >>> >>> >>>Hi. >>> >>>I want help about the following matter. >>> >>>I got an information that : >>> Apache was killed. This is the correct operation for apache. >>> According to the following matter, tomcat was communicating with apache, >>> and probably any web application process was executing. >>> >>>Is it really ? >>>If there is no web application executing, the following matter never happen ? >>> >>> >>>Yasunori Taniguchi さんは書きました: >>>>Hi. >>>> >>>>Please help me. >>>> >>>>I'm using apache and tomcat to use Web-based GUI tool on RHEL3.0. >>>>The GUI tool has a shell script that starts/stops apache and tomcat. >>>>This script with stop option displayed message "[FAILED]". >>>>It means that stopping of tomcat has been failed. >>>>But the tomcat was disappeared in the process list. And re-execution of >>>>stop >>>was >>>>failed as same as the execution of stop after succeeded-stop. (The messages >>>output >>>>to catalina.out is tha same.) >>>>Then GUI tool was not used at that time. >>>>In the script, all the messages were discarded to /dev/null, and nothing >>>related >>>>message was output to /var/log/messages or catalina.out. >>>>So, I want to know : >>>>1. Did tomcat stopped clearly ? >>>> For example, are there any possibilities that tomcat leave garbage of >files >> >>>? >>>> Restart of tomcat was succeeded. Does it mean that tomcat has stopped >>>clearly ? >
Re: Stopping of tomcat failed.
Thanks for your reply ! [EMAIL PROTECTED] wrote: >I understand your problem. This happens sometimes. Instead of runnign >shutdown.sh, you can manually kill the tomcat instance using the following steps: What is the cause of this problem's ? And. Is there any bad influences ? For example, garbage file or process is left, etc. [EMAIL PROTECTED] wrote: >I understand your problem. This happens sometimes. Instead of runnign >shutdown.sh, you can manually kill the tomcat instance using the following steps: >1. type this command: ps -ax | grep 'endorse'[an ugly way of >finding the tomcat process! ] > and find out its process id. (For example the Pid: 3435) >2. then kill the pid using kill command like: kill -9 3435 >(where 3435 is your tomcat instance process id.) > >Then, telnet to the tomcat port, sure, it wont reply. This is how it can be >shutdown indirectly. > >(If still not working, the worst solution is to restart you machine.) > >Good luck/ > > > >-- >Manivannan Palanichamy >http://geocities.com/manivannan57 > > > > > > >-Original Message- >From: Yasunori Taniguchi <[EMAIL PROTECTED]> >To: Tomcat Users List >Sent: Mon, 17 Apr 2006 19:48:35 +0900 >Subject: Re: Stopping of tomcat failed. > > >[EMAIL PROTECTED] さんは書きました: >>Are you running apache along with tomcat? >>(I mean apache on port 80 and tomcat on 8080) ? > >I'm running apache on port 13000. >Is there a setting of port for tomcat ? > >I can use web application on port 13000. >I think it means apache and tomcat are running correctly. > > >> >>-- >>Manivannan Palanichamy >>http://geocities.com/manivannan57 >> >> >> >> >> >> >>-Original Message- >>From: Yasunori Taniguchi <[EMAIL PROTECTED]> >>To: Tomcat Users List >>Sent: Mon, 17 Apr 2006 13:05:24 +0900 >>Subject: Re: Stopping of tomcat failed. >> >> >>Hi. >> >>I want help about the following matter. >> >>I got an information that : >> Apache was killed. This is the correct operation for apache. >> According to the following matter, tomcat was communicating with apache, >> and probably any web application process was executing. >> >>Is it really ? >>If there is no web application executing, the following matter never happen ? >> >> >>Yasunori Taniguchi さんは書きました: >>>Hi. >>> >>>Please help me. >>> >>>I'm using apache and tomcat to use Web-based GUI tool on RHEL3.0. >>>The GUI tool has a shell script that starts/stops apache and tomcat. >>>This script with stop option displayed message "[FAILED]". >>>It means that stopping of tomcat has been failed. >>>But the tomcat was disappeared in the process list. And re-execution of stop >>was >>>failed as same as the execution of stop after succeeded-stop. (The messages >>output >>>to catalina.out is tha same.) >>>Then GUI tool was not used at that time. >>>In the script, all the messages were discarded to /dev/null, and nothing >>related >>>message was output to /var/log/messages or catalina.out. >>>So, I want to know : >>>1. Did tomcat stopped clearly ? >>> For example, are there any possibilities that tomcat leave garbage of >>> files > >>? >>> Restart of tomcat was succeeded. Does it mean that tomcat has stopped >>clearly ? >>>2. What kind of error is guessed ? >>> >>>--- >>>#!/bin/sh >>># >>># Startup script >>># >>># chkconfig: 345 80 15 >>># description: >>># >>> >>>### BEGIN INIT INFO >>># Provides: test >>># Required-Start: $network $remote_fs >>># Required-Stop: >>># Default-Start: 3 5 >>># Default-Stop: 0 1 2 6 >>># Description:Start the gui daemon >>>### END INIT INFO >>> >>># Shell functions sourced from /etc/rc.status: >>># rc_check check and set local and overall rc status >>># rc_statuscheck and set local and overall rc status >>># rc_status -v ditto but be verbose in local rc status >>># rc_status -v -r ditto and clear the local rc status >>># rc_failedset local and overall rc status to failed >>># rc_failed set local and overall rc status to >>># rc_reset clear local rc status (overall rem
Re: Stopping of tomcat failed.
[EMAIL PROTECTED] さんは書きました: >Are you running apache along with tomcat? >(I mean apache on port 80 and tomcat on 8080) ? I'm running apache on port 13000. Is there a setting of port for tomcat ? I can use web application on port 13000. I think it means apache and tomcat are running correctly. > >-- >Manivannan Palanichamy >http://geocities.com/manivannan57 > > > > > > >-Original Message- >From: Yasunori Taniguchi <[EMAIL PROTECTED]> >To: Tomcat Users List >Sent: Mon, 17 Apr 2006 13:05:24 +0900 >Subject: Re: Stopping of tomcat failed. > > >Hi. > >I want help about the following matter. > >I got an information that : > Apache was killed. This is the correct operation for apache. > According to the following matter, tomcat was communicating with apache, > and probably any web application process was executing. > >Is it really ? >If there is no web application executing, the following matter never happen ? > > >Yasunori Taniguchi さんは書きました: >>Hi. >> >>Please help me. >> >>I'm using apache and tomcat to use Web-based GUI tool on RHEL3.0. >>The GUI tool has a shell script that starts/stops apache and tomcat. >>This script with stop option displayed message "[FAILED]". >>It means that stopping of tomcat has been failed. >>But the tomcat was disappeared in the process list. And re-execution of stop >was >>failed as same as the execution of stop after succeeded-stop. (The messages >output >>to catalina.out is tha same.) >>Then GUI tool was not used at that time. >>In the script, all the messages were discarded to /dev/null, and nothing >related >>message was output to /var/log/messages or catalina.out. >>So, I want to know : >>1. Did tomcat stopped clearly ? >> For example, are there any possibilities that tomcat leave garbage of >> files >? >> Restart of tomcat was succeeded. Does it mean that tomcat has stopped >clearly ? >>2. What kind of error is guessed ? >> >>--- >>#!/bin/sh >># >># Startup script >># >># chkconfig: 345 80 15 >># description: >># >> >>### BEGIN INIT INFO >># Provides: test >># Required-Start: $network $remote_fs >># Required-Stop: >># Default-Start: 3 5 >># Default-Stop: 0 1 2 6 >># Description:Start the gui daemon >>### END INIT INFO >> >># Shell functions sourced from /etc/rc.status: >># rc_check check and set local and overall rc status >># rc_statuscheck and set local and overall rc status >># rc_status -v ditto but be verbose in local rc status >># rc_status -v -r ditto and clear the local rc status >># rc_failedset local and overall rc status to failed >># rc_failed set local and overall rc status to >># rc_reset clear local rc status (overall remains) >># rc_exit exit appropriate to overall rc status >>cd / >> >>if [ -f /etc/rc.status ]; then >>. /etc/rc.status >>fi >>if [ -f /etc/init.d/functions ]; then >>. /etc/init.d/functions >>fi >> >>if [ -f /etc/rc.status ]; then >># First reset status of this service >>rc_reset >>fi >> >>case "$1" in >>'start') >>echo -n "Starting the service " >>if [ -f /etc/init.d/functions ]; then >>daemon "/usr/local/tomcat/bin/startup.sh" >>/opt/FJSVihs/bin/httpd -f /usr/local/apache/conf/httpd.conf 2> >/dev/null >>else >>/usr/local/tomcat/bin/startup.sh > /dev/null >>/opt/FJSVihs/bin/httpd -f /usr/local/apache/conf/httpd.conf 2> >/dev/null >>fi >>if [ -f /etc/rc.status ]; then >>rc_status -v >>fi >>if [ -f /etc/init.d/functions ]; then >>touch /var/lock/subsys/test >>echo >>fi >>;; >>'stop') >>echo -n "Stopping service." >>kill `cat /usr/local/apache/httpd.pid` >>if [ -f /etc/init.d/functions ]; then >>daemon "/usr/local/tomcat/bin/shutdown.sh" >>else >>/usr/local/tomcat/bin/shutdown.sh > /dev/null >>fi >>if [ -f /etc/rc.status ]; then >>rc_status -v >>fi >>if [ -f /etc/init.d/functions ]; then >>rm -f /var/lock/subsys/test >>echo >>fi >>;; >>'
Re: Stopping of tomcat failed.
Hi.
I want help about the following matter.
I got an information that :
Apache was killed. This is the correct operation for apache.
According to the following matter, tomcat was communicating with apache,
and probably any web application process was executing.
Is it really ?
If there is no web application executing, the following matter never happen ?
Yasunori Taniguchi さんは書きました:
>Hi.
>
>Please help me.
>
>I'm using apache and tomcat to use Web-based GUI tool on RHEL3.0.
>The GUI tool has a shell script that starts/stops apache and tomcat.
>This script with stop option displayed message "[FAILED]".
>It means that stopping of tomcat has been failed.
>But the tomcat was disappeared in the process list. And re-execution of stop
>was
>failed as same as the execution of stop after succeeded-stop. (The messages
>output
>to catalina.out is tha same.)
>Then GUI tool was not used at that time.
>In the script, all the messages were discarded to /dev/null, and nothing
>related
>message was output to /var/log/messages or catalina.out.
>So, I want to know :
>1. Did tomcat stopped clearly ?
> For example, are there any possibilities that tomcat leave garbage of files
> ?
> Restart of tomcat was succeeded. Does it mean that tomcat has stopped
> clearly ?
>2. What kind of error is guessed ?
>
>---
>#!/bin/sh
>#
># Startup script
>#
># chkconfig: 345 80 15
># description:
>#
>
>### BEGIN INIT INFO
># Provides: test
># Required-Start: $network $remote_fs
># Required-Stop:
># Default-Start: 3 5
># Default-Stop: 0 1 2 6
># Description:Start the gui daemon
>### END INIT INFO
>
># Shell functions sourced from /etc/rc.status:
># rc_check check and set local and overall rc status
># rc_statuscheck and set local and overall rc status
># rc_status -v ditto but be verbose in local rc status
># rc_status -v -r ditto and clear the local rc status
># rc_failedset local and overall rc status to failed
># rc_failed set local and overall rc status to
># rc_reset clear local rc status (overall remains)
># rc_exit exit appropriate to overall rc status
>cd /
>
>if [ -f /etc/rc.status ]; then
>. /etc/rc.status
>fi
>if [ -f /etc/init.d/functions ]; then
>. /etc/init.d/functions
>fi
>
>if [ -f /etc/rc.status ]; then
># First reset status of this service
>rc_reset
>fi
>
>case "$1" in
>'start')
>echo -n "Starting the service "
>if [ -f /etc/init.d/functions ]; then
>daemon "/usr/local/tomcat/bin/startup.sh"
>/opt/FJSVihs/bin/httpd -f /usr/local/apache/conf/httpd.conf 2>
> /dev/null
>else
>/usr/local/tomcat/bin/startup.sh > /dev/null
>/opt/FJSVihs/bin/httpd -f /usr/local/apache/conf/httpd.conf 2>
> /dev/null
>fi
>if [ -f /etc/rc.status ]; then
>rc_status -v
>fi
>if [ -f /etc/init.d/functions ]; then
>touch /var/lock/subsys/test
>echo
>fi
>;;
>'stop')
>echo -n "Stopping service."
>kill `cat /usr/local/apache/httpd.pid`
>if [ -f /etc/init.d/functions ]; then
>daemon "/usr/local/tomcat/bin/shutdown.sh"
>else
>/usr/local/tomcat/bin/shutdown.sh > /dev/null
>fi
>if [ -f /etc/rc.status ]; then
>rc_status -v
>fi
>if [ -f /etc/init.d/functions ]; then
>rm -f /var/lock/subsys/test
>echo
>fi
>;;
>'restart')
>$0 stop
>$0 start
>if [ -f /etc/rc.status ]; then
>rc_status
>fi
>;;
>'status')
>if [ -f /etc/rc.status ]; then
> echo -n "Checking: "
>if [ -f /usr/local/apache/httpd.pid ]; then
>rc_failed 0
>rc_status -v
>exit 0
>else
>rc_failed 3
>rc_status -v
>exit 3
>fi
>fi
>;;
>*)
>echo "Usage: $0 {start|stop|restart|status}"
>;;
>esac
>exit 0
>
>Regards
>Taniguchi
>
>--
>Open Source Software Database Prj. Middleware Platform Div.
>Software Unit, Fujitsu Limited
>Yasunori Taniguchi
>e-mail : [EMAIL PROTECTED]
>
>office layout was changed in 26th Sep., and phone number was changed
>phone:+81-78-304-0563 ext.:7773-5431
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
from : [EMAIL PROTECTED] (MWPF2開発)
address : [EMAIL PROTECTED]
TEL:7773-5431 (078-304-0563)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Stopping of tomcat failed.
Hi.
Please help me.
I'm using apache and tomcat to use Web-based GUI tool on RHEL3.0.
The GUI tool has a shell script that starts/stops apache and tomcat.
This script with stop option displayed message "[FAILED]".
It means that stopping of tomcat has been failed.
But the tomcat was disappeared in the process list. And re-execution of stop was
failed as same as the execution of stop after succeeded-stop. (The messages
output
to catalina.out is tha same.)
Then GUI tool was not used at that time.
In the script, all the messages were discarded to /dev/null, and nothing related
message was output to /var/log/messages or catalina.out.
So, I want to know :
1. Did tomcat stopped clearly ?
For example, are there any possibilities that tomcat leave garbage of files ?
Restart of tomcat was succeeded. Does it mean that tomcat has stopped
clearly ?
2. What kind of error is guessed ?
---
#!/bin/sh
#
# Startup script
#
# chkconfig: 345 80 15
# description:
#
### BEGIN INIT INFO
# Provides: test
# Required-Start: $network $remote_fs
# Required-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description:Start the gui daemon
### END INIT INFO
# Shell functions sourced from /etc/rc.status:
# rc_check check and set local and overall rc status
# rc_statuscheck and set local and overall rc status
# rc_status -v ditto but be verbose in local rc status
# rc_status -v -r ditto and clear the local rc status
# rc_failedset local and overall rc status to failed
# rc_failed set local and overall rc status to
# rc_reset clear local rc status (overall remains)
# rc_exit exit appropriate to overall rc status
cd /
if [ -f /etc/rc.status ]; then
. /etc/rc.status
fi
if [ -f /etc/init.d/functions ]; then
. /etc/init.d/functions
fi
if [ -f /etc/rc.status ]; then
# First reset status of this service
rc_reset
fi
case "$1" in
'start')
echo -n "Starting the service "
if [ -f /etc/init.d/functions ]; then
daemon "/usr/local/tomcat/bin/startup.sh"
/opt/FJSVihs/bin/httpd -f /usr/local/apache/conf/httpd.conf 2> /dev/null
else
/usr/local/tomcat/bin/startup.sh > /dev/null
/opt/FJSVihs/bin/httpd -f /usr/local/apache/conf/httpd.conf 2> /dev/null
fi
if [ -f /etc/rc.status ]; then
rc_status -v
fi
if [ -f /etc/init.d/functions ]; then
touch /var/lock/subsys/test
echo
fi
;;
'stop')
echo -n "Stopping service."
kill `cat /usr/local/apache/httpd.pid`
if [ -f /etc/init.d/functions ]; then
daemon "/usr/local/tomcat/bin/shutdown.sh"
else
/usr/local/tomcat/bin/shutdown.sh > /dev/null
fi
if [ -f /etc/rc.status ]; then
rc_status -v
fi
if [ -f /etc/init.d/functions ]; then
rm -f /var/lock/subsys/test
echo
fi
;;
'restart')
$0 stop
$0 start
if [ -f /etc/rc.status ]; then
rc_status
fi
;;
'status')
if [ -f /etc/rc.status ]; then
echo -n "Checking: "
if [ -f /usr/local/apache/httpd.pid ]; then
rc_failed 0
rc_status -v
exit 0
else
rc_failed 3
rc_status -v
exit 3
fi
fi
;;
*)
echo "Usage: $0 {start|stop|restart|status}"
;;
esac
exit 0
Regards
Taniguchi
--
Open Source Software Database Prj. Middleware Platform Div.
Software Unit, Fujitsu Limited
Yasunori Taniguchi
e-mail : [EMAIL PROTECTED]
office layout was changed in 26th Sep., and phone number was changed
phone:+81-78-304-0563 ext.:7773-5431
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
