Nagios Support Forum

Hi all,

I am trying to get a proof of concept running. While building up the config locally I stupidly I imported 10 hosts (more than 7 that you are allowed with the eval version)
After the conversion and improting the VM into vsphere the Nagios vm continues to monitor hosts and send out notifications. However the Web interface is not working correctly. Its almost like the WebService isnt reading the configuration files because it doesnt see the hosts within the hostgroups. Additionally I have deleted 3 of the 10 hosts to drop back below the license threwshold but the GUI is reporting 10 hosts still. When I navigate to /usr/local/nagios/etc/hosts/ Only 7 host config files show up. and when I view the Hostgroups.cfg Only 7 hosts appear.
I have tried multiple reboots and restarts of the monitoring engine, backend database and performance grapher, which hasnt made a difference.

Any help to resolve this would be very well received. As soon as I can show my management a funtioning Nagios server I am confident we will be purchasing a license (maybe even 2)

Thanks in advance

Joe

When you go to the Core Config Manager->Monitoring->Hosts, how many hosts do you see? Can you go to: Admin->System Config->License Information and post a screenshot of this screen?

Hi,

Thanks for the reply.
In, Core Config Manager->Monitoring->Hosts there are 7 hosts.

Admin->System Config->License Information Screenshot is below

So it looks like the number of hosts isnt the problem? But for some reason none of the hosts show up in any view

This is likely a database problem, run the following from the command line

Hi Scott,

Thank you very much, this has fixed it.
Am I correct in saying that for the remainder of the 60 days I can add more than 7 hosts. Or am I playing with fire again.

Joe

Actually, the evaluation version allows unlimited hosts, however after the trial period expires, it will disable access to view them all if a license isn't entered.

The problem you experienced was most likely caused by the VM being shutdown abruptly without shutting down the OS in the VM first.

MySQL doesn't like "power failure" when it is writing to disk, and if the VM gets stopped while it is running it is the equivalent to a power failure.