In your tasks.cfg, try "MAXTIME 10m" to the "[xymonnet]" block. Alter the "10m" to your taste. Probably something shorter than your STATUSLIFETIME.
Dave
On Wed, 19 Sep 2018, John Thurston wrote:
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?