Re: Monit: 'Matching' functionality isn't working

2015-06-24 Thread Martin Pala
On 24 Jun 2015, at 22:33, Marie Mcallister mmcallis...@sprinklr.com wrote: ​Hi Martin, ​The problem is with the 'Start' command. The proc match works fine, the check detects ​when the process is down. ​For example, if I just use this outside of monit, it works fine to bring back

Re: Monit: 'Matching' functionality isn't working

2015-06-24 Thread Marie Mcallister
​Hi Martin, ​The problem is with the 'Start' command. The proc match works fine, the check detects ​when the process is down. ​For example, if I just use this outside of monit, it works fine to bring back the process: ​/usr/bin/nohup /mnt1/build/seeing/build/bin/run.sh ​But if I put that

Re: Monit: 'Matching' functionality isn't working

2015-06-24 Thread Jan-Henrik Haukeland
The programs or scrips given to start, stop and restart are executed by Monit using exec, not a shell, and while it is perfectly fine to wrap the command in bash as you do, I would recommend to just use start program = “/mnt1/build/seeing/build/bin/run.sh” The ’nohup’ and ‘’ character used in

Re: Monit: 'Matching' functionality isn't working

2015-06-24 Thread Marie Mcallister
Hi Martin, Yes, that is what I tried as well, noted before. I tried formatting it as such: start program = /bin/bash -c 'nohup /mnt1/build/seeing/build/bin/run.sh ' but the same thing occurs. It won't run this for some reason - when I check logs, it says: [UTC Jun 24 21:25:05] error: