Nagios Support Forum

Can you please send me a copy of your profile?

Go to Admin --> System Config --> System Profile
Click "Download Profile"
Save the .zip file and send it to me as a PM.
Do not attach it to this forum post, it will contain sensitive information.

Thank you.

In addition to what hsmith asked for, can you login to the Xi server as root, run the following and post the output here? Thanks

ls -l /usr/local
total 68
drwxr-xr-x. 2 root root 4096 Dec 1 2011 bin
drwxr-xr-x. 2 root root 4096 Sep 23 2011 etc
drwxr-xr-x. 2 root root 4096 Sep 23 2011 games
drwxr-xr-x 3 root root 4096 Nov 5 16:40 ibm
drwxr-xr-x. 2 root root 4096 Sep 23 2011 include
drwxr-xr-x. 3 root root 4096 Dec 1 2011 lib
drwxr-xr-x. 3 root root 4096 Sep 20 12:50 lib64
drwxr-xr-x. 2 root root 4096 Sep 23 2011 libexec
drwxr-xr-x 9 root root 4096 Apr 23 2015 nagios
drwxr-xr-x 6 root root 4096 Oct 9 16:51 nagiosmobile
drwxr-xr-x 10 nagios nagios 4096 Apr 23 2015 nagiosxi
drwxr-xr-x 5 apache apache 4096 Apr 23 2015 nagvis
drwxr-xr-x 7 nagios nagios 4096 Apr 23 2015 nrdp
drwxr-xr-x 4 root root 4096 Apr 23 2015 nsis
-rwxr-xr-x 1 root root 0 Sep 18 08:18 run.sh
drwxr-xr-x. 2 root root 4096 Sep 23 2011 sbin
drwxr-xr-x. 6 root root 4096 Sep 20 12:50 share
drwxr-xr-x. 2 root root 4096 Sep 23 2011 src


ls -l /usr/local/nagiosxi
total 44
drwxr-xr-x 2 nagios nagios 4096 Apr 23 2015 cron
drwxr-xr-x 3 nagios nagios 4096 Apr 23 2015 etc
drwxr-xr-x 19 nagios nagios 4096 Oct 9 16:49 html
-rw-r--r-- 1 nagios nagios 0 Apr 23 2015 is.installed
drwxr-xr-x 3 nagios nagios 4096 Apr 23 2015 nom
drwxr-xr-x 2 nagios nagios 4096 Jan 25 12:16 scripts
drwsrwsr-x 3 nagios nagios 16384 Jan 18 17:17 tmp
drwxr-xr-x 2 nagios nagios 4096 Nov 16 21:32 tools
drwxr-xr-x 5 nagios nagios 4096 Jan 25 14:45 var

ls -l /usr/local/nagiosxi
total 44
drwxr-xr-x 2 nagios nagios 4096 Apr 23 2015 cron
drwxr-xr-x 3 nagios nagios 4096 Apr 23 2015 etc
drwxr-xr-x 19 nagios nagios 4096 Oct 9 16:49 html
-rw-r--r-- 1 nagios nagios 0 Apr 23 2015 is.installed
drwxr-xr-x 3 nagios nagios 4096 Apr 23 2015 nom
drwxr-xr-x 2 nagios nagios 4096 Jan 25 12:16 scripts
drwsrwsr-x 3 nagios nagios 16384 Jan 18 17:17 tmp
drwxr-xr-x 2 nagios nagios 4096 Nov 16 21:32 tools
drwxr-xr-x 5 nagios nagios 4096 Jan 25 14:45 var


