De nada! ('wasn't of much help, was I?!)
2015-07-23 12:55 GMT+02:00 shadow <[email protected]>:
> Turns out that monit did not restarted properly or did not reread the
> config properly.
>
> After a monit reload - everything is fine.
>
> Thanks for your help
>
>
> On 23.07.2015 12:47, shadow wrote:
> > Funny thing,
> >
> > if I copy the file /var/run/apache2/apache2.pid --> /var/run/apache2.pid
> > (former location in configuration).
> >
> > Monit is fine and recognized that the service is started and all is fine.
> >
> > Even if I restart monit it does not recognize the new location. I
> > expected if I restart it, it should reread the new configuration file.
> >
> > Is there an option to flush all internal configs and reread them?
> >
> >
> > On 23.07.2015 12:06, shadow wrote:
> >> Hello monit community,
> >>
> >> since I upgraded my servers to debian jessie I encountered the following
> >> behavior.
> >>
> >> Monit says it cannot start my apache2 anymore. Initialization failed.
> >> The log says:
> >>
> >>> Jul 23 11:59:00 www-xeon monit[495]: 'apache' process is not running
> >>> Jul 23 11:59:00 www-xeon monit[495]: 'apache' trying to restart
> >>> Jul 23 11:59:00 www-xeon monit[495]: 'apache' start:
> /etc/init.d/apache2
> >>> Jul 23 12:00:00 www-xeon monit[495]: 'apache' failed to start (exit
> status 0) -- /etc/init.d/apache2: Starting web server: apache2.
> >>
> >> But it actually restarts the apache process is restarted. But claim that
> >> it fails and unmonitors the service in the webgui. But if I stop the
> >> apache again, monit kicks in and restarts it. So there seem to be two
> >> false positives
> >>
> >> At first I thought it could the wrong .pid entry in
> >> /etc/monit/conf.d/apache. But that wasnt the case. (Changed in debian
> >> jessie from /var/run/apache2 to /var/run/apache2/apache2.pid )
> >>
> >>> check process apache with pidfile "/var/run/apache2/apache2.pid"
> >>> start program = "/etc/init.d/apache2 start" with timeout 60 seconds
> >>> stop program = "/etc/init.d/apache2 stop"
> >>> if cpu > 60% for 2 cycles then alert
> >>> if cpu > 80% for 5 cycles then restart
> >>> if children > 250 then restart
> >>> if loadavg(5min) greater than 10 for 8 cycles then stop
> >>> group server
> >>
> >>
> >> Does anyone had similiar issues? Am I missing something?
> >>
> >> thanks for this great tool - love it :)
> >>
> >> cheers shadow // systemli.org
> >>
> >>
> >>
> >>
> >>
> >> --
> >> To unsubscribe:
> >> https://lists.nongnu.org/mailman/listinfo/monit-general
> >>
> >
> >
> >
> >
> > --
> > To unsubscribe:
> > https://lists.nongnu.org/mailman/listinfo/monit-general
> >
>
>
> --
> best regards | viele Gruesse, [email protected]
>
> receive my key: gpg --keyserver zimmermann.mayfirst.org --recv-keys
> 0x06264855BA2DE161F08905A85C6B6ED4248C1F32
>
>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
