Nagios Support Forum

Hello,

Is there any information on installing XI on CentOS7? The only manual install docs I find are these:
http://assets.nagios.com/downloads/nagi ... ctions.pdf

And it's only for CentOS 6.

I found tis article stating from R2.0 release stating that it should work, but I can't find any information about it.
http://www.nagios.com/news/company-news ... 0-released
I'm renting a Linode server and was hoping to do some tests wit XI ont CentOS 7 on it. It might be worth noticing that the server has Apache, MariaDB and PHP installed.

Grtz

Willem

I can only give you the minimal experience I have had with installing Nagios "manually". Those instructions are really useless for what you're trying to do.

I installed Nagios on a server that I did not want all the 32 bit software removed from, so I performed "surgery" on the installation scripts and utilized some manual processes to make it work. This server also had MySQL, Apache, and PHP installed and I didn't want them "blown up". This was not, by the way, intended to be a production server, so I was willing to accept the risks.

What I found is that the installer is broken up into individual scriptlets responsible for the installation of various components of Nagios. If you spend a couple of hours tracing through them, you'll see the logic behind their construction and how the commercial installer builds and configures everything. What you're going to have to do is "map" the processes in those scripts to their equivalents in Centos 7. I've only limited experience with Centos 7, but found it very different from Centos 5/6. Essentially, if you know the major differences between Centos 6 and 7, you should be able to pick out those portions of the process where a modification of the installer is required.

You can also try a "brute force" approach where in you take the structure of a Centos 6 Nagios installation and replicate it on the Centos 7 box. You will still need to build the Nagios components, but if you look at a Centos 6 installation, you'll know what each of them is. Again, examining the existing installers will tell you when YUM is being used, when components are being compiled, etc. It's tedious, but it does work if you're willing to put in the time.

That said, I would guess the biggest difference is how processes are started and stopped. This is based only on my own brief experience with Centos 7 however.

mp4783 wrote:Those instructions are really useless for what you're trying to do.

This should not be the case anymore. The current XI installer should support CentOS/RHEL 7 just fine. I just tested it last week on a CentOS 7 box myself. I am unsure if Linode will present any unique issues, but I can confirm that the current installer should work just fine on CentOS 7, including the new init systems and all.

Andy,

Good to know. I'll test this in the coming weeks and will report if everything went smooth.

Grtz

Willem

Great. Best of luck!

I just installed NagiosXI 2014R2.7 on CentOS 7 and it went fairly smooth. The only issue now is NagiosXI has an alert stating the database backend is not running, when in fact it is.

My guess is the dashboard is looking for MySQL and CentOS only provides MariaDB.

belvdr wrote:I just installed NagiosXI 2014R2.7 on CentOS 7 and it went fairly smooth. The only issue now is NagiosXI has an alert stating the database backend is not running, when in fact it is.

My guess is the dashboard is looking for MySQL and CentOS only provides MariaDB.

That's exactly it, and I believe this has been fixed in a developer revision. Will post back to confirm.

Update: How are you confirming that the backend is in fact running? It appears to just be checking the output of "/etc/init.d/ndo2db status" which itself would not care about mysqld vs mariadb.

I was able to install Nagios XI on my Linode CentOS 7 server with a LAMP stack on it for my website (http://outsideit.net) Are there any guidelines about exposing a Nagios XI server to the Internet? Is there a way to limit access only from certain ip addresses to http://outsideit.net/nagiosxi?
It seems like I do have some issue, that only started after rebooting the server. All my services are shown 4 times in the XI gui. In the CCM they are only visible once. What could cause this?

Grtz

Willem

WillemDH wrote:Are there any guidelines about exposing a Nagios XI server to the Internet?

Our guidelines are that it's not a good practice. Think of this no different than the rest of your pieces of management software. Can you access https://vcenterserver from the Internet? How about https://HPSIM or https://DellOpenManage? That said, if you must - just be sure to enable SSL:

https://assets.nagios.com/downloads/nag ... s%20XI.pdf

WillemDH wrote:Is there a way to limit access only from certain ip addresses

Something like: I'm at home now so I can't really test, fiddle with it to suit your needs, and don't forget if you've already put in a standard rule (NagiosXI does this for you) to allow all traffic, you'll have to remove that one for this to really do anything.

Hey Jdalrymple,

There is no production data or anything critical on it. It's more for testing and dev purposes in my private time. I'll see if I can configure SSL on it. For limiting access only from a few ip's I was more looking for something like .htaccess control, as described here => http://premium.wpmudev.org/blog/limit-a ... ogle.be%2F

Did you ever see the duplicate services in the XI gui before?
(by the way you can move this to general support forum if you want as these questions do not apply to our licensed XI server)

EDIT: So I tried putting a .htaccess file in /usr/local/nagiosxi/html but it does not seem to have any effect. I'm guessing this was just to easy..
EDIT 2: Ah the .htaccess file for nagiosxi is in fact /etc/httpd/conf.d/nagiosxi.conf

So I updated it with
Tested it and it works, I can only access the Nagios XI gui at http://outsideit.net/nagiosxi from my home ip. I have a dynamic ip but it generally stays the same for 3-4 months, so I should be good.

Now I just need to get this duplicate services fixed.

Grtz

Willem