Re: mmonit 2.0.3 to 2.3.3 (3rd send, not seen in list traffic)

[Mike Schmidt]

Having seen this myself in certain cases, if you don't get this m/monit error on every monit client, but only on some, the you have an error in your monit config on these machines. The fact that monit likes it does not mean that m/monit likes it. For example, when I had two group entries in one service entry, m/monit responded exactly this way, even though monit didn't complain., Check the m/monit error log for more details. 

Note that m/monit does NOT accept any standard xml, if there is anything in the xml status or event report report that m/monit does not expect, this is what happens.

On Sat, Mar 26, 2011 at 12:06 PM, Len Conrad <address@hidden> wrote:

upgrading all our monits and mmonit to latest version.

in the CHANGES, nothing about 2.0.3 to 2.3.3

Is it easier erase 2.0.3 and start over, or is there an upgrade script?

also, getting really tired of this stuff on only a couple of our monits, and our inability to stop it.

[CDT Mar 24 11:51:11] error    : M/Monit: message sending failed to http://mmonit.xxx.net:8080/collector -- HTTP/1.1 500 Internal Server error
[CDT Mar 24 11:51:11] error    : M/Monit: communication failed (status message)

... every one or two seconds in monit.log.

mmonit can connects to the monit fine, shows that monit's monitored items.

deleting the monit host on mmonit and recreating doesn't work.

monit's password for mmonit is correct.

deleting monit's  .files for id, state, whatever, and restarting monit, no fix.

Thanks
Len



--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general

--

Mike SCHMIDT
CTO 
Intello Technologies Inc.
address@hidden

Canada: 1-888-404-6261 x320
USA: 1-888-404-6268 x320
www.intello.com