Nagios Support Forum

scottwilkerson wrote:Actually, it ocould be database corruption, can you run

Code: Select all

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

I will try that, but after repair, is it possible that the logs still empty or missing some?! if so, since the NagiosXI VM had been backup before upgrade to 2012, do you think we should back to use the old one, or continue to use 2012 and try to repair it (could lost some data)?

I would run the repair first. If you restoe the backup you are going to be missing everything since the backup, whereas is the repair goes fine, you will only be missing items since the table got corrupted.

scottwilkerson wrote:Actually, it ocould be database corruption, can you run

Code: Select all

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

Yes, logs came back after running repair script.

Another two strange things ...

1. When there were alert events, our client said the notification seems delay?
2. When email alert notified, only one person got the alert?!

Are these two things possible?

xpertech wrote:Yes, logs came back after running repair script.

Excellent.

xpertech wrote:1. When there were alert events, our client said the notification seems delay?

This would be possible, and somewhat likely depending on how the setting are set for
retry_interval
max_check_attempts

Nagios doesn't send the notification until a HARD state is reached.

Additionally, there could be delay in delivery from the mail server.

xpertech wrote:2. When email alert notified, only one person got the alert?!

This is going to depend on what the contacts or contact groups are set to for the host/service that went down, and what notification handler the contact has set, additionally if the notification handler is the xi_host/service_notification handler, they need to have notifications enabled in their user settings...