Page 1 of 1

Re: Mysql queries peaking to 1M+ occasionally

Posted: Wed Jan 07, 2015 5:10 am
by skurudo
GreenUnicorn wrote:Image
What woud be the best way to find the reason for that?
Mystery!
May be it's ddos or shell?

Re: Mysql queries peaking to 1M+ occasionally

Posted: Wed Jan 07, 2015 8:46 pm
by emardotcom
There is a known issue with calculating usage that maybe the reason for this, but does your server shut down?
To see what I'm talking about please go into services and check out the usage.

Re: Mysql queries peaking to 1M+ occasionally

Posted: Fri Jan 23, 2015 2:59 am
by armyboylegend
Add swap ram to your machine, mysql will not crash

Re: Mysql queries peaking to 1M+ occasionally

Posted: Mon Jan 26, 2015 11:24 pm
by emardotcom
Next time this happens please find the issue in:

Code: Select all

#RHEL
sudo tail /var/log/mysqld.log
#Debian
sudo tail /var/log/mysql.log
sudo tail /var/log/mysql/error.log
and post what you find.

Re: Mysql queries peaking to 1M+ occasionally

Posted: Tue Jan 27, 2015 10:53 pm
by joem
GreenUnicorn wrote:here we go

Code: Select all

150126 22:31:29 [Note] Plugin 'FEDERATED' is disabled.
150126 22:31:29 InnoDB: The InnoDB memory heap is disabled
150126 22:31:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150126 22:31:29 InnoDB: Compressed tables use zlib 1.2.3.4
150126 22:31:29 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
150126 22:31:29 InnoDB: Completed initialization of buffer pool
150126 22:31:29 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150126 22:31:29 [ERROR] Plugin 'InnoDB' init function returned error.
150126 22:31:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150126 22:31:29 [ERROR] Unknown/unsupported storage engine: InnoDB
150126 22:31:29 [ERROR] Aborting

150126 22:31:29 [Note] /usr/sbin/mysqld: Shutdown complete

150126 22:31:31 [Note] Plugin 'FEDERATED' is disabled.
150126 22:31:31 InnoDB: The InnoDB memory heap is disabled
150126 22:31:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150126 22:31:31 InnoDB: Compressed tables use zlib 1.2.3.4
150126 22:31:31 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
150126 22:31:31 InnoDB: Completed initialization of buffer pool
150126 22:31:31 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150126 22:31:31 [ERROR] Plugin 'InnoDB' init function returned error.
150126 22:31:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150126 22:31:31 [ERROR] Unknown/unsupported storage engine: InnoDB
150126 22:31:31 [ERROR] Aborting

150126 22:31:31 [Note] /usr/sbin/mysqld: Shutdown complete
The problem is InnoDB is unable to allocate memory as specified in innodb_buffer_pool_size variable...Please see http://codesplanet.blogspot.com/2014/04 ... tom-0.html

Re: Mysql queries peaking to 1M+ occasionally

Posted: Wed Jan 28, 2015 8:07 pm
by emardotcom
As Joem has suggested you need to add swap at least 512mg incase your physical memory at some point reaches it's limit. Perhaps in a future release of Vesta we can add and change the swap settings, but for now try to do it manually.

Re: Mysql queries peaking to 1M+ occasionally

Posted: Fri Jan 30, 2015 3:01 am
by emardotcom
Did that seem to due the trick?