Menu
▾
▴
wrapper-user
|
From: Divya H. <div...@gm...> - 2012-03-05 09:52:39
|
I have few services that are running in a Linux machines and I am using the 3.2.3 version of http://old.nabble.com/file/p33441896/Poller.conf Poller.conf Java Service Wrapper. Just before the sever reboot, the services are stopped using a stopall services command(that has stop command for each service).While Few services are giving out the following warning :: 'WARN | wrapper | 2012/03/04 03:00:42 | JVM process was still running after receiving a SIGCHLD signal. STATUS | wrapper | 2012/03/04 03:00:42 | TERM trapped. Shutting down.' After the sever reboot, a startall application script(that has start command for each service) is run.It starts all the applications except those that gave the above warning. But when I try starting the service again using the start command of that particular service, it starts with the message '"Removed stale pid file:' . I want to understand here two things: 1.Why the process has become stale. 2.Why the start all application command that had the start command didn start it after removing the stale id. I am attaching the configuration file. Thanks in advance. -- View this message in context: http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33441896p33441896.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Christian M. <chr...@ta...> - 2012-03-06 03:13:40
|
Hello Divya, how is your script starting/stopping the processes exactly? The wrapper-script whenever called to start an instance, checks for the pid-file, which contains the pid of the Wrapper process. If the pid from the file matches with the currently running processes, then it won't start the Wrapper, since it assumes the process is already running. The warning "Removed stale pid file", means that the pid in the pid file doesn't match. So the script removes the file and starts a new instance. The Wrapper removes the pid file by itself usually during exiting, however if the Wrapper is forcibly killed (like a kill -9), then it won't have a chance to remove the file. So when you run the start command after the reboot and see the stale pid warning, it means probably, that the Wrapper was forcibly killed during shutdown and couldn't remove the pid file. could you also please turn on debug log level (wrapper.debug=TRUE) and re-run? Best Regards, Christian Mueller Tanuki Software, Ltd. On Mon, Mar 5, 2012 at 6:52 PM, Divya Habin <div...@gm...>wrote: > > I have few services that are running in a Linux machines and I am using the > 3.2.3 version of http://old.nabble.com/file/p33441896/Poller.conf > Poller.conf Java Service Wrapper. Just before the sever reboot, the > services > are stopped using a stopall services command(that has stop command for each > service).While Few services are giving out the following warning :: > 'WARN | wrapper | 2012/03/04 03:00:42 | JVM process was still running > after receiving a SIGCHLD signal. > STATUS | wrapper | 2012/03/04 03:00:42 | TERM trapped. Shutting down.' > > After the sever reboot, a startall application script(that has start > command > for each service) is run.It starts all the applications except those that > gave the above warning. > > But when I try starting the service again using the start command of that > particular service, it starts with the message '"Removed stale pid file:' . > > I want to understand here two things: > 1.Why the process has become stale. > 2.Why the start all application command that had the start command didn > start it after removing the stale id. > > I am attaching the configuration file. > > Thanks in advance. > > > -- > View this message in context: > http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33441896p33441896.html > Sent from the Java Service Wrapper mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Divya H. <div...@gm...> - 2012-03-06 13:49:40
|
Hi Mueller, Thanks for the reply. I will turn on the debug level and see what is going around.I will let you know my observations then. Thanks, Divya Christian Mueller-13 wrote: > > Hello Divya, > > how is your script starting/stopping the processes exactly? > > The wrapper-script whenever called to start an instance, checks for the > pid-file, which contains the pid of the Wrapper process. > If the pid from the file matches with the currently running processes, > then > it won't start the Wrapper, since it assumes the process is already > running. > The warning "Removed stale pid file", means that the pid in the pid file > doesn't match. So the script removes the file and starts a new instance. > The Wrapper removes the pid file by itself usually during exiting, however > if the Wrapper is forcibly killed (like a kill -9), then it won't have a > chance to remove the file. > So when you run the start command after the reboot and see the stale pid > warning, it means probably, that the Wrapper was forcibly killed during > shutdown and couldn't remove the pid file. > > could you also please turn on debug log level (wrapper.debug=TRUE) and > re-run? > > Best Regards, > > Christian Mueller > Tanuki Software, Ltd. > > On Mon, Mar 5, 2012 at 6:52 PM, Divya Habin > <div...@gm...>wrote: > >> >> I have few services that are running in a Linux machines and I am using >> the >> 3.2.3 version of http://old.nabble.com/file/p33441896/Poller.conf >> Poller.conf Java Service Wrapper. Just before the sever reboot, the >> services >> are stopped using a stopall services command(that has stop command for >> each >> service).While Few services are giving out the following warning :: >> 'WARN | wrapper | 2012/03/04 03:00:42 | JVM process was still running >> after receiving a SIGCHLD signal. >> STATUS | wrapper | 2012/03/04 03:00:42 | TERM trapped. Shutting down.' >> >> After the sever reboot, a startall application script(that has start >> command >> for each service) is run.It starts all the applications except those that >> gave the above warning. >> >> But when I try starting the service again using the start command of that >> particular service, it starts with the message '"Removed stale pid file:' >> . >> >> I want to understand here two things: >> 1.Why the process has become stale. >> 2.Why the start all application command that had the start command didn >> start it after removing the stale id. >> >> I am attaching the configuration file. >> >> Thanks in advance. >> >> >> -- >> View this message in context: >> http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33441896p33441896.html >> Sent from the Java Service Wrapper mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------------ >> Try before you buy = See our experts in action! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-dev2 >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- View this message in context: http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33442324p33451001.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Divya H. <div...@gm...> - 2012-04-02 06:14:27
|
Hi Mueller, I tried enabling the debug level but it did no help :(. The script to stop and start the monitoring application is put as a service on the server and it will be run before and after the server reboot respectively. Before reboot, when the service is run, this is the message printed on log: STATUS | wrapper | 2012/04/01 03:00:47 | TERM trapped. Shutting down. WARN | wrapper | 2012/04/01 03:00:47 | JVM process was still running after receiving a SIGCHLD signal. After reboot, when the service is run the application is not started but when the command to start is run individually the application is started and the message printed is : [root@rpc bin]# /TaskingEAI/bin/UserMonitoring start Starting User Monitoring Application... Removed stale pid file: TaskingEAI/bin/./UserMonitoring.pid Thanks, Divya Divya Habin wrote: > > Hi Mueller, > > Thanks for the reply. > > I will turn on the debug level and see what is going around.I will let you > know my observations then. > > Thanks, > Divya > > > Christian Mueller-13 wrote: >> >> Hello Divya, >> >> how is your script starting/stopping the processes exactly? >> >> The wrapper-script whenever called to start an instance, checks for the >> pid-file, which contains the pid of the Wrapper process. >> If the pid from the file matches with the currently running processes, >> then >> it won't start the Wrapper, since it assumes the process is already >> running. >> The warning "Removed stale pid file", means that the pid in the pid file >> doesn't match. So the script removes the file and starts a new instance. >> The Wrapper removes the pid file by itself usually during exiting, >> however >> if the Wrapper is forcibly killed (like a kill -9), then it won't have a >> chance to remove the file. >> So when you run the start command after the reboot and see the stale pid >> warning, it means probably, that the Wrapper was forcibly killed during >> shutdown and couldn't remove the pid file. >> >> could you also please turn on debug log level (wrapper.debug=TRUE) and >> re-run? >> >> Best Regards, >> >> Christian Mueller >> Tanuki Software, Ltd. >> >> On Mon, Mar 5, 2012 at 6:52 PM, Divya Habin >> <div...@gm...>wrote: >> >>> >>> I have few services that are running in a Linux machines and I am using >>> the >>> 3.2.3 version of http://old.nabble.com/file/p33441896/Poller.conf >>> Poller.conf Java Service Wrapper. Just before the sever reboot, the >>> services >>> are stopped using a stopall services command(that has stop command for >>> each >>> service).While Few services are giving out the following warning :: >>> 'WARN | wrapper | 2012/03/04 03:00:42 | JVM process was still >>> running >>> after receiving a SIGCHLD signal. >>> STATUS | wrapper | 2012/03/04 03:00:42 | TERM trapped. Shutting down.' >>> >>> After the sever reboot, a startall application script(that has start >>> command >>> for each service) is run.It starts all the applications except those >>> that >>> gave the above warning. >>> >>> But when I try starting the service again using the start command of >>> that >>> particular service, it starts with the message '"Removed stale pid >>> file:' . >>> >>> I want to understand here two things: >>> 1.Why the process has become stale. >>> 2.Why the start all application command that had the start command didn >>> start it after removing the stale id. >>> >>> I am attaching the configuration file. >>> >>> Thanks in advance. >>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33441896p33441896.html >>> Sent from the Java Service Wrapper mailing list archive at Nabble.com. >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Try before you buy = See our experts in action! >>> The most comprehensive online learning library for Microsoft developers >>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >>> Metro Style Apps, more. Free future releases when you subscribe now! >>> http://p.sf.net/sfu/learndevnow-dev2 >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >> >> ------------------------------------------------------------------------------ >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-d2d >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > -- View this message in context: http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33442324p33544977.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Christian M. <chr...@ta...> - 2012-04-04 06:19:16
|
Hello Divya, how did you install the daemon? Furthermore please let me know which OS you are trying to run. We have actually updated the script from version 3.2.3. greatly, and since version 3.4.0, the script enables you to let it install itself in your system as daemon process. For installing the script as daemon simply run: ./script.sh install (you need to be root/sudo for that) If it's possible could you also please try if you see the same after using a more later version? Best Regards, Christian On Mon, Apr 2, 2012 at 3:14 PM, Divya Habin <div...@gm...>wrote: > > Hi Mueller, > > I tried enabling the debug level but it did no help :(. > The script to stop and start the monitoring application is put as a service > on the server and it will be run before and after the server reboot > respectively. > Before reboot, when the service is run, this is the message printed on log: > STATUS | wrapper | 2012/04/01 03:00:47 | TERM trapped. Shutting down. > WARN | wrapper | 2012/04/01 03:00:47 | JVM process was still running > after receiving a SIGCHLD signal. > > After reboot, when the service is run the application is not started but > when the command to start is run individually the application is started > and > the message printed is : > [root@rpc bin]# /TaskingEAI/bin/UserMonitoring start > Starting User Monitoring Application... > Removed stale pid file: TaskingEAI/bin/./UserMonitoring.pid > > > Thanks, > Divya > > > > Divya Habin wrote: > > > > Hi Mueller, > > > > Thanks for the reply. > > > > I will turn on the debug level and see what is going around.I will let > you > > know my observations then. > > > > Thanks, > > Divya > > > > > > Christian Mueller-13 wrote: > >> > >> Hello Divya, > >> > >> how is your script starting/stopping the processes exactly? > >> > >> The wrapper-script whenever called to start an instance, checks for the > >> pid-file, which contains the pid of the Wrapper process. > >> If the pid from the file matches with the currently running processes, > >> then > >> it won't start the Wrapper, since it assumes the process is already > >> running. > >> The warning "Removed stale pid file", means that the pid in the pid file > >> doesn't match. So the script removes the file and starts a new instance. > >> The Wrapper removes the pid file by itself usually during exiting, > >> however > >> if the Wrapper is forcibly killed (like a kill -9), then it won't have a > >> chance to remove the file. > >> So when you run the start command after the reboot and see the stale pid > >> warning, it means probably, that the Wrapper was forcibly killed during > >> shutdown and couldn't remove the pid file. > >> > >> could you also please turn on debug log level (wrapper.debug=TRUE) and > >> re-run? > >> > >> Best Regards, > >> > >> Christian Mueller > >> Tanuki Software, Ltd. > >> > >> On Mon, Mar 5, 2012 at 6:52 PM, Divya Habin > >> <div...@gm...>wrote: > >> > >>> > >>> I have few services that are running in a Linux machines and I am using > >>> the > >>> 3.2.3 version of http://old.nabble.com/file/p33441896/Poller.conf > >>> Poller.conf Java Service Wrapper. Just before the sever reboot, the > >>> services > >>> are stopped using a stopall services command(that has stop command for > >>> each > >>> service).While Few services are giving out the following warning :: > >>> 'WARN | wrapper | 2012/03/04 03:00:42 | JVM process was still > >>> running > >>> after receiving a SIGCHLD signal. > >>> STATUS | wrapper | 2012/03/04 03:00:42 | TERM trapped. Shutting > down.' > >>> > >>> After the sever reboot, a startall application script(that has start > >>> command > >>> for each service) is run.It starts all the applications except those > >>> that > >>> gave the above warning. > >>> > >>> But when I try starting the service again using the start command of > >>> that > >>> particular service, it starts with the message '"Removed stale pid > >>> file:' . > >>> > >>> I want to understand here two things: > >>> 1.Why the process has become stale. > >>> 2.Why the start all application command that had the start command didn > >>> start it after removing the stale id. > >>> > >>> I am attaching the configuration file. > >>> > >>> Thanks in advance. > >>> > >>> > >>> -- > >>> View this message in context: > >>> > http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33441896p33441896.html > >>> Sent from the Java Service Wrapper mailing list archive at Nabble.com. > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Try before you buy = See our experts in action! > >>> The most comprehensive online learning library for Microsoft developers > >>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, > MVC3, > >>> Metro Style Apps, more. Free future releases when you subscribe now! > >>> http://p.sf.net/sfu/learndevnow-dev2 > >>> _______________________________________________ > >>> Wrapper-user mailing list > >>> Wra...@li... > >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user > >>> > >> > >> > ------------------------------------------------------------------------------ > >> Keep Your Developer Skills Current with LearnDevNow! > >> The most comprehensive online learning library for Microsoft developers > >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > >> Metro Style Apps, more. Free future releases when you subscribe now! > >> http://p.sf.net/sfu/learndevnow-d2d > >> _______________________________________________ > >> Wrapper-user mailing list > >> Wra...@li... > >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > >> > >> > > > > > > -- > View this message in context: > http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33442324p33544977.html > Sent from the Java Service Wrapper mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
