The upgrade to Upgraded to 2014R1.0 went well.
Now in the 'Tactical Overview'/'Network Outages' we get "Error: Unable to parse XML output! Monitoring engine may be stopped. Check engine"
---
Everything else is fine.
---
In /var/log/httpd/error_log I keep getting:
PHP Warning: simplexml_load_string(): ^ in /opt/nagiosxi/html/includes/components/xicore/ajaxhelpers-tac.inc.php on line 29, referer: https://myhost/nagiosxi/includes/compon ... re/tac.php
Edit: I have all green checkmarks up in the 'System Ok' area and in 'System Status' screen.
Unfortunately the "Monitoring Engine Status" page reveals the "Monitoring Engine Process" is dead and will not start.
Also clicking on "Schedule an immediate check" results in 'error occurred processing your request'.
Mod Note: Please edit your previous post to add new information if you are the last poster, thank you.
Upgraded to 2014R1.0: 'Network Outages' Unable to parse XML
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
Are you forcing SSL in your Nagios XI installation? We have seen this as a cause and have a fix for that.
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
All links to my NagiosXI installation go to HTTPS.
(The previous NagiosXI upgrades had no issue with this....)
I have restored back to the 2012R2.9 version.
--
I am interested in knowing what the fix is so I can go to the current version.
(The previous NagiosXI upgrades had no issue with this....)
I have restored back to the 2012R2.9 version.
--
I am interested in knowing what the fix is so I can go to the current version.
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
Patch did not help.
During the restore back to the 2012R2.9 version there are errors at the end:
------------
Restoring PostgresQL databases...
SET
.
.
CREATE INDEX
WARNING: no privileges could be revoked for "public"
REVOKE
WARNING: no privileges could be revoked for "public"
REVOKE
WARNING: no privileges were granted for "public"
GRANT
WARNING: no privileges were granted for "public"
GRANT
Restarting database servers...
.
During the restore back to the 2012R2.9 version there are errors at the end:
------------
Restoring PostgresQL databases...
SET
.
.
CREATE INDEX
WARNING: no privileges could be revoked for "public"
REVOKE
WARNING: no privileges could be revoked for "public"
REVOKE
WARNING: no privileges were granted for "public"
GRANT
WARNING: no privileges were granted for "public"
GRANT
Restarting database servers...
.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
This would be normal on the restore, lets work this from one thread, please make follow-up items here and not on the other thread.atuttle wrote: During the restore back to the 2012R2.9 version there are errors at the end:
------------
Restoring PostgresQL databases...
SET
.
.
CREATE INDEX
WARNING: no privileges could be revoked for "public"
REVOKE
WARNING: no privileges could be revoked for "public"
REVOKE
WARNING: no privileges were granted for "public"
GRANT
WARNING: no privileges were granted for "public"
GRANT
Restarting database servers...
.
I did post this on the other thread but
@atuttle - what "Network Outages" message and "Monitoring Engine Status" failure were you seeing?
Also, It should be noted that the "patch" procedure would be done AFTER a successful upgrade to 2014 (that only had the improper "Network Outages")
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
In each effort to upgrade from 2012R2.9 to 21014 the upgrade appeared successful.
However:
In the "Tactical Overview" screen the "Network Outages" section would have the 'Cannot parse XML..." error in red.
Searching for a way to resolve that seem to be what led to getting referred to the patch mentioned earlier.
--
The MAJOR problem on each upgrade attempt was that the Monitoring Engine was broke but nothing on the home screens indicated this, everything showed green. Even in System Status.
--
Going to Admin/Monitoring Engine Status revealed the failure, and I could not start the monitoring engine.
Lucky the restore process works.
(Good to know the postgress restore errors are normal.)
Do you have any ideas on what I should be looking for?
However:
In the "Tactical Overview" screen the "Network Outages" section would have the 'Cannot parse XML..." error in red.
Searching for a way to resolve that seem to be what led to getting referred to the patch mentioned earlier.
--
The MAJOR problem on each upgrade attempt was that the Monitoring Engine was broke but nothing on the home screens indicated this, everything showed green. Even in System Status.
--
Going to Admin/Monitoring Engine Status revealed the failure, and I could not start the monitoring engine.
Lucky the restore process works.
(Good to know the postgress restore errors are normal.)
Do you have any ideas on what I should be looking for?
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
First of all, how are you forcing ssl? Through rewrites rules, redirects, or disabling the virtualhost on port 80?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
As described in the document from Nagios: Configuring_SSL_with_Nagios_XI.pdf
Re: Upgraded to 2014R1.0: 'Network Outages' Unable to parse
Are you using Mod gearman or mk-livestatus? Did ndo2db upgrade to 2.0.0?
Code: Select all
/usr/local/nagios/bin/ndo2db | head -2Be sure to check out our Knowledgebase for helpful articles and solutions!