Page 2 of 3
Re: Unable to parse response
Posted: Wed Mar 25, 2015 9:46 am
by tmcdonald
You might try doubling that to 20.
Also, the php settings on the remote system could have an effect as well if they are taking a long time to run. What settings do you have on the affected server?
Re: Unable to parse response
Posted: Wed Mar 25, 2015 11:16 am
by vAJ
Remote system is as follows:
Code: Select all
memory_limit = 1024M
max_execution_time = 240
max_input_time = 60
default_socket_timeout = 60
Re: Unable to parse response
Posted: Wed Mar 25, 2015 1:22 pm
by ssax
When the issue is occurring, you may want to see what the output of this page is:
Code: Select all
http://XISERVER/nagiosxi/backend/?cmd=getservicestatus&combinedhost=true&brevity=1
This is the page that fusion calls for it's service data, it seems yours is returning invalid XML data when grabbing the service data.
Make sure to replace XISERVER with you problem XI server.
Let us know what you see.
Re: Unable to parse response
Posted: Wed Mar 25, 2015 2:00 pm
by vAJ
Wow. That page takes FOREVER to return on that instance. Matter of fact, the XML returns hosts that have not been valid on this system for years.
Where does this data come from? The MySQL database? I'm thinking we have some serious stale data there.
Hah. And Chrome just errored with "Out of Memory" and wanted to close...
Re: Unable to parse response
Posted: Wed Mar 25, 2015 2:05 pm
by vAJ
I take that back. Those checks do exist. But I can't post the response here. Too much company and customer information that I'm not allowed to post publicly.
Re: Unable to parse response
Posted: Wed Mar 25, 2015 2:12 pm
by vAJ
Every time I hit that URI, chrome crashes:
HesDeadJim.JPG
Re: Unable to parse response
Posted: Wed Mar 25, 2015 2:57 pm
by vAJ
Was just looking at some of the known verbose tables in the mysql DB:
Code: Select all
[root@nagios ~]# mysql -u ndoutils -pn@gweb nagios -e 'SELECT COUNT(*) from nagios_notifications'
+----------+
| COUNT(*) |
+----------+
| 267463 |
+----------+
[root@nagios ~]# mysql -u ndoutils -pn@gweb nagios -e 'SELECT COUNT(*) from nagios_logentries'
+----------+
| COUNT(*) |
+----------+
| 2663969 |
+----------+
Re: Unable to parse response
Posted: Wed Mar 25, 2015 2:58 pm
by vAJ
And I'm happy to have you guys move this to the XI forum instead. Or we can spin this off to a private support ticket.
Re: Unable to parse response
Posted: Wed Mar 25, 2015 4:56 pm
by lmiltchev
And I'm happy to have you guys move this to the XI forum instead. Or we can spin this off to a private support ticket.
This should be fine. Email us at
[email protected]. Type "Unable to parse response" in the subject and provide a URL link to this post in the email body.
Re: Unable to parse response
Posted: Wed Mar 25, 2015 5:00 pm
by vAJ
Man, that's a lot of data to be asking every 10 seconds. There has to be a better way to flow data to Fusion.
At this point, I'm thinking rolling all of my monitoring into one XI instance with a larger gearman deployment would give us better NOC Ops Center performance. Fusion seems to be a better solution for multi-tentant situations.