i have the same issue:
Monitor Engine Process: No data
Monitor Engine Event Queue: Scheduled Events Over Time: Error: No output from backend!
Did anyone ever solve this? For me it started after the most recent upgrade.
Search found 5 matches
- Tue Sep 29, 2015 9:57 pm
- Forum: Nagios XI
- Topic: Nagios XI GUI lost connection Monitoring Engine
- Replies: 10
- Views: 4440
- Tue Jul 22, 2014 10:28 am
- Forum: Nagios XI
- Topic: problems after upgrading to 2014R1.3
- Replies: 7
- Views: 1749
Re: problems after upgrading to 2014R1.3
Yes, ping only; there was a different issue with the host check, but that seemed to be a syntax difference which was solved by just forcing the configs to be rewritten. No, I only altered the command now to add the -4 flag. Either way, that works for now and I'll remove and re-add the existing hosts...
- Mon Jul 21, 2014 5:49 pm
- Forum: Nagios XI
- Topic: problems after upgrading to 2014R1.3
- Replies: 7
- Views: 1749
Re: problems after upgrading to 2014R1.3
It should not try ipv6 first unless it is available. I bet your server is configured to support ipv6 and for some reason the plugin tries that first even though you do not have a valid interface up running ipv6. I just tested on one of my test boxes and didn't experience the issue, so this may be u...
- Mon Jul 21, 2014 4:23 pm
- Forum: Nagios XI
- Topic: problems after upgrading to 2014R1.3
- Replies: 7
- Views: 1749
Re: problems after upgrading to 2014R1.3
Thanks, yes, I did that, but there's no IPv6 on the server, nor any quad A for the zone, so why is it trying IPv6? It shouldn't be doing that.
Either way, it's working now.
Either way, it's working now.
- Sat Jul 19, 2014 8:44 am
- Forum: Nagios XI
- Topic: problems after upgrading to 2014R1.3
- Replies: 7
- Views: 1749
problems after upgrading to 2014R1.3
We were able to upgrade to NagiosXI 2014R1.3, all works fine for existing hosts and services, but if I edit a service or add a new host with services, then the services keeps flapping: 2014-07-19 09:36:47 XXX UP HARD 1 of 5 HTTP OK: HTTP/1.1 200 OK - 79826 bytes in 0.046 second response time 2014-07...