Page 3 of 3
Re: Problem with Ingres Plugin
Posted: Fri Jan 08, 2016 10:29 am
by rkennedy
Let's check out the mysql log file. Can you run the following command and post the output?
Re: Problem with Ingres Plugin
Posted: Fri Jan 08, 2016 10:58 am
by Bone8Head
rkennedy wrote:Let's check out the mysql log file. Can you run the following command and post the output?
Code: Select all
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:25 InnoDB: Started; log sequence number 0 229406
160108 10:32:25 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:25 [ERROR] Can't start server: can't create PID file: No space left on device
160108 10:32:25 mysqld_safe Number of processes running now: 0
160108 10:32:25 mysqld_safe mysqld restarted
160108 10:32:25 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:25 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:25 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:26 InnoDB: Started; log sequence number 0 229406
160108 10:32:26 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:26 [ERROR] Can't start server: can't create PID file: No space left on device
160108 10:32:26 mysqld_safe Number of processes running now: 0
160108 10:32:26 mysqld_safe mysqld restarted
160108 10:32:26 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:26 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:26 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:26 InnoDB: Started; log sequence number 0 229406160108 10:32:55 mysqld_safe Number of processes running now: 0
160108 10:32:55 mysqld_safe mysqld restarted
160108 10:32:55 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:55 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:55 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:55 InnoDB: Started; log sequence number 0 229406
160108 10:32:55 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:55 [ERROR] Can't start server: can't create PID file: No space left on device
160108 10:32:55 mysqld_safe Number of processes running now: 0
160108 10:32:55 mysqld_safe mysqld restarted
160108 10:32:55 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:55 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:55 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:55 InnoDB: Started; log sequence number 0 229406
160108 10:32:55 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:55 [ERROR] Can't start server: can't create PID file: No space left on device
160108 10:32:55 mysqld_safe Number of processes running now: 0
160108 10:32:55 mysqld_safe mysqld restarted
160108 10:32:55 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:55 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:55 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:55 InnoDB: Started; log sequence number 0 229406
160108 10:32:55 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:55 [ERROR] Can't start server: can't create PID file: No space left on device
160108 10:32:55 mysqld_safe Number of processes running now: 0
160108 10:32:55 mysqld_safe mysqld restarted
160108 10:32:55 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:55 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:55 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:56 InnoDB: Started; log sequence number 0 229406
160108 10:32:56 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:56 [ERROR] Can't start server: can't create PID file: No space left on device
160108 10:32:56 mysqld_safe Number of processes running now: 0
160108 10:32:56 mysqld_safe mysqld restarted
160108 10:32:56 InnoDB: Initializing buffer pool, size = 8.0M
160108 10:32:56 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160108 10:32:56 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160108 10:32:56 InnoDB: Started; log sequence number 0 229406
Re: Problem with Ingres Plugin
Posted: Fri Jan 08, 2016 1:47 pm
by rkennedy
Code: Select all
160108 10:32:25 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:25 [ERROR] Can't start server: can't create PID file: No space left on device
This stands out as you may have ran out of disk space, what is the result of
df -H?
Re: Problem with Ingres Plugin
Posted: Fri Jan 08, 2016 1:52 pm
by Bone8Head
rkennedy wrote:Code: Select all
160108 10:32:25 [ERROR] /usr/libexec/mysqld: Error writing file '/var/run/mysqld/mysqld.pid' (Errcode: 28)
160108 10:32:25 [ERROR] Can't start server: can't create PID file: No space left on device
This stands out as you may have ran out of disk space, what is the result of
df -H?
Code: Select all
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
7.9G 7.9G 0 100% /
tmpfs 2.1G 0 2.1G 0% /dev/shm
/dev/sda1 500M 75M 399M 16% /boot
[root@nagiosfe /]#
I guess you are right...what should I do?
This is the Space on VMWare:
I should put another space for this VM?
But I got a question: Nagios XI will need new bytes everyday and he will never stop? I mean, yesterday I already deleted some pretty big log files in /var/log/, but I guess that's not enough
Re: Problem with Ingres Plugin
Posted: Fri Jan 08, 2016 3:08 pm
by rkennedy
Take a look at this document for information on resizing the VM disk -
https://assets.nagios.com/downloads/nag ... M-Disk.pdf
The files that grow in Nagios shouldn't be growing by very much every day to be honest. You can always tweak certain programs to not log which would stop space from being used.
Re: Problem with Ingres Plugin
Posted: Fri Jan 08, 2016 4:19 pm
by Bone8Head
rkennedy wrote:Take a look at this document for information on resizing the VM disk -
https://assets.nagios.com/downloads/nag ... M-Disk.pdf
The files that grow in Nagios shouldn't be growing by very much every day to be honest. You can always tweak certain programs to not log which would stop space from being used.
Ok, thanks.
I should do EVERY step of this PDF that you gave me?
Resize Virtual Disk - Partition - P Volume - Logical Volume - Filesystem?
And how much size is reccomended?
Re: Problem with Ingres Plugin
Posted: Mon Jan 11, 2016 10:14 am
by rkennedy
I will now close this thread out as you have started a new one for this issue,
https://support.nagios.com/forum/viewto ... 498#167245.