[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Execution Failed"
Re: "Execution Failed"
Fri, 4 May 2012 21:44:28 +0800
unmonitor and then monitor worked. Thanks
On Fri, May 4, 2012 at 9:33 PM, Martin Pala <address@hidden> wrote:
> the execution error flag is set, because monit wasn't able to start the
> process … the root cause could be, that either the stat program failed to
> start it - for example because of some missing environment variable: monit
> executes the programs in the sandbox and purges environment variables, it
> sets just basic PATH=/bin:/usr/bin:/sbin:/usr/sbin. Another possible reason
> could be, that the service start was too slow (based on the output your start
> timeout 30s, which is the default).
> If somebody starts the service manually (out of monit control), the execution
> error flag remains set as a reminder, that monit wasn't able to start it =>
> the configuration should be fixed.
> To clear the flag, just unmonitor and monitor the service:
> monit unmonitor pixelServer
> monit monitor pixelServer
> On May 4, 2012, at 12:31 PM, David Montgomery wrote:
>> I have one particular process that I am monitoring that all of a
>> sudden stop working in monit. For the process status...I get
>> "Execution Failed"
>> Below is the output from running monit -v
>> Process Name = pixelServer
>> Pid file = /etc/sv/pixelServer/supervise/pid
>> Monitoring mode = active
>> Start program = '/usr/bin/sv start pixelServer' timeout 30 second(s)
>> Stop program = '/usr/bin/sv kill pixelServer' timeout 30 second(s)
>> Existence = if does not exist 1 times within 1 cycle(s)
>> then restart else if succeeded 1 times within 1 cycle(s) then alert
>> Pid = if changed 1 times within 1 cycle(s) then alert
>> Ppid = if changed 1 times within 1 cycle(s) then alert
>> Unix Socket = if failed /tmp/nginx9001.socket [protocol
>> DEFAULT] with timeout 5 seconds 1 times within 1 cycle(s) then restart
>> else if succeeded 1 times within 1 cycle(s) then alert
>> Port = if failed 127.0.0.1:80/pixel [HTTP via TCP]
>> with timeout 5 seconds 1 times within 1 cycle(s) then restart else if
>> succeeded 1 times within 1 cycle(s) then alert
>> I logged into the machine and all is well. The pid is fine and not
>> changing, the url and path is fine, I even restarted the process
>> manually...all is fine. The process is a python script using
>> spawn-fcgi under runit control.
>> I have 3 other similar process and they are all working as expected.
>> So...every that every other indicator suggests the process is fine,
>> then how do I do a deeper dive to find out why monit is have an issue
>> with that process?
>> To unsubscribe:
> To unsubscribe: