We've had a similar problem with another service. Looking at the xymonnet man page, there doesn't appear to be a general timeout (http, yes, but not generally). I use an expect script (as an external test) where I can spawn a process (in this case the ldap call). I set a timeout in expect, so if the spawned connection hangs, the timeout triggers and terminates the connection.
From: Xymon <xymon-bounces at xymon.com> on behalf of John Thurston <john.thurston at alaska.gov> Sent: Thursday, September 20, 2018 7:48:59 AM To: xymon at xymon.com Subject: [Xymon] xymonnet blocking
We've run xymon for years, and BB for years before that. We've recently bumped into a potential problem with xymonnet. In the middle of the night, all of our tests populated by xymonnet went purple. We think we've tracked the problem, and attribute it to an ldap query which took too long to respond. It looks like xymonnet just stopped while it waited for this query to complete. While it was waiting on this response, none of the other xymonnet tests were being performed.
The man for xymonnet indicates there is a --timeout=N which determines how long to wait for a service to accept a connection. Is there some parameter which will control how long xymonnet can try to get an answer after connecting?
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon<http://lists.xymon.com/mailman/listinfo/xymon>