Permissions wrong on nagios.log on fresh CentOS 7 install

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
vitkork
Posts: 1
Joined: Mon Dec 12, 2016 5:22 pm

Permissions wrong on nagios.log on fresh CentOS 7 install

Post by vitkork »

I installed Nagios Core 4.2.4 on CentOS 7 following instructions here: https://assets.nagios.com/downloads/nag ... entos7.pdf

Received error "Error: Cannot open log file '/usr/local/nagios/var/nagios.log' for reading!" When trying to view log files through the nagios web UI. Reviewed permissions on /usr/local/nagios/var/nogios.log and realised it was owned by nagios:nagios and lacked read permissions for "other". "chmod o+r nagios.log" resolved the issue.

Does this happen for other people? Is there a problem with the install script / instructions in the pdf? Was I holding it wrong? Inquiring minds want to know.
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: Permissions wrong on nagios.log on fresh CentOS 7 instal

Post by dwhitfield »

vitkork wrote:Is there a problem with the install script / instructions in the pdf?
Well, sorta...

Those instructions are for 4.1.1. For lack of a better term, 4.1.1 is our stable version. What I mean by that is that it is the version that has been tested and integrated into XI. Think of it like Fedora and RHEL. Fedora (Core) releases stable versions, but they aren't as stable as RHEL (XI).

Specifically, among other things, newer versions need perl. Instructions for the new version are available at https://support.nagios.com/kb/article.php?id=96. I just re-did our videos for compiling from source (still being edited) and I used the KB instructions. Even the KB was tested against 4.2.2 and not 4.2.4, although 4.2.4 was literally just one security fix. It just takes time to test and update the documentation.

Let us know if you have trouble running through the KB and we'll help you out with that.
Locked