Notifications link on Locks up browser

[matt.lilek]

I cannot go into the notifications link on the user interface to make changes it just keeps spinning and locks up my browser. I have tried multiple browsers and the same thing happens. I need to take off unknown and unreachable notifications for an office that keeps going up and down i just want to see the parent going up and down not all the children saying unknown or unreachable cause its spamming like crazy.

[abrist]

The notifications table in the db is probably huge causing the page to timeout when it requests data from the table. What is the output of:

Code: Select all

ls -la /var/lib/mysql/nagios/nagios_notification*
tail -15 /var/log/mysqld.log

[matt.lilek]

login as: root
[email protected]'s password:
Last login: Thu Dec 5 09:41:17 2013 from 10.41.66.245
[root@att1-nag1 ~]# ls -la /var/lib/mysql/nagios/nagios_notification*
-rw-rw---- 1 mysql mysql 33744 Sep 27 09:32 /var/lib/mysql/nagios/nagios_notifications.frm
-rw-rw---- 1 mysql mysql 20547184 Nov 4 09:00 /var/lib/mysql/nagios/nagios_notifications.MYD
-rw-rw---- 1 mysql mysql 4236288 Nov 4 09:00 /var/lib/mysql/nagios/nagios_notifications.MYI
[root@att1-nag1 ~]# tail -15 /var/log/mysqld.log
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
131128 17:10:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131128 17:10:10 InnoDB: Initializing buffer pool, size = 8.0M
131128 17:10:10 InnoDB: Completed initialization of buffer pool
131128 17:10:10 InnoDB: Started; log sequence number 0 44243
131128 17:10:10 [Note] Event Scheduler: Loaded 0 events
131128 17:10:10 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
131128 17:14:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131128 17:14:29 InnoDB: Initializing buffer pool, size = 8.0M
131128 17:14:29 InnoDB: Completed initialization of buffer pool
131128 17:14:30 InnoDB: Started; log sequence number 0 44243
131128 17:14:30 [Note] Event Scheduler: Loaded 0 events
131128 17:14:30 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
[root@att1-nag1 ~]#

[abrist]

If the notification history is not required, you could truncate the table:

Code: Select all

mysql -u ndoutils -pn@gweb nagios -e 'TRUNCATE TABLE nagios_notifications'

BEWARE! This is destructive. The entries removed can only be recovered by restoring a a backup, so make sure that you do not need the historical information.
If you do opt to truncate, you should probably run a db repair afterwards:

Code: Select all

/usr/local/nagiosxi/scripts/repairmysql.sh nagios

[matt.lilek]

Is this a common occurence with a large installation?

[slansing]

If your notification table is quite large could certainly cause sluggishness, and that is a symptom of a large installation, though not very prevalent unless you send out a massive amount of notifications.