birger
06-11-2008, 12:31 PM
First of all I want to apologize for not sitting down and doing a proper writeup. A jumbled mess is better than nothing, I hope. You may find the answer to your problem here somewhere.
I have just installed Centreon 2.0b3 on fedora 9, and I'll summarize the gotchas I can remember here.
I started with a clean server installation and tried to follow the instructions at http://fr.doc.centreon.com/Setup_Fedora_core_8:setup-2-fedora-core8/fr
Since I don't read french (I do read a little bit spanish, so I am able to get some nuggets of information from french as well) I mostly ran the commands listed.
One problem I discovered when I tried to do anything using the web interface is that centreon is far from clean with regard to SElinux, so start by turning selinux off. Edit /etc/sysconfig/selinux and set SELINUX=permissive to turn it off at boot, and then either reboot or run setenforce Permissive to set it for the running instance. You may as well do this before starting the installation. Typically, selinux will stop apache from writing files into places like /etc/centreon no matter what the file permissions are. A permanent fix would be for centreon to install proper selinux configurations so /etc/centreon would be writable by httpd. I leave this as a task for 'someone else'
Prerequisites
The web pages listed above are for Fedora 8. I installed on Fedora 9, but I still think there are 2 typos in the page about installation of prerequisites. The package listed as perl-crypt-DES is really called perl-Crypt-DES, and the package listed as gli2-devel should probably be glib2-devel.
After installing all prerequisites, start mysqld with the command service mysqld start and then set a password with the command mysqladmin password <password> where <password> should be substituted with the password you want. Later in the installation when the instructions say mysql -u someuser dosomething you add a -p after the username, and you will get prompted for the password. Also, make sure mysqld will start at boot with the command chkconfig mysqld on.
This would also be a good time to run chkconfig httpd on to make sure the apache web server starts automatically at boot.
Installing nagios
After following the instructions to install nagios, you should probably run chkconfig nagios on to make sure nagios starts after a reboot.
Compiling
Installing into /usr/local... may not be default Fedora behaviour, and if someone were to compile these for rpm packaging I would have taken the time to set all paths correctly for the fedora environment. For now I think it's best to go 'the beaten path' to make sure any problems I see are real problems and not my own stooopid mistakes.
Unsolved problems
I'm certain the first one is easy. Centreon doesn't restart nagios. I have to open a command window and run service nagios restart after exporting config files from centreon.
The next one has me stumped right now. I have added one windows host in addition to the predefined centreon server itself. I can see nagios alarms in nagios.log, and I can see them when browsing the log inside centreon. I can get ping graphs for both of them, but the status view still says 0 in all fields. 0 hosts up and 0 hosts down, when I have ping graphs telling me both the defined hosts are up?
I have just installed Centreon 2.0b3 on fedora 9, and I'll summarize the gotchas I can remember here.
I started with a clean server installation and tried to follow the instructions at http://fr.doc.centreon.com/Setup_Fedora_core_8:setup-2-fedora-core8/fr
Since I don't read french (I do read a little bit spanish, so I am able to get some nuggets of information from french as well) I mostly ran the commands listed.
One problem I discovered when I tried to do anything using the web interface is that centreon is far from clean with regard to SElinux, so start by turning selinux off. Edit /etc/sysconfig/selinux and set SELINUX=permissive to turn it off at boot, and then either reboot or run setenforce Permissive to set it for the running instance. You may as well do this before starting the installation. Typically, selinux will stop apache from writing files into places like /etc/centreon no matter what the file permissions are. A permanent fix would be for centreon to install proper selinux configurations so /etc/centreon would be writable by httpd. I leave this as a task for 'someone else'
Prerequisites
The web pages listed above are for Fedora 8. I installed on Fedora 9, but I still think there are 2 typos in the page about installation of prerequisites. The package listed as perl-crypt-DES is really called perl-Crypt-DES, and the package listed as gli2-devel should probably be glib2-devel.
After installing all prerequisites, start mysqld with the command service mysqld start and then set a password with the command mysqladmin password <password> where <password> should be substituted with the password you want. Later in the installation when the instructions say mysql -u someuser dosomething you add a -p after the username, and you will get prompted for the password. Also, make sure mysqld will start at boot with the command chkconfig mysqld on.
This would also be a good time to run chkconfig httpd on to make sure the apache web server starts automatically at boot.
Installing nagios
After following the instructions to install nagios, you should probably run chkconfig nagios on to make sure nagios starts after a reboot.
Compiling
Installing into /usr/local... may not be default Fedora behaviour, and if someone were to compile these for rpm packaging I would have taken the time to set all paths correctly for the fedora environment. For now I think it's best to go 'the beaten path' to make sure any problems I see are real problems and not my own stooopid mistakes.
Unsolved problems
I'm certain the first one is easy. Centreon doesn't restart nagios. I have to open a command window and run service nagios restart after exporting config files from centreon.
The next one has me stumped right now. I have added one windows host in addition to the predefined centreon server itself. I can see nagios alarms in nagios.log, and I can see them when browsing the log inside centreon. I can get ping graphs for both of them, but the status view still says 0 in all fields. 0 hosts up and 0 hosts down, when I have ping graphs telling me both the defined hosts are up?