Nagios Support Forum

Is it possible you ran a monitoring wizard as HTTP and are not trying to access via HTTPS? Depending on what version you are running, that could cause the port # to be wrong. If it was hand-coded, maybe the port just got messed up. It seems all of the posts on the forum with that error are somehow related to SSL not being configured properly, often it seems with multiple XI servers. Not sure if that's the case here.

Can you login to both XI servers in the GUI interface?
Can you login to both servers as root in a command prompt?
Could you PM in your Nagios XI System Profile so we can review it?
To send us your system profile. login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and PM it back to us.

I got the command to execute. Unfortunately I would have to hand type the output as there is no way to paste it here. I ran this on a working server and I see there is alot of output.

For the server that is NOT working I have:

Array
(
[hearders] => Array
(
)

[body] =>

EVERYTHING ABOVE IS EMPTY
EVERYTHING BELOW IN THE [INFO] BLOCK HAS 0 FOR THE VALUE EXCEPT [namelookup_time] => 0.0000128, [connect_time] => 0.000 555[download_content_legnth] => -1, [upload_content_legnth] => -1


[info] => Array

Any thoughts?

Looks like you might not have seen my update yesterday:

Is it possible you ran a monitoring wizard as HTTP and are not trying to access via HTTPS? Depending on what version you are running, that could cause the port # to be wrong. If it was hand-coded, maybe the port just got messed up. It seems all of the posts on the forum with that error are somehow related to SSL not being configured properly, often it seems with multiple XI servers.

Can someone at least let me know that they are no lower assisting with this post?

Didnt realize there was a page 2. Im reading now.

Can you login to both XI servers in the GUI interface? Yes
Can you login to both servers as root in a command prompt? Yes
Could you PM in your Nagios XI System Profile so we can review it? NO sandboxed
To send us your system profile. login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and PM it back to us.

On the server that is failing, take a look at the Apache log files to see if there are any errors there that can help out.
Look in /var/log/httpd folder.
Another thing to try is to create a new admin account with a new API key on the bad server and use that account when running the check.
Other than that, we will need to see more information to help out.

I have ckeck all logs in /var/log/httpd - Nothing is being printed to the log when using the new nagiosadmin's ticket. I am sure you guys with customer who can not send you their log files for various reasons. I am who cannot. The only error literally is "Could not parse XML from https://serve_name/nagiosxi/"