Re: M/Monit host registration issues

[Predrag Punosevac]

On 12/26/2013 23:58 PM, Rui Lapa wrote:
 
> Simple Top-Down List:
> 
> Check syntax
>     monit -t
> 
> Check Id file
>     monit -v
> 
> 
> Stop Monit
> remove .monit.id
> 
> Start TCP network sniffer on both hosts, filter traffic between both
> hosts
>     tcpdump -n "host MMONIT_IP and host CLIENT_IP"
>     ping to check sniffer
> 
> Run monit in verbose
>     monit -I -vv
> 
> Unmonitor something
>     monit unmonitor SOMETHING
> 
> 
> 
> In case of no success... do an "strace -fo monit.log monit -I" and check
> monit.log, Hope you understand system calls. 
> 
> My 2 cents!

I took a clue from this excellent answer by Mr. Rui Lapa. After a bit of
debugging it became clear that Monit client was trying to contact
M/Monit server but it was timing out due to the 500 internal server
error. Before going further and trying to figure out why the server is
refusing the connection I checked the Monit version. The version of
Monit I installed on Springdale Linux using yum was

address@hidden ~]$ monit -V
This is monit version 5.1.1

The version I had on this laptop running the latest OpenBSD release was

address@hidden monit -V
This is Monit version 5.5.1
Copyright (C) 2001-2012 Tildeslash Ltd. All Rights Reserved.

Long story short I downloaded the latest binaries from  Tildeslash Ltd.
website and everything is working as expected. OpenBSD port of Monit has
been already updated but it will become available for OpenBSD 5.5
release.

I would like to thank this community and in particularly Mr. Rui Lapa
for such a worm welcome.