On Fri, July 13, 2012 04:38, John Horne wrote:
On Fri, 2012-07-13 at 14:45 +1000, Jeremy Laidman wrote:
How long did you wait between the reboot and restarting Xymon?
On Thu, Jul 12, 2012 at 7:35 PM, John Horne <john.horne at plymouth.ac.uk> wrote:
Using Xymon 4.3.7 I have noticed that if I reboot the Xymon server then the 'conn' test fails for all the clients. E.g.: ============================ Thu Jul 12 10:24:11 2012 conn NOT ok Service conn on dns1 is not OK : Host does not respond to ping System unreachable for 5 poll periods (984 seconds) ============================ If, from the server, I run 'ping' to the client then that works fine. So does fping. If I stop then start the Xymon service on the server then the client conn tests all report ok.Hello,
I have waited various amounts of time, from as soon as I could log in (about a minute or two since rebooting), up to about an hour.
I should have added that after a reboot, and when the conn tests are red, then they stay red! Yet the clients are all up and running, and are pingable. At what time I restart Xymon seems to make no difference, once it is done then the tests start to turn green.
I can only assume that there is some initial condition which causes the ping to fail, but that it remains in force until Xymon is restarted. Very odd. I will investigate, but am a little lost as to why, say after 5, 10, 60 (!) mins, the tests do not automatically turn green.
I added 'trace' to one client in hosts,cfg, and it shows the traceroute working fine but the test is still red and saying the ping failed.
Just a WAG: could Xymon be getting started before the network interfaces and be locked onto localhost as a route, or in some other ambiguous networking state? How's it getting started at boot?