Re: Not a valid pidnumber

[Jan-Henrik Haukeland]

The following:

        monit: <blah> pidfile does not contain a valid pidnumber

is from a control thread monit uses to check if a program it started  
did in fact start. The control thread check the pid file each second  
to see if the program got up and continue to check the pid file for  
up to cycle seconds before it times out, hence the log statements  
above which I just removed from monit since that was somewhat  
excessive logging by monit.

In your case, the program monit tried to start obviously did not  
start since it never wrote a valid pid file or pid. And yes, monit  
will continue to try and start the program at each cycle, but to find  
out why the program did not start you must check the program log  
files or other log files to find out why.



On 17. jun. 2007, at 22.00, Dylan Carruthers wrote:


> It did indicate a problem though: the program wasn't running. Is there
> not a way for the program to be restarted if the pid file is
> incorrect? Or should the program be fixing the pid file before it
> stops etc?
>
> Thanks!
> Dylan
>
> Date: Sat, 16 Jun 2007 18:33:20 +0200
> From: Jan-Henrik Haukeland <address@hidden>
> Subject: Re: Not a valid pidnumber
>
> Monit has been updated in CVS and the log file is no longer peppered
> with these statements. You may get the new monit version by following
> these instructions (or wait for an official release)
>
> http://savannah.nongnu.org/cvs/?group=monit
>
> Best regards
> --
> Jan-Henrik Haukeland
>
>
> On 16. jun. 2007, at 12.45, Dylan Carruthers wrote:
>
>
> > Hi
> >
> > I had a situation where my syslog (Debian 4.0) were filled with
> > monit: <blah> pidfile does not contain a valid pidnumber
> >
> > But the process was not restarted to clear this error. Is there a way
> > to make a restart happen on this error?
> >
> > Cheers,
> > Dylan