Nagios Support Forum

Hi All,
We are attempting to use auto-discovery scans however they fail to execute, the jobs status remains in a "waiting" state. Manual executions of the "Once" jobs works fine.

Nagios Version - 5.6.10
OS Version: RHEL 7.7
SELinux: Disabled

I did find the following post https://support.nagios.com/forum/viewto ... 16&t=54184 which mentioned changing permissions on the jobs dir, re-creating the scheduled jobs however this has failed to make a difference.


The permissions prior to this were 776 on the jobs dir, i changed to 775 which i didn't suspect to make a difference.

[nagios@monprdappla005 autodiscovery]$ ls -la
total 64
drwxr-xr-x 4 nagios nagios 115 Sep 11 2019 .
drwxr-xr-x 64 nagios nagios 4096 Sep 11 2019 ..
-rw-r--r-- 1 nagios nagios 12800 Sep 11 2019 autodiscovery.inc.php
-rw-r--r-- 1 nagios nagios 2329 Sep 11 2019 CHANGES.TXT
drwxr-xr-x 2 nagios nagios 31 Sep 11 2019 images
-rw-r--r-- 1 nagios nagios 39584 Sep 11 2019 index.php
-rwxr-xr-- 1 nagios nagios 0 Sep 11 2019 install.sh
drwxrwxr-x 2 nagios nagios 62 Sep 22 14:02 jobs
[nagios@monprdappla005 autodiscovery]$


I did find some errors in /var/log/httpd

# tail error_log
cat: write error: Broken pipe
You (apache) are not allowed to use this program (crontab)
See crontab(1) for more information
You (apache) are not allowed to use this program (crontab)
See crontab(1) for more information
You (apache) are not allowed to use this program (crontab)
See crontab(1) for more information
You (apache) are not allowed to use this program (crontab)
See crontab(1) for more information
cat: write error: Broken pipe
#

# tail ssl_error_log
[Thu Sep 24 08:42:01.764310 2020] [:error] [pid 29691] [client 10.241.160.6:55038] PHP Warning: filemtime(): stat failed for /usr/local/nagiosxi/html/includes/components/autodiscovery/jobs/pAHv9d.out in /apps/nagiosxi/html/includes/components/autodiscovery/index.php on line 286, referer: https://<hostname removed>/nagiosxi/includes/components/autodiscovery/?

FYI, issue resolved it was our SOE having a /etc/cron.allow and the apache user not being allowed to setup the scheduled jobs .

Hi,

FYI, issue resolved it was our SOE having a /etc/cron.allow and the apache user not being allowed to setup the scheduled jobs

Fabulous! Glad to hear you got it fixed and thanks for sharing the solution.

Regards,
Benjamin