Yet Another "Error: Could not read object configuration


Hola, recent reader and first time poster.

This spot seems to be the place for Nagios help. Sorry to have to post, but while nagios docs/google/searching this forum has been helpful, my problem persists.

Red Hat 9

My install order was as follows:

All compiles/installs proceeded without error.
I attempted make cleans for each and went over my install twice.
I can provide full install logs if needed for each step.

I’ve attached the following in the txt file (since I can’t upload a collected archive):
snippet of my apache httpd.conf
terminal log of my nagios -v tests, access_log, nagios log, ps -ef|grep nagios

This is a Red Hat 9 install so selinux is not present from my searches (was really hoping that was it).

I’ve stripped out my authentication requirements till I have the basics working.

I can successfully run all of my plugins via the command line. I can provide results upon request.

Yet I still have the classic "Error: Could not read object configuration data!"
error on every cgi link present.

I believe my access_log shows the cgi request being processed and all of my tests have proved fruitless in locating the issue.

Would certainly any assistance people can render. If you need more logs/tests/etc I’d be happy to provide them.



You posted nagios.cfg twice and did not include your minimal.cfg in the .txt file uploaded here.

But try this.
cd /usr/local/nagios/sbin
ldd status.cfg => /usr/lib/mysql/ (0x0011d000) => /lib/tls/ (0x008a9000) => /lib/ (0x03655000) => /lib/ (0x006aa000) => /lib/tls/ (0x009d4000) => /usr/lib/ (0x00397000)
/lib/ (0x00890000)

What did you get for output?


My apologies on missing the minimal.cfg

I’m assuming you wanted me to list the object links to an example cgi.

[[email protected] sbin]# pwd
[[email protected] sbin]# ldd status.cgi => /lib/ (0x40024000)
/lib/ => /lib/ (0x40000000)
[[email protected] sbin]#

It certainly seems I’m missing most of the object files that should be linked to that.

I’ve attached my minimal.cfg (as a .txt) to this response.



One thing I see, is
obsess_over_service 1
Why? Have you defined an ocsp_command also?


This determines whether or not Nagios will obsess over service

checks and run the ocsp_command defined below. Unless you’re

planning on implementing distributed monitoring, do not enable

this option. Read the HTML docs for more information on

implementing distributed monitoring.

Values: 1 = obsess over services, 0 = do not obsess (default)

That may well be your problem, since after a service check is performed, it then wants to run the ocsp_command, of which, I don’t think you have one defined.


Gave that a try. No dice.

Changed obsess_over_service 1 to 0
Same issues.

Are there any other logs checks I can perform to hunt down this problem? I’m half tempted to just try a another box with a different linux distro and going from top to bottom again.

I appreciate your help, I know looking over all the info I sent is quite time-consuming.


The permissions on the files may not be correct then. Check them and report what they are.
ls -la /usr/local/nagios
ls -la /usr/local/nagios/sbin



I believe I already loosened these alot to see if it was a permissions error.

[[email protected] nagios]# ls -la
total 32
drwxrwxrwx 8 nagios nagios 4096 Sep 15 15:24 .
drwxr-xr-x 16 root root 4096 Sep 16 10:55 …
drwxrwxr-x 2 nagios nagios 4096 Sep 16 14:36 bin
drwxrwxr-x 2 nagios nagios 4096 Sep 19 11:46 etc
drwxrwxrwx 2 nagios nagios 4096 Sep 16 14:49 libexec
drwxrwxr-x 2 nagios nagios 4096 Sep 16 14:36 sbin
drwxrwxr-x 9 nagios nagios 4096 Sep 16 14:36 share
drwxrwxr-x 4 nagios nagios 4096 Sep 22 09:58 var
[[email protected] nagios]# cd sbin
[[email protected] sbin]# ls -la
total 2108
drwxrwxr-x 2 nagios nagios 4096 Sep 16 14:36 .
drwxrwxrwx 8 nagios nagios 4096 Sep 15 15:24 …
-rwxrwxr-x 1 nagios nagios 159456 Sep 16 14:36 avail.cgi
-rwxrwxr-x 1 nagios nagios 160620 Sep 16 14:36 cmd.cgi
-rwxrwxr-x 1 nagios nagios 121472 Sep 16 14:36 config.cgi
-rwxrwxr-x 1 nagios nagios 178764 Sep 16 14:36 extinfo.cgi
-rwxrwxr-x 1 nagios nagios 129056 Sep 16 14:36 histogram.cgi
-rwxrwxr-x 1 nagios nagios 108480 Sep 16 14:36 history.cgi
-rwxrwxr-x 1 nagios nagios 105088 Sep 16 14:36 notifications.cgi
-rwxrwxr-x 1 nagios nagios 104324 Sep 16 14:36 outages.cgi
-rwxrwxr-x 1 nagios nagios 104000 Sep 16 14:36 showlog.cgi
-rwxrwxr-x 1 nagios nagios 157732 Sep 16 14:36 status.cgi
-rwxrwxr-x 1 nagios nagios 124544 Sep 16 14:36 statusmap.cgi
-rwxrwxr-x 1 nagios nagios 118624 Sep 16 14:36 statuswml.cgi
-rwxrwxr-x 1 nagios nagios 104448 Sep 16 14:36 statuswrl.cgi
-rwxrwxr-x 1 nagios nagios 125248 Sep 16 14:36 summary.cgi
-rwxrwxr-x 1 nagios nagios 121860 Sep 16 14:36 tac.cgi
-rwxrwxr-x 1 nagios nagios 133696 Sep 16 14:36 trends.cgi
[[email protected] sbin]#

I’m really starting to think this is more related to my apache setup than Nagios.

I’ll try a fresh install on another machine that I have and see how that goes as well. I’ll make sure to log it from top to bottom and see what I can come up with.

Again, I certainly appreciate all the help that has been provided. I’ll make sure to post the results of my next forray into the wild blue yonder.



Ok so I gave up on my last installation and simply located another box.

Ran through my exact same install process, and everything worked fine.

Sorry to take up so much of your time Jakked, I certainly appreciate the help. I’m just going to chalk up that one to gremlins. Mostly likely gremlins involving my cgi setup on the previous machine.

Such is life.