Re: Monit HTTP console stopped on reload

[Martin Pala]

This behavior is normal and expected. The http interface is not killed 
but restarted.

On reload monit first stops the http interface, saves state, cleans up 
the configuration, then parses the new configuration and if allowed, the 
http interface is started and monitoring cycle follows.

It should be quite quick, and until monit finished reload, it won't 
perform any other action.

Martin


Alexey Verkhovsky wrote:
> When monit receives a SIGHUP (or I run monit reload, which does the
> same thing), it quite often kills HTTP server and does not start it
> again until after the next monitoring cycle.
>
> Is it a bug or a feature?
>
> --
> Alex Verkhovsky
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general