Network Status Map not displayed

[n1841]

The Network Status Map (Home --> Maps --> Network Status Map) is not displaying on our Nagios XI install. We are using the Nagios supplied VM appliance version of Nagios with the latest updates installed. The system is installed behind a firewall and does not have Internet access. It looks like the system is trying to do a get request to http://www.bin-co.com/php/scripts/load/ when the Network Status Map link is being navigated to. I have tried with the latest FireFox and IE browsers and still can't see the Network Status Map. The map page from Nagios core, works fine though.



Thanks,

John

[mguthrie]

Try resetting the security credentials for the sub-system components. Go Admin->Reset Security Credentials, and then change the passwords for the sub-system components. Sometimes errors in the graphical tools are related to sub-system permissions.

Just out of curiosity, are the performance graphs working? If so I'm going to add this to the FAQ as a related issue.

[n1841]

Try resetting the security credentials for the sub-system components. Go Admin->Reset Security Credentials, and then change the passwords for the sub-system components. Sometimes errors in the graphical tools are related to sub-system permissions.

Just out of curiosity, are the performance graphs working? If so I'm going to add this to the FAQ as a related issue.

I have tried this in the past, when the performance graphs were not working, it fixed the graphs, but not the status map.

I tried a reset security credentials again today, still no status map.

-John

[admin]

The map is part of Nagios Core, so a good place to check if its working properly on its own is to directly access it. To do this, access Nagios Core on your XI server. This is done by using the following URL:

[url]http://[serverip]/nagios[/url]

You'll be asked for a username/password - use the same ones you authenticate to Nagios XI with.

Select the "Map" option under the "Current Status" section of the Nagios Core navigation bar. Does the map display properly there?

[n1841]

The map page from Nagios core, works fine though.

Yes, it works fine in the nagios core.

[mguthrie]

Hmm.....I have broken the status maps on my test server before, but it also broke the performance graphs and basically anything that had to dynamically create an image. My issue was permissions related in the file structure, but never did track down the source, I just ended up re-installing since it was a testing box. Not sure what's causing your issue yet, we'll have to do some hunting on what would cause that....

[n1841]

Is there a reset permissions script, which goes through all of the files and resets file permissions?

[mguthrie]

Here's a script that's worked for a lot of people, but it's more for performance graph issues, not sure if it'll work for the status map but it could be worth a try.

Code: Select all

chown -R nagios.nagios /usr/local/nagios/etc
find /usr/local/nagios/etc -type d -exec chmod 775 '{}' + -o \
        -type f -exec chmod 664 '{}' +

[n1841]

The permission reset didn't help. Remember, this server is behind a firewall without any Internet access.

While going through the logs, I again notice the system trying to get out to the internet to download something when the statusmap.php page loads.
127.0.0.1 - - [19/Oct/2010:15:32:34 -0500] "POST /nagiosxi/backend/ HTTP/1.1" 20
0 812 "-" "BinGet/1.00.A (http://www.bin-co.com/php/scripts/load/)"

Do I need to download a component from http://www.bin-co.com and install it on my system before the status map will display in the XI interface? I would really like to get the problem fixed.

Update:
We have the server configured to use https, if I use http://host.name/nagiosxi and click on the Network status map, it displays fine. So what file do I need to modify, so it displays using https?

[mmestnik]

That log indecates the contents of the about section, not an active web request. It's stating it's own homepage for infermational purposes.

As for https there are a number of other users who have ventured into this area. Look on this forum for more information. You need to allow resuests to http://127.0.0.1:80/ to be accepted and not redirected or anything.