Event Data Stops

[SeanFromIT]

Starting yesterday, the XI System Component "Event Data" has been showing red (!). I restarted the server yesterday and the (!) went away, but it came back today. What could cause this?

[tonyyarusso]

I don't know the cause myself, but I'm told this is a now-known bug, and a patch will be coming shortly.

[SeanFromIT]

Thanks. I'm running Nagios XI 2009R1.4B. Other errors are creeping up while Event Data is in (!) state:

Network Outages widget -

Code: Select all

Error: Unable to parse XML Output! Monitoring engine may be stopped.

CCM -

Code: Select all

Error while connecting to database:
[localhost] Connection to the database server has failed by reason:
Too many connections

And while it starts with Event Data, several other XI components go red (!) within 6 hours:
Command Subsystem
Event Manager
Feed Processor
Report Engine
System Statistics

[mguthrie]

Thanks for this data, we'll have our lead developer look at this. We created a patch for the Event Data issue, but I'd like to make sure this isn't an additional issue that is outside of what was patched.

[markhoulihan]

We are too experiencing this since upgrading to the latest version. The only thing we changed on our system was the Timezone and I thought that caused this error until seeing this post. Has the patch been released?

Latest Available Version: 2009R1.4B
Installed Version: 2009R1.4B
Last Update Check: 2011-03-02 17:10:22

[mguthrie]

Are you guys running a lot of passive checks on your system? We're working on tracking down an event data issue at the moment and so far it's been showing up on systems with a lot of passive checks.

We did get a patch made for 1.4B, but we're wondering if there's more to the issue, we'll get something posted ASAP.

[SeanFromIT]

We use all active checks. Please post a link to the patch when available.

[rdedon]

This is being worked on today and I am noting this thread for an update ASAP for when we complete it.

[markhoulihan]

Yes .. confirming all active checks also

[markhoulihan]

Sorry was meaning to add

I suspect ours was started by altering the timezone to the correct city we are located in. Scouring around some other nagios forums it looks like maybe the SQL backend might have issues with certain timezones but that is just a stab in the dark. The timezone was updated and then not long after we updated to 2009R1.4B and this is when the Event Data Stale errors appeared. We are located Brisbane, Australia GMT +10 but no daylight savings. The Event data always says it is out 1hr and about 40 secs and daylight savings time is +1 hr so figured might be related to that.