Nagios Support Forum

You guys fixed this for me before but I cant find/remember the ticket

getting a HTTP ERROR 500 when trying to open the /objects/services API page

The others are fine

I think it was a timeout setting somewhere or something like that?

I would guess that the setting was changed could of been a a PHP settings or an Apache settings
Lets see if you can capture any errors.

Run this in a root shell.

tail -f /var/log/httpd/*_log

Then run your API call and post all of the output from the tail command so we can check it for errors.

The logs are vast for this - I did a tail -n 10 instead if that helps?

PM ed the results to you

Sorry, the data did not provide any information in the issue for the API.

I am going to have to see all of the data or you can search through the files for the 500 error and see if you can figure it out.

Zip it up if it is too big.

Sorry - I've sent the full ones gathered since yesterday - I clicked a URL a good few times so there should be something in there

Thanks

I see the 500 error on the log files now but they do not have any details on what is causing the error.
How many Hosts and Services is the server monitoring?

First, upgrade XI to the latest version.
Run the manual XI upgrade from the instructions in this document.
https://assets.nagios.com/downloads/nag ... ctions.pdf

Login to the XI interface and go to the Admin > System Settings menu and verify the Program URI is correct.

If the upgrade fails, get the following configuration files and post them. Thanks

Hi OP,

We hit up against the same issue. We had to increase the PHP memory_limit. Here's what they told me. Basically in /etc/php.ini find "memory_limit" increase it & restart httpd. Hope this helps.

"
There isn't a maximum, however you are likely hitting a php memory_limit

edit /etc/php.ini and increase the memory_limit
CODE: SELECT ALL
memory_limit = 256M


restart httpd
CODE: SELECT ALL
service httpd restart
"

Yes @Maxwellb99, that's exactly it!

Thanks!

Thanks @Maxwellb99!

@optionstechnology, is it safe to close this topic now, and mark it as resolved?

yup