<div dir="ltr">David<div><br></div><div>Is xymond_alert running on the same server as xymond? If so, perhaps try setting XYMSRV or XYMSERVERS to 127.0.0.1 and see if that helps.</div><div><br></div><div>I'm wondering if the problem has something to do with your VM.</div><div><br></div><div>Does the xymond.log flap messages mention what test was flapping?</div><div><br></div><div>Cheers</div><div>Jeremy</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 March 2017 at 05:01, David Boyer <span dir="ltr"><<a href="mailto:davieb@gmail.com" target="_blank">davieb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Jeremy,<br></div> Yes, it returns hosts.cfg and the contents of the hosts.d directory. A little more background, as the VM is nat'd and the <br>route-able address is what is being queried and configured in the xymonserver.cfg config file. The error surfaced 9 times over night..<br><br></div>The xymond.log has a dozen or so msgs about flapping, xymonnet.log is empty. The history log just has msgs from the restarting on the server yesterday about not updating a ext test and color unchanged.<br><br></div>Thanks,<br></div>Dave<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 15, 2017 at 3:41 PM, Jeremy Laidman <span dir="ltr"><<a href="mailto:jlaidman@rebel-it.com.au" target="_blank">jlaidman@rebel-it.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On 16 March 2017 at 06:24, David Boyer <span dir="ltr"><<a href="mailto:davieb@gmail.com" target="_blank">davieb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><br></div>Anybody have any info on this error in ~xymon/server/logs/alert.log?<br><br></div>Whoops ! Failed to send message (select(2) failed)<br></div>-> Select failure while sending to Xymon <a href="http://daemon@192.168.11.100:1984" target="_blank">daemon@192.168.11.100:1984</a><br></div>-> Recipent '192.168.11.100', timeout 15<br></div>-> 1st line: 'config hosts.cfg'<br></div>Cannot load hosts.cfg from xymond, code 6<br></div>Failed to load from xymond, reverting to file-load<br></div></div></div></blockquote><div><br></div></span><div>I'm guessing this is displayed when xymond_alert asks xymond to give it the "hosts.cfg" file contents, but the xymond process is not responding at that time. The fact that you get a timeout after 15 seconds, rather than being refused, suggests that either the xymond daemon was running but wedged, or that a firewall was dropping packets so the socket could not be established in the first place. I'm not a coder, but my guess is that select(2) is called after the socket is up, and so a wedged xymond is more likely.</div><div><br></div><div>Why would xymond not respond? Perhaps high CPU load, or memory thrashing?</div><div><br></div><div>Do you see these log messages often? If it's only occasionally, are they all about the same time of day?</div><div><br></div><div>Can you run this command and see if it gives the hosts.cfg file:</div><div><br></div><div>$ /path/to/xymon 192.168.11.100 'config hosts.cfg'</div><span class="m_-1614811289657090802HOEnZb"><font color="#888888"><div><br></div><div>J</div><div><br></div></font></span></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>