Poller not running

[gwakem]

I came in this morning to discover that fusion's poller service stopped about three days ago. This is on a rhel 6.7 system.

Is there a way I can restart the poller? Output from the poller.log looks like this:

(Before I changed tidy.ini from module.so to mcrypt.so)

Code: Select all

PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/module.so' - /usr/lib64/php/modules/module.so: cannot open shared object file: No such file or directory in Unknown on line 0
Saving Tac Data to DB: XI
PHP Notice:  Undefined index: query in /usr/local/nagiosfusion/html/includes/utilsx.inc.php on line 80
PHP Fatal error:  Call to undefined function tidy_repair_string() in /usr/local/nagiosfusion/html/includes/utils-tacdata.inc.php on line 418

(After)

Code: Select all

PHP Warning:  Module 'mcrypt' already loaded in Unknown on line 0
Saving Tac Data to DB: XI
PHP Notice:  Undefined index: query in /usr/local/nagiosfusion/html/includes/utilsx.inc.php on line 80
PHP Fatal error:  Call to undefined function tidy_repair_string() in /usr/local/nagiosfusion/html/includes/utils-tacdata.inc.php on line 418

[gwakem]

Ahh.. a "service htcacheclean restart" seems to have done it. The service was dead.

[lmiltchev]

Can you run the following commands, and show the output?

Code: Select all

ps -ef | grep [p]oller
ps -ef | grep [c]ron
cat /etc/php.d/tidy.ini
tail -20 /var/log/cron
chage nagios -l
sestatus

[gwakem]

Here you go:

Code: Select all

15:42:09 [root@fusion ~]# ps -ef | grep [p]oller
15:43:37 [root@fusion ~]# ps -ef | grep [c]ron
root     11111     1  0 15:42 ?        00:00:00 crond
nagios   11178 11177  0 15:43 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosfusion/cron/cmdsubsys.php > /usr/local/nagiosfusion/var/cmdsubsys.log 2>&1
nagios   11179 11178  0 15:43 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosfusion/cron/cmdsubsys.php
nagios   11180 11176  0 15:43 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosfusion/cron/eventman.php > /usr/local/nagiosfusion/var/eventman.log 2>&1
nagios   11181 11175  0 15:43 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosfusion/cron/sysstat.php > /usr/local/nagiosfusion/var/sysstat.log 2>&1
nagios   11182 11181  0 15:43 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosfusion/cron/sysstat.php
nagios   11183 11180  0 15:43 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosfusion/cron/eventman.php
15:43:43 [root@fusion ~]# cat /etc/php.d/tidy.ini
; Enable tidy extension module
;extension=module.so
extension=mcrypt.so
15:43:53 [root@fusion ~]# tail -20 /var/log/cron
Mar  7 15:40:01 fusion CROND[10854]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/sysstat.php > /usr/local/nagiosfusion/var/sysstat.log 2>&1)
Mar  7 15:40:02 fusion CROND[10855]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/poller.php > /usr/local/nagiosfusion/var/poller.log 2>&1)
Mar  7 15:40:02 fusion CROND[10860]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Mar  7 15:40:02 fusion CROND[10861]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/dbmaint.php > /usr/local/nagiosfusion/var/dbmaint.log 2>&1)
Mar  7 15:40:02 fusion CROND[10859]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/eventman.php > /usr/local/nagiosfusion/var/eventman.log 2>&1)
Mar  7 15:41:01 fusion CROND[10955]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/eventman.php > /usr/local/nagiosfusion/var/eventman.log 2>&1)
Mar  7 15:41:01 fusion CROND[10958]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/sysstat.php > /usr/local/nagiosfusion/var/sysstat.log 2>&1)
Mar  7 15:41:01 fusion CROND[10957]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/cmdsubsys.php > /usr/local/nagiosfusion/var/cmdsubsys.log 2>&1)
Mar  7 15:41:30 fusion crontab[11013]: (root) LIST (root)
Mar  7 15:42:01 fusion CROND[11061]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/eventman.php > /usr/local/nagiosfusion/var/eventman.log 2>&1)
Mar  7 15:42:01 fusion CROND[11064]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/sysstat.php > /usr/local/nagiosfusion/var/sysstat.log 2>&1)
Mar  7 15:42:01 fusion CROND[11063]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/cmdsubsys.php > /usr/local/nagiosfusion/var/cmdsubsys.log 2>&1)
Mar  7 15:42:09 fusion crond[18865]: (CRON) INFO (Shutting down)
Mar  7 15:42:09 fusion crond[11111]: (CRON) STARTUP (1.4.4)
Mar  7 15:42:09 fusion crond[11111]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 94% if used.)
Mar  7 15:42:09 fusion crond[11111]: (CRON) INFO (running with inotify support)
Mar  7 15:42:09 fusion crond[11111]: (CRON) INFO (@reboot jobs will be run at computer's startup.)
Mar  7 15:43:01 fusion CROND[11178]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/cmdsubsys.php > /usr/local/nagiosfusion/var/cmdsubsys.log 2>&1)
Mar  7 15:43:01 fusion CROND[11181]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/sysstat.php > /usr/local/nagiosfusion/var/sysstat.log 2>&1)
Mar  7 15:43:01 fusion CROND[11180]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosfusion/cron/eventman.php > /usr/local/nagiosfusion/var/eventman.log 2>&1)
15:44:00 [root@fusion ~]# chage nagios -l
Last password change					: Feb 17, 2016
Password expires					: May 17, 2016
Password inactive					: never
Account expires						: never
Minimum number of days between password change		: 1
Maximum number of days between password change		: 90
Number of days of warning before password expires	: 10
15:44:06 [root@fusion ~]# sestatus
SELinux status:                 disabled

[lmiltchev]

Does the issue go away when you modify the "/etc/php.d/tidy.ini" file as in the example below?

Code: Select all

; Enable tidy extension module
;extension=module.so
;extension=mcrypt.so
extension=tidy.so

[gwakem]

Not only did that fix the problem with the poller running, it fixed an issue I hadn't reported yet. My Core stats are now showing up, whereas before I could only get xi to pull in. Thanks! I've been banging my head against that on and off most of the day! This looks good now, so should be safe to lock. Appreciate the help!

[lmiltchev]

I am glad I could help!