Nagios Support Forum

I have a new NagiosXI installation on RHEL5 32b. Everything seems to have installed OK, however it appears that the Config Manager is not setup.
If I select any of the options in the Alerts Menu - nothing is displayed - I would expect to be able to add an entry?
When I select Write files to update Nagios, none of the .cfg files are copied to the etc folder.
When I try to add a host using the wizard, it allows me to add all the new info but when I try to apply the configuration, it would stay on the Verifying Configuration stage forever ( adding a dot to the screen continuously).
As others seem to have had problems with the d/bases - I checked that both mysql & postgresql are running OK.
I have tried running the 3-dbservers script again to see if there are any errors displayed.
Now when I try to add a host it gives this error SQL: SQL Error [nagiosxi] : ERROR: duplicate key violates unique constraint "xi_commands_pkey"
I have tried this install twice now on different clean servers and have the same problem with CCM - What do I need to do to get this working.



regards... Fred

Hi Fred -

It sounds like the CCM has a problem, or didn't quite get installed properly.

One way to verify this is to try and directly access NagiosQL using this URL:

http://[your_nagiosxi_ip]/nagiosql

See if you can access it directly without problems. You might want to also watch the Apache error log for error messages coming out of NagiosQL:

Hi - pointing my browser at http://[my_nagiosxi_ip]/nagiosql displayed a blank page - no errors.
the apache log file didn't offer much either apart from Is there anything else I can check?
regards.... Fred

Have you recently checked if you can do a manual install on a fresh RHEL 5.5 server?
I've just tried a new install again and this time found that I can't connect to the dag repo anymore - I'm pointing to a mirror and that appears to work OK - baseurl=http://rh-mirror.linux.iastate.edu/pub/ ... search/dag

and the epel rpm in the 1-prereqs script is pointing to a wrong version epel-release-5-3 - had a look in that repository and it's version 5.4

Even after these changes - I still can't get CCM to work - still the symptoms described above.

Fred

No we havn't. It's impractical for me to comment without knowing the cause, though I should warn that we can't be responsible for "service pack" releases that cause system instabilities. Try seeking assistance from the vendor of the repositories.

We will attempt to maintain compatibility with the current service packs, but we will always lag far behind. The best advice is to test any service packs before you apply them. In the case of repositories, well the only solution would be to keep a local mirror or use a mirror that's more resilient to change/breakage. We have no plans nor will ever consider running a repository, it's simply not part of our business model.

Making RH aware of these issues would be a great help, they should know how to help correct these types of problems.

I'm not sure that you understand.
I have a fresh install of plain RedHat 5.5 - Your installation scripts *do not work* ! They reference non-existent rpm's.
You provide the installation scripts for manual installs - I expect them to work.
You have certified that this product works on RedHat 32bit - I can't get it to work.

The URL to the EPEL rpm just changed recently, and for some reason the EPEL repository administrators are not properly maintaining it, making our URL broken. We will update the link for future users, but it is certainly not our fault that it broke. A proper mirror would maintain the old file in place, or at the very list apply an HTTP redirect. Just deleting it means that all sorts of products such as ours are going to be broken, but such is life in RPM-land apparently.