Re: why can't monit see the pid file?

[Jan-Henrik Haukeland]

We think there is a problem with CentOS's start/stop scripts which manifests 
itself with Monit. This issue, for instance, refer to a variant of the same 
https://bitbucket.org/tildeslash/monit/issue/59/ssh-failes-to-restart-by-monit

Monit version 5.8.2. address this problem. We want to improve the solution 
further in 5.9, so 5.8.2. is just a temporary release. However, it should 
address this problem and you can download it here if you want to give it a try, 
https://bitbucket.org/tildeslash/monit/get/master.tar.gz 

On 25 Aug 2014, at 22:38, Anthony Griffiths <address@hidden> wrote:

> after reading at the link you gave (thanks) I tried "if 3 restarts within 5 
> cycles then timeout" but all that does is stop monitoring the process, which 
> means that if the process does actually go down monit will not restart it, 
> which is not the result I want. The whole point of monit (for me) is to 
> restart a stopped process.
> In my case the process in question is ffmpeg and it takes a good 5 seconds 
> for the process to come up an start running. What I need is for monit to 
> delay for say 10 seconds before checking the pid but I can't see a way to do 
> that.
> 
> 
> On Mon, Aug 25, 2014 at 9:15 PM, Matt Coneybeare <address@hidden> wrote:
> For me, the issue was resolved with a little tweaking of the monit script to 
> accommodate the longer startup time for jetty/solr. Check my answer here: 
> http://serverfault.com/questions/620728/monit-cannot-connect-to-solr-jetty-instance
> 
> 
> On August 25, 2014 at 4:06:25 PM, Anthony Griffiths (address@hidden) wrote:
> 
>> I've installed monit-5.6-1.el7.x86_64 on centos 7 and I've set up monitrc 
>> but I'm getting: "monit: Error reading pid from file 
>> '/var/run/<process>.pid". I can see the pid file is there, the process is 
>> running because monit has in fact done it's job and started the process but 
>> it keeps stopping and restarting it every minute and I'm baffled as to why I 
>> keep getting this error message filling up the monit.log. Any ideas?