[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: monit not connecting to mmonit

From: Martin Pala
Subject: Re: monit not connecting to mmonit
Date: Thu, 13 Oct 2011 11:58:08 +0200


the problem will most probably be, that the monit id is the same as some other 
machine (for example if the machine was created by cloning the image of other 
system). The monit id is used to pair the status message from monit with host 
entry in M/Monit - if such id doesn't exist, new host is created automatically, 
otherwise the existing host entry with corresponding monit id is updated.

The solution is simple:
1.) stop monit
2.) remove the monit id file (by default stored as ~/
3.) start monit … it will generate new id and store it to the file, you should 
see the new host in M/Monit now

Best regards,

On Oct 12, 2011, at 5:28 PM, AEI Hannover wrote:

> Hi all,
> I have a problem here with one particular system where monit is not
> connecting to my m/monit instance.
> The setup for monit on that machine is the same as for dozens of other
> machines here that work fine. In particular, I have the line
> set mmonit http://monit:address@hidden
> in there. Monit starts just fine
> [CEST Oct 12 17:12:53] info     : Starting monit daemon with http interface 
> at [*:8080]
> [CEST Oct 12 17:12:53] info     : Starting monit HTTP server at [*:8080]
> [CEST Oct 12 17:12:53] info     : monit HTTP server started
> [CEST Oct 12 17:12:53] info     : 'system_pt-fb11' Monit started
> [CEST Oct 12 17:12:53] info     : M/Monit heartbeat started
> and never complains about anything. It writes me emails about starting and 
> stopping the monit instance just fine.  However, it never shows up on my 
> m/monit server, although it claims to send the necessary information:
> M/Monit: status message sent to http://cascade:8080/collector
>> From a quick tcpdump on the machine I can verify that it is talking to the 
>> m/monit, but obviously something must be going wrong there (although I 
>> cannot see any error message at all). Any hints what might be the reason for 
>> this?
> cu
>  Gerrit
> --
> To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]