Nagios Support Forum

Posted: **Tue Aug 11, 2015 4:34 pm**

Sure No,
We upgrade the storage size, then reboot the server then repair data base, the failed repair message disappeared and later returned again.

Code: Select all

[root@nms ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_nms2-lv_root
                      193G   35G  149G  19% /
tmpfs                 5.9G     0  5.9G   0% /dev/shm
/dev/sda1             485M   70M  390M  16% /boot
You have new mail in /var/spool/mail/root
[root@nms ~]# df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/mapper/vg_nms2-lv_root
                     12803616  868729 11934887    7% /
tmpfs                1523843       1 1523842    1% /dev/shm
/dev/sda1             128016      44  127972    1% /boot
[root@nms ~]#

Posted: **Tue Aug 11, 2015 8:39 pm**

Generally speaking, if the database keeps crashing this is commonly caused by the OS running out of memory and deciding to kill a process to reclaim memory. When it chooses mysqld then this is going to leave the database in a crashed state.

Starting off, when you look at /var/log/mysqld.log you'll see that these errors start being reported at a specific time.

Can you correlate that time to any events in /var/log/messages ?

Also, seeing as this is a VM, using the Hypervisor can you look at the VM's memory and CPU usage performance graphs at the same time that these errors start occurring in mysqld.log. It might show you that the memory was completely used at this time perhaps.

Nagios Support Forum

Nagios XI CPU NEar 100 %

Re: Nagios XI CPU NEar 100 %

Re: Nagios XI CPU NEar 100 %