On 11/22/2010 2:58 PM, Henrik Størner wrote:
Not easily. The network test code in Xymon is pretty "dumb", it doesn't support a communication scenario with multiple stages. After connecting to the port, if there's a "send" string in the protocols.cfg (bb-services) file it will send that, and then it will just wait to see if the "expect" string arrives. It doesn't support multiple expect/send sequences. In the old days, the smtp check just waited for the "220" greeting in the banner from the smtp daemon and then disconnected. However, that caused sendmail to log connections from Xymon because *that* behaviour is also not RFC-compliant. I don't know what Postfix thinks of it - you could try just commenting out the "send" string of the smtp-test in protocols.cfg.
I did get it to stop logging the nasty message using multiple send commands, with thanks to Bruce White. It sends mail, then it sends quit. This separates the two commands into separate TCP packets, which seems to be enough for Postfix. That could be because I have Xymon installed on the same machine and therefore network latency is pretty much nil. I do have multiple expect commands in the config too, but those are not handled correctly, as you said above.
I'm mostly satisfied with the current outcome, though the pedant in me does want to see multiple expect/send pairs work correctly. If that worked, many things that currently have to be handled by external scripts could be done in Xymon through config files alone.
Thanks, Shawn