We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Mysql queries peaking to 1M+ occasionally
Re: Mysql queries peaking to 1M+ occasionally
Mystery!GreenUnicorn wrote:
What woud be the best way to find the reason for that?
May be it's ddos or shell?
-
- Posts: 54
- Joined: Wed Dec 11, 2013 9:05 pm
Re: Mysql queries peaking to 1M+ occasionally
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.
To see what I'm talking about please go into services and check out the usage.
-
- Posts: 33
- Joined: Sun Oct 05, 2014 7:53 am
Re: Mysql queries peaking to 1M+ occasionally
Add swap ram to your machine, mysql will not crash
-
- Posts: 54
- Joined: Wed Dec 11, 2013 9:05 pm
Re: Mysql queries peaking to 1M+ occasionally
Next time this happens please find the issue in:
and post what you find.
Code: Select all
#RHEL
sudo tail /var/log/mysqld.log
#Debian
sudo tail /var/log/mysql.log
sudo tail /var/log/mysql/error.log
Re: Mysql queries peaking to 1M+ occasionally
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.htmlGreenUnicorn 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
-
- Posts: 54
- Joined: Wed Dec 11, 2013 9:05 pm
Re: Mysql queries peaking to 1M+ occasionally
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.
-
- Posts: 54
- Joined: Wed Dec 11, 2013 9:05 pm
Re: Mysql queries peaking to 1M+ occasionally
Did that seem to due the trick?