My check looks like this: check process api with pidfile /var/run/api.pid start program = "/opt/api/server.sh start 8888" stop program = "/opt/api/server.sh stop" if failed port 8888 protocol http request "/ping" for 2 cycles then restart
Why do you mean by "please check that the pid from the file is running". So I should start the application first (put the pid into the file) and then lat monit take over? Is there a more elegant solution if there is no pid at all? 2016-01-28 9:33 GMT+01:00 Martin Pala <[email protected]>: > Hi, > > the way you added the configuration is correct, the problem will be most > probably in the "check process" configuration ... if you use a pidfile, > please check that the pid from the file is running, if you use a pattern > based check, test the pattern using "monit procmatch <pattern>" > > Regards, > Martin > > > On 28 Jan 2016, at 08:47, Michael Wittig <[email protected]> wrote: > > Hi > > I want to add processes to monit (monit-5.2.5-3.11.amzn1.x86_64) during > runtime. So far I include > > include /etc/monit.d/* > > all files from a certain directory. When I add a new process I place a > file into /etc/monit.d/ and run > > monit -c /etc/monit.conf reload > > Th problem is that I get a process is not running error in my logs. Any > idea how I can get rid of the error message? > > I most likely will not be alerted on this. But I want to get alerts if my > process dies after the first start? > > Thanks > Michael > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general > > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general >
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
