alert history unavailable on nagios1.private.releng.scl3.mozilla.com

RESOLVED FIXED

Status

RESOLVED FIXED
a year ago
a year ago

People

(Reporter: arich, Assigned: ryanc)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
This might also apply to the mdc1 server, but I can't get to the web interface of that to check (will file a separate bug for that if one isn't already on file).

https://nagios1.private.releng.scl3.mozilla.com/releng-scl3/cgi-bin/history.cgi?host=all

Error: Cannot open log file '/var/log/nagios/nagios.log' for reading!
Assignee: nobody → rchilds
This appears to be a bug introduced with Nagios 4 [1]. The nagios log is being created 0600 instead of the old standard of 0644 so httpd cannot open the log. I have manually chmod'ed the log to 0640 and it can now be read, for at least the next few hours until the log is rolled again.

TLDR; We'll need to Nagios 4.3.0 to be released in epel for a permanent fix but we may be able to get a cron job to change the permissions after log rotate, for now. Will follow with ryanc about this option.

[1] - https://github.com/NagiosEnterprises/nagioscore/issues/303
(Assignee)

Updated

a year ago
Status: NEW → ASSIGNED
(Assignee)

Comment 2

a year ago
Created attachment 8885886 [details]
diff1

Here's proposed stanza for this.
(Assignee)

Comment 3

a year ago
Fix is as easy as that,

https://github.com/NagiosEnterprises/nagioscore/commit/d2481ed02e2ab64f83b6e9a43a65c74e791d343e

Committed in a5e82859fc46e6b8e102f14bd0cbe5e079961616 as
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.