Re: [monit] monit upgrade

[Martin Pala]

Monit uses it's pidfile to check whether the monit daemon is running  
already - if it is, then it will work only as CLI utility and will  
communicate with existing daemon via http interface (the combination  
of 5.0 client with 4.10.1 server may be OK). Only the daemon writes  
statefiles - the CLI utility won't overwrite statefile.

For upgrade you don't need to stop services ... just do:

 monit quit (it will stop current monit daemon)

and then start new version of monit. It will detect that the processes  
are running already and won't try to restart.



On Jan 23, 2009, at 12:51 AM, Gilad Benjamini wrote:

> I had a system running with monit 4.10.1
> I executed the following sequence
>         1. Installed monit5.0beta6
>         2. "monit stop all"
>         3. Stopped monit
>         4. Started monit
>         5. "monit start all"
>
> It turns out that in phase #2 some of the services (perhaps all of  
> them, not
> sure) didn't actually stop. Technically, in this phase a monit5.0  
> executable
> was communicating with a monit4.10 daemon. I assume this might be an  
> illegal
> combination ?
> Even if it is illegal, I don't think that this should have happened. I
> suspect that phase #2 wrote a new state file which the existing  
> daemon could
> not handle.
>
> I am guessing the right sequence is to install the new monit after  
> stopping
> the current one.
>
> Is there a way to update monit without stopping all the services ? On
> production machines this could be crucial.
>
>
>
>
>
>
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general