ls -l /usr/local/nagiosxi/var
total 820
-rw-r--r-- 1 nagios nagios 303 Jan 25 14:47 cleaner.log
-rw-r--r-- 1 nagios nagios 303 Jan 3 03:43 cleaner.log-20160103
-rw-r--r-- 1 nagios nagios 303 Jan 10 03:22 cleaner.log-20160110
-rw-r--r-- 1 nagios nagios 303 Jan 17 03:45 cleaner.log-20160117
-rw-r--r-- 1 nagios nagios 303 Jan 24 03:40 cleaner.log-20160124
-rw-r--r-- 1 nagios nagios 80 Jan 25 14:47 cmdsubsys.log
-rw-r--r-- 1 nagios nagios 77 Jan 3 03:44 cmdsubsys.log-20160103
-rw-r--r-- 1 nagios nagios 78 Jan 10 03:23 cmdsubsys.log-20160110
-rw-r--r-- 1 nagios nagios 79 Jan 17 03:46 cmdsubsys.log-20160117
-rw-r--r-- 1 nagios nagios 78 Jan 24 03:41 cmdsubsys.log-20160124
drwsrwsr-x 2 apache nagios 4096 Dec 17 21:42 components
-rw-r--r-- 1 nagios nagios 8 Jan 25 14:47 corelog.data
-rw-r--r-- 1 nagios nagios 238 Jan 25 14:47 corelog.diff
-rw-r--r-- 1 nagios nagios 2681 Jan 25 14:45 dbmaint.log
-rw-r--r-- 1 nagios nagios 2812 Jan 3 03:25 dbmaint.log-20160103
-rw-r--r-- 1 nagios nagios 2812 Jan 9 18:10 dbmaint.log-20160110
-rw-r--r-- 1 nagios nagios 2681 Jan 17 03:45 dbmaint.log-20160117
-rw-r--r-- 1 nagios nagios 2681 Jan 24 03:40 dbmaint.log-20160124
-rw-r--r-- 1 nagios nagios 75 Jan 25 14:45 deadpool.log
-rw-r--r-- 1 nagios nagios 253 Jan 3 03:25 deadpool.log-20160103
-rw-r--r-- 1 nagios nagios 253 Jan 9 18:10 deadpool.log-20160110
-rw-r--r-- 1 nagios nagios 75 Jan 18 04:25 deadpool.log-20160118
-rw-r--r-- 1 nagios nagios 75 Jan 25 03:30 deadpool.log-20160125
-rw-r--r-- 1 nagios nagios 11549 Jan 25 14:47 eventman.log
-rw-r--r-- 1 nagios nagios 87875 Jan 3 03:44 eventman.log-20160103
-rw-r--r-- 1 nagios nagios 210808 Jan 10 03:23 eventman.log-20160110
-rw-r--r-- 1 nagios nagios 83127 Jan 17 03:46 eventman.log-20160117
-rw-r--r-- 1 nagios nagios 19468 Jan 24 03:41 eventman.log-20160124
-rw-r--r-- 1 nagios nagios 25 Jan 25 14:47 feedproc.log
-rw-r--r-- 1 nagios nagios 25 Jan 3 03:44 feedproc.log-20160103
-rw-r--r-- 1 nagios nagios 325 Jan 10 03:23 feedproc.log-20160110
-rw-r--r-- 1 nagios nagios 25 Jan 17 03:46 feedproc.log-20160117
-rw-r--r-- 1 nagios nagios 25 Jan 24 03:41 feedproc.log-20160124
-rw-r--r-- 1 nagios nagios 0 Jan 17 03:45 load_url.log
-rw-r--r-- 1 nagios nagios 901 Dec 13 03:46 load_url.log-20151213
-rw-r--r-- 1 nagios nagios 867 Dec 18 11:51 load_url.log-20151220
-rw-r--r-- 1 nagios nagios 869 Jan 13 22:18 load_url.log-20160114
-rw-r--r-- 1 nagios nagios 901 Jan 17 03:45 load_url.log-20160117
-rw-r--r-- 1 nagios nagios 0 Jan 25 14:47 nom.log
-rw-r--r-- 1 nagios nagios 347 Oct 19 01:11 nom.log-20151019
-rw-r--r-- 1 nagios nagios 1035 Dec 10 03:46 nom.log-20151210
-rw-r--r-- 1 nagios nagios 81 Jan 25 14:47 perfdataproc.log
-rw-r--r-- 1 nagios nagios 81 Jan 3 03:44 perfdataproc.log-20160103
-rw-r--r-- 1 nagios nagios 881 Jan 10 03:23 perfdataproc.log-20160110
-rw-r--r-- 1 nagios nagios 81 Jan 17 03:46 perfdataproc.log-20160117
-rw-r--r-- 1 nagios nagios 81 Jan 24 03:41 perfdataproc.log-20160124
-rw-r--r-- 1 nagios nagios 27534 Jan 25 14:01 recurringdowntime.log
-rw-r--r-- 1 nagios nagios 28051 Jan 3 00:01 recurringdowntime.log-20160103
-rw-r--r-- 1 nagios nagios 30040 Jan 9 14:01 recurringdowntime.log-20160110
-rw-r--r-- 1 nagios nagios 30163 Jan 17 03:01 recurringdowntime.log-20160117
-rw-r--r-- 1 nagios nagios 27533 Jan 24 03:01 recurringdowntime.log-20160124
-rw-r--r-- 1 nagios nagios 0 Jan 25 14:47 reportengine.log
drwxr-xr-x 2 nagios nagios 4096 Jan 21 18:07 subsys
-rw-r--r-- 1 nagios nagios 2603 Jan 25 14:47 sysstat.log
-rw-r--r-- 1 nagios nagios 12679 Jan 3 03:39 sysstat.log-20160103
-rw-r--r-- 1 nagios nagios 12670 Jan 10 03:22 sysstat.log-20160110
-rw-r--r-- 1 nagios nagios 8239 Jan 17 03:46 sysstat.log-20160117
-rw-r--r-- 1 nagios nagios 8235 Jan 24 03:41 sysstat.log-20160124
drwxr-xr-x 2 nagios nagios 4096 Oct 9 16:49 upgrades
-rw-r--r-- 1 nagios nagios 34615 Dec 18 14:48 xi-sys.cfg
-rw-r--r-- 1 nagios nagios 195 Dec 18 14:48 xiversion

