Hello,
Sorry to bring back this 1,5 year old issue but this is giving me
headaches.
Its about ignoring PID/PPID changes from monit to m/monit.
If locally specified it works, but not when pushing alerts from monit
to m/monit.
Has it been "solved" in monit 5.10 or m/monit 3.3?
Is there a plan to implement this feature in NEAR future releases?
Is there a way to circumvent?
Thanks a lot,
Rui Lapa
On Fri, Mar 9, 2012 at 8:33 AM, Rui Lapa <[email protected]> wrote:
> Thanks Martin!
>
> Always helpfull!
>
> I'm not responsible for this "pid changed event', this is due to
> /etc/dhcp/dhclient-exit-hooks.d/ntp used on Ubuntu when DHCP/Interface
> changes.
>
> We use this mostly on +200 laptops that move around the country
> roaming between different private network ranges.
>
> Since monit is "always on", it's a nice way of knowing device IP
> and, if needed, remotely accessing them, besides the normal operator
> replacement tasks.
>
> I've noticed this behavior and was wondering if there is a way of
> reducing M/Monit processing by disabling this "event".
>
> I'm not really using M/Monit for this, although I've bought and use
> one for the server farms.
> For the laptops I use a custom django-monit because we don't need
> notifications and the integration with operator and helpdesk web based
> "console".
> I'm now ignoring it, but I still get events and need to parse them.
>
> Em 08-03-2012 15:30, Martin Pala escreveu:
>
> > Hello,
> >
> > the PID change event is generated automatically - there is currently no
> way to suppress it.
> >
> > The PID changes the process which is monitored by Monit is restarted
> externally (e.g. manually) … in general when the process is monitored, the
> restart should be either done via monit or the monitoring should be
> disabled+enabled during the restart, otherwise if monit detects that the
> process is not running, it will try to restart it, whereas the manual
> restart could be pending. How the system will deal with the parallel
> restart attempts depends on the start methods.
> >
> > => i recommend one of following ways to restart the monitored process
> (which also prevents the 'pid changed' event):
> > 1.) either do:
> > monit restart<servicename>
> > 2.) or do:
> > monit unmonitor<servicename>
> > <do manual maintanence of the service as needed>
> > monit monitor<servicename>
> >
> > Regards,
> > Martin
> >
> >
> > On Mar 6, 2012, at 12:38 PM, Rui Lapa wrote:
> >
> >> Hello,
> >>
> >> How do I ignore all ntp PID changes and NOT SEND them to M/Monit server.
> >>
> >> if changed pid then exec "/bin/echo" ???
> >>
> >> Thanks,
> >> Rui Lapa
> >>
> >> --
> >> 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
