pid file not working???
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
pid file not working???
by Dean Hiller
::
Rate this Message:
I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun. when I run
./tomcat start (tomcat was the wrappertest file) my tomcat starts fine but then when running ./tomcat status it says the pid file is stale yet my wrapper and tomcat are running(and if I kill tomcat, the wrapper restarts it). ie. my status and stop commands completely don't work because of some pid problem. Here is data from my last run... pid file 4013 Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no 4013 exists...that must have been the shell file pid or something). root@builddragon:/opt/tomcat/ wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat
root 4015 1 0 22:18 ? 00:00:00 /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status root 4017 4015 6 22:18 ? 00:00:29 /opt/jdk/bin/java -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat -Djava.io.tmpdir=/opt/tomcat/temp -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib -classpath /opt/ tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=4013 -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperStartStopApp org.apache.catalina.startup.Bootstrap 1 start org.apache.catalina.startup.Bootstrap TRUE 1 stop root 4296 27756 0 22:26 pts/0 00:00:00 grep tomcat NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes the pid file which is wrong. When I kill tomcat, wrapper still starts it up fine but the pid file is all wrong. Also, the 4017 command above seems odd to me as it passes in all 7 arguments but the WrapperStartStopApp is supposed to only pass in the 2 start args and the 3 stop args I would think into the tomcat bootstrap process? anyone have any idea what is going on? thanks, Dean ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Wrapper-user mailing list Wrapper-user@... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
|
Re: pid file not working???
by Leif Mortenson-2
::
Rate this Message:
Dean,
The PID file should be getting written by the shell script that ships with the Wrapper. Could you please confirm that you are using our script? Most likely you are. 1) When you first start out, please confirm that no pid file, wrapper process, or java process are running. 2) run the script with the "console" command. This should launch the Wrapper, and Java. 3) There should now be a PID file containing the Wrapper's PID. Please confirm the id in the PID file, and also print out a "ps -faux". 4) Does the PID in the file match that of the Wrapper? If not, please send me your shell script and wrapper.conf file as attachments. Also please send me the name of your OS and version. I should be able to find the problem from that. > Also, the 4017 command above seems odd > to me as it passes in all 7 arguments but the WrapperStartStopApp is > supposed to only pass in the 2 start args and the 3 stop args I would think > into the tomcat bootstrap process? This is actually working correctly. The Wrapper is actually launching the WrapperStartStopApp class, not the Bootstrap class. The WrapperStartStopApp class is responsible for running the startup and stop classes with their parameters at the appropriate times. This looks like you have set it up correctly: org.tanukisoftware.wrapper.WrapperStartStopApp org.apache.catalina.startup.Bootstrap 1 start org.apache.catalina.startup.Bootstrap TRUE 1 stop Cheers, Leif On Thu, Oct 29, 2009 at 11:43 PM, Dean Hiller <dean@...> wrote: > I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun. when I run > ./tomcat start (tomcat was the wrappertest file) > my tomcat starts fine but then when running > ./tomcat status > it says the pid file is stale yet my wrapper and tomcat are running(and if I > kill tomcat, the wrapper restarts it). ie. my status and stop commands > completely don't work because of some pid problem. > > Here is data from my last run... > > pid file 4013 > > Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no 4013 > exists...that must have been the shell file pid or something). > > root@builddragon:/opt/tomcat/ > wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat > root 4015 1 0 22:18 ? 00:00:00 > /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper > /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf > wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid > wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae > monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status > wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status > root 4017 4015 6 22:18 ? 00:00:29 /opt/jdk/bin/java > -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed > -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat > -Djava.io.tmpdir=/opt/tomcat/temp > -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib -classpath > /opt/ > tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar > -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001 > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=4013 > -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s > ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 > org.tanukisoftware.wrapper.WrapperStartStopApp > org.apache.catalina.startup.Bootstrap 1 start > org.apache.catalina.startup.Bootstrap TRUE 1 stop > root 4296 27756 0 22:26 pts/0 00:00:00 grep tomcat > > NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes the > pid file which is wrong. When I kill tomcat, wrapper still starts it up > fine but the pid file is all wrong. Also, the 4017 command above seems odd > to me as it passes in all 7 arguments but the WrapperStartStopApp is > supposed to only pass in the 2 start args and the 3 stop args I would think > into the tomcat bootstrap process? > > anyone have any idea what is going on? > thanks, > Dean ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Wrapper-user mailing list Wrapper-user@... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
|
Re: pid file not working???
by Leif Mortenson-2
::
Rate this Message:
Dean,
We have been looking into this and it turns out that this is a bug introduced in version 3.3.7. We added a new WRAPPER_PID environment variable that can be referenced in the wrapper.conf file for things like log files, etc. The problem is that the PID was being set before the process was daemonized (forked). This is a bug if you call "wrapper.sh start". It is working fine as "wrapper.sh console". We view this as 3.3.7 being pretty much broken for UNIX platforms and will be doing a 3.3.8 release with this fix within the next couple days. Sorry for the trouble. Cheers, Leif On Fri, Oct 30, 2009 at 12:50 AM, Leif Mortenson <leif@...> wrote: > Dean, > The PID file should be getting written by the shell script that ships > with the Wrapper. Could you please confirm that you are using our > script? Most likely you are. > > 1) When you first start out, please confirm that no pid file, wrapper > process, or java process are running. > 2) run the script with the "console" command. This should launch the > Wrapper, and Java. > 3) There should now be a PID file containing the Wrapper's PID. > Please confirm the id in the PID file, and also print out a "ps > -faux". > 4) Does the PID in the file match that of the Wrapper? If not, > please send me your shell script and wrapper.conf file as attachments. > Also please send me the name of your OS and version. I should be able > to find the problem from that. > >> Also, the 4017 command above seems odd >> to me as it passes in all 7 arguments but the WrapperStartStopApp is >> supposed to only pass in the 2 start args and the 3 stop args I would think >> into the tomcat bootstrap process? > > This is actually working correctly. The Wrapper is actually launching > the WrapperStartStopApp class, not the Bootstrap class. The > WrapperStartStopApp class is responsible for running the startup and > stop classes with their parameters at the appropriate times. This > looks like you have set it up correctly: > org.tanukisoftware.wrapper.WrapperStartStopApp > org.apache.catalina.startup.Bootstrap 1 start > org.apache.catalina.startup.Bootstrap TRUE 1 stop > > Cheers, > Leif > > On Thu, Oct 29, 2009 at 11:43 PM, Dean Hiller <dean@...> wrote: >> I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun. when I run >> ./tomcat start (tomcat was the wrappertest file) >> my tomcat starts fine but then when running >> ./tomcat status >> it says the pid file is stale yet my wrapper and tomcat are running(and if I >> kill tomcat, the wrapper restarts it). ie. my status and stop commands >> completely don't work because of some pid problem. >> >> Here is data from my last run... >> >> pid file 4013 >> >> Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no 4013 >> exists...that must have been the shell file pid or something). >> >> root@builddragon:/opt/tomcat/ >> wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat >> root 4015 1 0 22:18 ? 00:00:00 >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf >> wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid >> wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae >> monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status >> wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status >> root 4017 4015 6 22:18 ? 00:00:29 /opt/jdk/bin/java >> -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed >> -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat >> -Djava.io.tmpdir=/opt/tomcat/temp >> -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib -classpath >> /opt/ >> tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar >> -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001 >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=4013 >> -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s >> ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 >> org.tanukisoftware.wrapper.WrapperStartStopApp >> org.apache.catalina.startup.Bootstrap 1 start >> org.apache.catalina.startup.Bootstrap TRUE 1 stop >> root 4296 27756 0 22:26 pts/0 00:00:00 grep tomcat >> >> NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes the >> pid file which is wrong. When I kill tomcat, wrapper still starts it up >> fine but the pid file is all wrong. Also, the 4017 command above seems odd >> to me as it passes in all 7 arguments but the WrapperStartStopApp is >> supposed to only pass in the 2 start args and the 3 stop args I would think >> into the tomcat bootstrap process? >> >> anyone have any idea what is going on? >> thanks, >> Dean ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Wrapper-user mailing list Wrapper-user@... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
|
Re: pid file not working???
by Dean Hiller
::
Rate this Message:
cool! and wow! that was quick.
hmmm, I think I was using the wrapper script from 3.2 or something that my friend gave me but I was definitely using the wrapper binary from 3.3.7. Is this bug in 3.3.6 or can I try out 3.3.6? thanks, Dean On Thu, Oct 29, 2009 at 11:11 PM, Leif Mortenson <leif@...> wrote: Dean, ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Wrapper-user mailing list Wrapper-user@... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
|
Re: pid file not working???
by Leif Mortenson-3
::
Rate this Message:
Dean,
This was a bug that was added in 3.3.7. 3.3.6 works perfectly and has been a very stable release. I will let you know as soon as 3.3.8 has been tested and is ready for release. Sincerely, Leif Mortenson Tanuki Software, Ltd. On Fri, Oct 30, 2009 at 11:16 PM, Dean Hiller <dean@...> wrote: > cool! and wow! that was quick. > > hmmm, I think I was using the wrapper script from 3.2 or something that my > friend gave me but I was definitely using the wrapper binary from 3.3.7. Is > this bug in 3.3.6 or can I try out 3.3.6? > thanks, > Dean > > On Thu, Oct 29, 2009 at 11:11 PM, Leif Mortenson <leif@...> > wrote: >> >> Dean, >> We have been looking into this and it turns out that this is a bug >> introduced in version 3.3.7. We added a new WRAPPER_PID environment >> variable that can be referenced in the wrapper.conf file for things >> like log files, etc. The problem is that the PID was being set >> before the process was daemonized (forked). >> >> This is a bug if you call "wrapper.sh start". It is working fine as >> "wrapper.sh console". >> >> We view this as 3.3.7 being pretty much broken for UNIX platforms and >> will be doing a 3.3.8 release with this fix within the next couple >> days. >> >> Sorry for the trouble. >> >> Cheers, >> Leif >> >> On Fri, Oct 30, 2009 at 12:50 AM, Leif Mortenson >> <leif@...> wrote: >> > Dean, >> > The PID file should be getting written by the shell script that ships >> > with the Wrapper. Could you please confirm that you are using our >> > script? Most likely you are. >> > >> > 1) When you first start out, please confirm that no pid file, wrapper >> > process, or java process are running. >> > 2) run the script with the "console" command. This should launch the >> > Wrapper, and Java. >> > 3) There should now be a PID file containing the Wrapper's PID. >> > Please confirm the id in the PID file, and also print out a "ps >> > -faux". >> > 4) Does the PID in the file match that of the Wrapper? If not, >> > please send me your shell script and wrapper.conf file as attachments. >> > Also please send me the name of your OS and version. I should be able >> > to find the problem from that. >> > >> >> Also, the 4017 command above seems odd >> >> to me as it passes in all 7 arguments but the WrapperStartStopApp is >> >> supposed to only pass in the 2 start args and the 3 stop args I would >> >> think >> >> into the tomcat bootstrap process? >> > >> > This is actually working correctly. The Wrapper is actually launching >> > the WrapperStartStopApp class, not the Bootstrap class. The >> > WrapperStartStopApp class is responsible for running the startup and >> > stop classes with their parameters at the appropriate times. This >> > looks like you have set it up correctly: >> > org.tanukisoftware.wrapper.WrapperStartStopApp >> > org.apache.catalina.startup.Bootstrap 1 start >> > org.apache.catalina.startup.Bootstrap TRUE 1 stop >> > >> > Cheers, >> > Leif >> > >> > On Thu, Oct 29, 2009 at 11:43 PM, Dean Hiller <dean@...> >> > wrote: >> >> I am starting to play with JSW for tomcat 3.3.7, 64 bit for fun. when >> >> I run >> >> ./tomcat start (tomcat was the wrappertest file) >> >> my tomcat starts fine but then when running >> >> ./tomcat status >> >> it says the pid file is stale yet my wrapper and tomcat are running(and >> >> if I >> >> kill tomcat, the wrapper restarts it). ie. my status and stop commands >> >> completely don't work because of some pid problem. >> >> >> >> Here is data from my last run... >> >> >> >> pid file 4013 >> >> >> >> Then here is a typical ps...(4017 is tomcat and 4015 is wrapper, but no >> >> 4013 >> >> exists...that must have been the shell file pid or something). >> >> >> >> root@builddragon:/opt/tomcat/ >> >> wrapper-linux-x86-64-3.3.7# ps -ef | grep tomcat >> >> root 4015 1 0 22:18 ? 00:00:00 >> >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/./wrapper >> >> /opt/tomcat/wrapper-linux-x86-64-3.3.7/bin/../conf/tomcat.conf >> >> wrapper.syslog.ident=tomcat6 wrapper.pidfile=/opt/tomcat/tomcat6.pid >> >> wrapper.name=tomcat6 wrapper.displayname=Tomcat6 Server wrapper.dae >> >> monize=TRUE wrapper.statusfile=/opt/tomcat/tomcat6.status >> >> wrapper.java.statusfile=/opt/tomcat/tomcat6.java.status >> >> root 4017 4015 6 22:18 ? 00:00:29 /opt/jdk/bin/java >> >> -Djava.endorsed.dirs=/opt/tomcat/bin:/opt/tomcat/common/endorsed >> >> -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat >> >> -Djava.io.tmpdir=/opt/tomcat/temp >> >> -Djava.library.path=/opt/tomcat/wrapper-linux-x86-64-3.3.7/lib >> >> -classpath >> >> /opt/ >> >> >> >> tomcat/wrapper-linux-x86-64-3.3.7/lib/wrapper.jar:/opt/jdk/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar >> >> -Dwrapper.key=Dq17CpXisAAYC-ed -Dwrapper.port=32001 >> >> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >> >> -Dwrapper.pid=4013 >> >> -Dwrapper.version=3.3.7 -Dwrapper.native_library=wrapper -Dwrapper.s >> >> ervice=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 >> >> org.tanukisoftware.wrapper.WrapperStartStopApp >> >> org.apache.catalina.startup.Bootstrap 1 start >> >> org.apache.catalina.startup.Bootstrap TRUE 1 stop >> >> root 4296 27756 0 22:26 pts/0 00:00:00 grep tomcat >> >> >> >> NOTE: obvioulsy tomcat stop fails and tomcat status fails and deletes >> >> the >> >> pid file which is wrong. When I kill tomcat, wrapper still starts it >> >> up >> >> fine but the pid file is all wrong. Also, the 4017 command above seems >> >> odd >> >> to me as it passes in all 7 arguments but the WrapperStartStopApp is >> >> supposed to only pass in the 2 start args and the 3 stop args I would >> >> think >> >> into the tomcat bootstrap process? >> >> >> >> anyone have any idea what is going on? >> >> thanks, >> >> Dean ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Wrapper-user mailing list Wrapper-user@... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
| Free embeddable forum powered by Nabble | Forum Help |