#service crond status
crond (pid 2009) is running...

Can you run the following tail command as root on the XI server. Then try and open the Availability report. Then post any errors you see from the tail command?

Just one error here.

PHP Notice: Use of undefined constant Hostgroup - assumed 'Hostgroup' in /usr/local/nagiosxi/html/includes/components/bbmap/bbmap.inc.php on line 193, referer: http://MY SERVER/nagiosxi/dashboards/dashboard.php?id=vsve6ta8

any ideia?

So far, everything looks OK. Can you login as root to the Xi server, run the following commands and post the output?

grep nag /etc/group
nagios500:nagios,apache,snmptt
nagcmd501:nagios,apache,snmptt


tail -50 /var/log/mysqld.log
160113 12:54:51 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:54:51 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:54:51 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:54:51 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:54:51 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:54:51 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:54:53 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:55:41 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:55:48 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:55:50 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:55:58 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:04 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:09 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:17 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:29 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:29 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:33 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:40 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 12:56:40 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_logentries' is marked as crashed and last (automatic?) repair failed
160113 13:10:04 [Note] Found 18936396 of 2519861 rows when repairing './nagios/nagios_logentries'
160113 21:52:35 [Note] /usr/libexec/mysqld: Normal shutdown

160113 21:52:35 [Note] Event Scheduler: Purging the queue. 0 events
160113 21:52:35 InnoDB: Starting shutdown...
160113 21:52:38 InnoDB: Shutdown completed; log sequence number 0 44233
160113 21:52:38 [Note] /usr/libexec/mysqld: Shutdown complete

160113 21:52:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160113 14:10:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160113 14:10:53 InnoDB: Initializing buffer pool, size = 8.0M
160113 14:10:53 InnoDB: Completed initialization of buffer pool
160113 14:10:53 InnoDB: Started; log sequence number 0 44233
160113 14:10:53 [Note] Event Scheduler: Loaded 0 events
160113 14:10:53 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160113 22:18:00 [Note] /usr/libexec/mysqld: Normal shutdown

160113 22:18:00 [Note] Event Scheduler: Purging the queue. 0 events
160113 22:18:02 InnoDB: Starting shutdown...
160113 22:18:07 InnoDB: Shutdown completed; log sequence number 0 44233
160113 22:18:07 [Note] /usr/libexec/mysqld: Shutdown complete

160113 22:18:07 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160113 14:36:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160113 14:36:14 InnoDB: Initializing buffer pool, size = 8.0M
160113 14:36:14 InnoDB: Completed initialization of buffer pool
160113 14:36:15 InnoDB: Started; log sequence number 0 44233
160113 14:36:15 [Note] Event Scheduler: Loaded 0 events
160113 14:36:15 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution




To the messages log i have just sensor errors

tail -100 /var/log/messages
Jan 26 17:32:22 MY SERVER nagios: SERVICE ALERT: WINSERVER;CPU Stats;WARNING;HARD;5;WARNING - CPU usage at 94.75%
Jan 26 17:32:22 MY SERVER nagios: SERVICE NOTIFICATION: nagiosadmin;WINSERVER;CPU Stats;WARNING;xi_service_notification_handler;WARNING - CPU usage at 94.75%
Jan 26 17:33:08 MY SERVER nagios: SERVICE NOTIFICATION: nagiosadmin;WINSERVER01;Drive E: Disk Usage;CRITICAL;xi_service_notification_handler;connect to address 10.x.X.X and port 12489: Connection refused
Jan 26 17:33:10 MY SERVER nagios: SERVICE NOTIFICATION: nagiosadmin;WINSERVER002;CPU Stats;CRITICAL;xi_service_notification_handler;CRITICAL - CPU usage at 100%
Jan 26 17:33:10 MY SERVER nagios: SERVICE NOTIFICATION: nagiosadmin;WINSERVER002;CPU Stats;CRITICAL;xi_service_notification_handler;CRITICAL - CPU usage at 100%
Jan 26 17:33:10 MY SERVER nagios: SERVICE NOTIFICATION: nagiosadmin;WINSERVER002;CPU Stats;CRITICAL;xi_service_notification_handler;CRITICAL - CPU usage at 100%
Jan 26 17:33:10 MY SERVER nagios: SERVICE NOTIFICATION: nagiosadmin;WINSERVER002;CPU Stats;CRITICAL;xi_service_notification_handler;CRITICAL - CPU usage at 100%

The log file indicates that you have a crashed table, can you try to fix this with the following commands?

I run the report repair and rolled normally. But the report continues with this message "Availability date is not Available When monitoring engine is not running."