Page 1 of 1

Table nagios/logentries marked as crashed and last

Posted: Thu Apr 19, 2018 4:48 am
by Gonela
Hi Team,

We are not able to run the local backup. when we see the logs .Table nagios/logentries marked as crashed and last automatic repair is failed.
how can i resolve this.

I want to resolve this issue without disturbing the current monitoring.

Re: Table nagios/logentries marked as crashed and last

Posted: Thu Apr 19, 2018 9:35 am
by scottwilkerson
This document outlines the repair procedure
https://assets.nagios.com/downloads/nag ... tabase.pdf

Re: Table nagios/logentries marked as crashed and last

Posted: Thu Apr 19, 2018 9:45 am
by Gonela
HI Team,

We just gone through that document. Can we repair the single table why should we repair total database instead of doing single table. Can you tell me any another alternative way. how we can repair the single table without disturbing the existing environment.

Re: Table nagios/logentries marked as crashed and last

Posted: Thu Apr 19, 2018 9:54 am
by scottwilkerson
you can do a singe table BUT you need to know all the affected tables, and either way your whole environment is already affected.

However to do a single table run the following

Code: Select all

service mysqld stop
/usr/local/nagiosxi/scripts/repairmysql.sh <database_name> <table_name>
service mysqld start

Re: Table nagios/logentries marked as crashed and last

Posted: Thu Apr 19, 2018 10:47 am
by Gonela
Hi team,

Thanks for the reply. I should not disturb the existing mysql status. mysql should in running status. is there any command to repair the table without disturbing the environment.

Re: Table nagios/logentries marked as crashed and last

Posted: Thu Apr 19, 2018 11:01 am
by scottwilkerson
Gonela wrote:Hi team,

Thanks for the reply. I should not disturb the existing mysql status. mysql should in running status. is there any command to repair the table without disturbing the environment.
No there is not, also, I need to strongly encourage you to fix the problem ASAP.

All of the data will not go in the database if you do not, by delaying you are actually prolonging the issue.