|
From: Leif M. <lei...@ta...> - 2014-04-08 07:11:13
|
Davide, I am sorry for the trouble. The Wrapper's instantiation is controlled by the shell script of Linux and other UNIX platforms. It tells the Wrapper to create a PID file when it starts and then delete it when it exits. This PID file is used to decide whether the Wrapper is running and then locate it to request its status. Just in case the Wrapper or system were to crash and a stale PID file is left around, the script contains logic that lets it decide that the PID file is stale, delete it, and continue. This logic has been tuned over the years and has been quite reliable. If someone launches the Wrapper without using the shell script then these checks will not take place and it would be possible to launch a second instance. Is it possible that something like this could have happened? Cheers, Leif On Mon, Apr 7, 2014 at 11:20 PM, Davide Silvestre <ds...@cd...> wrote: > Hi, > > I am using the tanukisoft wrapper version 3.5.15 on different environments > and I am experiencing this issue only on a Linux server (Red Hat > Enterprise Linux Server release 6.5 (Santiago)). > > From time to time I can see that there are 2 wrapper processes created for > a sevice. If I stop the service only the second process terminates. The > first one is like "detached" from the service. > > Any idea of why this is happening? > > > > Davide > > |