Bug 1330627 - Error: Could not read object configuration data!
Summary: Error: Could not read object configuration data!
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nagios
Version: epel7
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Keiran Smith
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2016-04-26 15:25 UTC by Brian J. Murrell
Modified: 2017-02-22 14:50 UTC (History)
9 users (show)

Fixed In Version: nagios-4.2.4-2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-02-22 14:50:28 UTC
Type: Bug

Attachments (Terms of Use)

Description Brian J. Murrell 2016-04-26 15:25:11 UTC
Description of problem:

Error: Could not read object configuration data!

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install nagios
2. Go to http://server/nagios

Actual results:

Error: Could not read object configuration data!

Here are some things you should check in order to resolve this error:

Verify configuration options using the -v command-line option to check for errors.
Check the Nagios log file for messages relating to startup or status data errors.
Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.

Expected results:
Should get minimal (at least) working configuration.

Additional info:
Admittedly, I have just installed nagios and done zero configuration.  But one really ought not to have to do anything to get at least minimal functionality of monitoring the host that it was installed on.  Clearly branching out from there will need additional configuration.

Is "out of the box" functionality supposed to work or is it expected that one has to do some amount of configuration?  If the latter, there ought to be a Fedora supplied README guiding one through that minimal configuration.

For good measure:

# sudo -u nagios nagios -v /etc/nagios/nagios.cfg
Nagios Core 4.0.8
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-12-2014
License: GPL

Website: http://www.nagios.org
Reading configuration data...
   Read main config file okay...
   Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
        Checked 8 services.
        Checked 1 hosts.
        Checked 1 host groups.
        Checked 0 service groups.
        Checked 1 contacts.
        Checked 1 contact groups.
        Checked 24 commands.
        Checked 5 time periods.
        Checked 0 host escalations.
        Checked 0 service escalations.
Checking for circular paths...
        Checked 1 hosts
        Checked 0 service dependencies
        Checked 0 host dependencies
        Checked 5 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check

Comment 1 Brian J. Murrell 2016-04-26 16:05:51 UTC
Seems I had to "systemctl start nagios", which is fair enough, except that I didn't know I had to do that.

Comment 2 Fedora Update System 2017-02-07 23:47:08 UTC
nagios-4.2.4-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-0f3297a19b

Comment 3 Fedora Update System 2017-02-09 21:17:56 UTC
nagios-4.2.4-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-0f3297a19b

Comment 4 Fedora Update System 2017-02-22 14:50:28 UTC
nagios-4.2.4-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.