HTTP ERROR 500

[rkurnik]

login.txt

[mcapra]

It looks as if Nagios Log Server as well as Nagios Network Analyzer have been installed on this machine:

Code: Select all

CORP root@nagios01:/var/log/httpd$ ls -al /var/www/html
total 24
drwxr-xr-x. 5 root root 4096 Sep 8 12:53 .
drwxr-xr-x. 7 root root 4096 Jan 5 21:57 ..
-rwxr-xr-x. 1 root root 3038 Sep 19 2015 index.php
drwxr-xr-x 5 root root 4096 Feb 15 14:30 nagioslogserver
drwxr-xr-x. 5 root root 4096 Sep 21 2015 nagiosna
drwxr-xr-x. 8 apache apache 4096 Sep 19 2015 nagiosql

This is likely causing all sorts of problems. We recommend a clean, minimal CentOS/RHEL machine for each of our products. Installing NLS on top of NNA on top of XI isn't a supported setup.

[rkurnik]

OK it has run for a year like this and all of a sudden xi starts throwing 500 errors?

[dwhitfield]

It looks like nagioslogserver was modified on Feb 15, so that could be the source of your most recent issue, so perhaps you found the perfect order when you installed them before.

Please let us know if you are still getting these 500 errors once you've installed these on three separate hosts (they can be separate VMs on the same physical host).

[stefanmadsen]

I need to chime in on this topic, I just started seeing this issue today - and strangely enough - calls to different REST services Work.
but the usual servicestatus and hoststatus results in a http500

it seems to be related to us injecting an additional 500 service checks a few days ago.
I'm wondering if the request is being cut off due to too "large" a request?

we only have a pure nagiosxi installation running on that machine - machine is far from overloaded (6core 16gb ram) - load5 is steady at ~1.5 over the last week.

[stefanmadsen]

aaand fixed.. it was simply the payload size that caused the http 500

in /etc/php.ini
set the maxmemorylimit to something higher (i bumped it from 128m to 256m)
REST calls are now working Again.

fyi: we have roughly 2500 service checks and ~250host checks

i would recommend a enhancement where we could specify which data we need extracted (~~REST parameters - or json request payload) - that would result in a smaller response payload.

[tmcdonald]

Thanks for the input stefanmadsen! @rkurnik please let us know if that resolves your issue, or if you split the products up to their own servers.

[rkurnik]

That fix did not work. I do believe what happened was SourceGuardian protected files were somehow corrupt. I backed up the currently running directory and did a fullinstall... then i move the backup back into production and the xi interface began to work.

Still confirming all is well but things are looking good. I'll work on later getting these services split onto their own vm's

[tmcdonald]

Want us to keep this open for you, or shall we consider it resolved and close the thread?