In <E993C40BDB792F4BB38DCB444F8B88E70905AA33 at TFPRDEXS1.tf1.groupetf1.fr> "SEGLARD, Thomas" <tseglard at wat.tv> writes:
I got a very strange behaviour on my platform with the Xymon client. The cient process don't stop to change PID (and sometimes the process stops running without any reasons)
First, I would like you to stop Monit/Puppet from restarting the client. After that, kill all "hobbitlaunch" instances. Then start the client with the "runclient.sh start" command.
That should start the client, and it should remain running until explicitly stopped.
If it stops, there is a bug. What version of the client software is this ? Older versions could behave oddly if the system clock was stepped back in time - the 4.3.0 betas/RC's have this fixed.
As a consequence each time PID changes, Puppet restarts Xymon client and
"hobbitlaunch" will remain running with the same PID. The actual client job - that is run by hobbitlaunch - will have a new PID every 5 minutes.
Regards, Henrik