Hello,
the clean way is to restat the service via monit after the deploy like this:
/usr/bin/monit restart app_thin
If you want to just suppres the alert on PID change, you can set the filter
option for the alert statement:
set alert foo@bar but not on { pid ppid } #note: send all alerts to foo@bar
except on PID or PPID change
Regards,
Martin
On Nov 10, 2011, at 3:09 AM, Mike Zupan wrote:
> I have a monitor in place that looks like
>
> check process app_thin_8107
> with pidfile /data/app/current/tmp/pids/thin.8107.pid
> start = "/etc/init.d/thin-app start 8107"
> stop = "/etc/init.d/thin-app stop 8107"
> if totalmem > 500.0 MB for 3 cycles then restart
> if 9 restarts within 9 cycles then timeout
>
> We do a lot of deploys and thin needs to be restarted for each deploy
> and we get spammed with email each time. Is there a way to tell monit
> to ignore pid changes?
>
> Or is the solution to monitor the port and not the process?
>
> thanks
> mike
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
