Weird behavior after performing repair database script
Re: Weird behavior after performing repair database script
I PM scottwilkerson with the zip file.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Weird behavior after performing repair database script
Looking at the profile you sent I am seeing a log of lines like these
Lets edit /etc/my.cnf
and right under
add
Then restart mysqld
Code: Select all
Too many connections in /usr/local/nagiosxi/html/db/adodb/drivers/adodb-mysqli.inc.php on line 117and right under
Code: Select all
[mysqld]Code: Select all
max-connections=500Code: Select all
service mysqld restartRe: Weird behavior after performing repair database script
I have edited the /etc/my.cnf as requested. Should I send a new profile.zip?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Weird behavior after performing repair database script
Did you also restart mysqld?Berto wrote:I have edited the /etc/my.cnf as requested. Should I send a new profile.zip?
If you are still experiencing the same problems, yes, please send a new profile.
Re: Weird behavior after performing repair database script
Yes I restarted mysqld. Okay will monitor and update whether its an issue or if its been resolved.
Re: Weird behavior after performing repair database script
Noticed after the change most the red warnings have gone away now, except for two as seen in the PNG file. I'll go ahead a PM again with a new profile.zp file.
You do not have the required permissions to view the files attached to this post.
Re: Weird behavior after performing repair database script
I've PM a new profile.zip but now the Nagios server now is displaying:
SQL Error [nagiosxi] : Table './nagiosxi/xi_auditlog' is marked as crashed and should be repaired
SQL Error [nagiosxi] : Table './nagiosxi/xi_auditlog' is marked as crashed and should be repaired
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Weird behavior after performing repair database script
Run the repair database script
Additionally, because you are getting errors like thing on nagios_logentries
, I'd like you run the following
Code: Select all
cd /usr/local/nagiosxi/scripts/
./repair_databases.shCode: Select all
ndo2db: mysql_error: 'Duplicate entry '5431088' for key 'PRIMARY''Code: Select all
echo "select max(logentry_id) from nagios_logentries;"| mysql -pnagiosxi nagios
echo "describe nagios_logentries;"| mysql -pnagiosxi nagiosRe: Weird behavior after performing repair database script
I ran ./repair_databases.sh and after a long time of the script running, the following error was displayed:
/usr/local/nagiosxi/scripts/repairmysql.sh: line 110: 22215 Segmentation fault $cmd $t --sort_buffer_size=256M
I see that the issue was that /var was filled up and I see that the nagiosxi directory under /var/lib/mysql filled up with 72, should that have occurred?
/usr/local/nagiosxi/scripts/repairmysql.sh: line 110: 22215 Segmentation fault $cmd $t --sort_buffer_size=256M
I see that the issue was that /var was filled up and I see that the nagiosxi directory under /var/lib/mysql filled up with 72, should that have occurred?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Weird behavior after performing repair database script
That shouldn't normally occur, your system ran out of memory, how much memory do you have? can you allocate more?Berto wrote:I ran ./repair_databases.sh and after a long time of the script running, the following error was displayed:
/usr/local/nagiosxi/scripts/repairmysql.sh: line 110: 22215 Segmentation fault $cmd $t --sort_buffer_size=256M
I see that the issue was that /var was filled up and I see that the nagiosxi directory under /var/lib/mysql filled up with 72, should that have occurred?