Re: pid change notice

[Martin Pala]

It seems that you application actually creates two "susepics" processes, one of 
them has "init" as parent (init's PID=1) and has one child process "susepics". 
The init as parent is common when the process demonizes itself. In your case 
the pattern based check is not suitable, as the pattern is not unique and 
matches two processes.

Regards,
Martin


On Mar 29, 2012, at 12:06 PM, Gerrit Kühn wrote:

> On Thu, 29 Mar 2012 10:31:54 +0200 Martin Pala <address@hidden>
> wrote about Re: pid change notice:
> 
> MP> Which Monit version it is? Please can you send full monit log? The
> MP> pattern based process check needs unique match - if there are more
> MP> processes matching the same pattern, the test may see different
> MP> process (PID) during different cycles. If the pidfile is available, it
> MP> could be better choice if multiple processes matching the same pattern
> MP> are running.
> 
> This is with monit-5.2.3.
> You are probably right that there is some other process popping up:
> 
> 
> [CEST Mar 29 11:46:39] error    : 'susepics' process PPID changed to 9967
> [CEST Mar 29 11:47:39] error    : 'susepics' process PPID changed to 1
> [CEST Mar 29 11:48:39] error    : 'susepics' process PID changed to 2052
> [CEST Mar 29 11:48:40] error    : 'susepics' process PPID changed to 9967
> [CEST Mar 29 11:49:40] error    : 'susepics' process PID changed to 9967
> [CEST Mar 29 11:49:40] error    : 'susepics' process PPID changed to 1
> [CEST Mar 29 11:50:40] info     : 'susepics' process PID has not changed
> since last cycle
> 
> However, I have no idea what this process might be (PPID is 1?). It is 
> certainly gone soon. Unfortunately the scripts that start the process are 
> autogenerated, and it is not that easy to get a proper PID file.
> 
> 
> cu
>  Gerrit