Appealing to some cpanel + WHM experts.
We experienced Out of Memory and MYsql restarts PHP and httpd on our Centos 6 platform of WHM version 60 and Centos 6.8 with server memory 8GB
/var/log/messages
Jan 12 Restart 1
php invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
Jan 30 Restart 2
httpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
After Restart 1
We ran the mysqltuner.pl everyone talks about for tweaking mysql.cnf
Also we increase server memory from 8 - 12GB
Then added these settings as recommended.
After Restart 1
We ran the mysqltuner.pl it now recommends this ?
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[--] InnoDB Thread Concurrency: 8
[OK] InnoDB File per table is activated
[OK] InnoDB buffer pool / data size: 9.0G/2.1G
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (2.77777777777778 %): 128.0M * 2/9.0G should be equal 25%
[!!] InnoDB buffer pool instances: 8
[--] InnoDB Buffer Pool Chunk Size not used or defined in your version
[OK] InnoDB Read buffer efficiency: 99.98% (345174626 hits/ 345244918 total)
[!!] InnoDB Write Log efficiency: 65.86% (109652 hits/ 166496 total)
[OK] InnoDB log waits: 0.00% (0 waits / 56844 writes)
Variables to adjust:
table_open_cache (> 2000)
key_buffer_size (> 88.1M)
innodb_log_file_size should be equals to 1/4 of buffer pool size (=2G) if possible.
innodb_buffer_pool_instances(=9)
Has anyone experience enough to verify the above configuration or experience with sar analysis for server and memory optimisation ?
Architecturally should we stick with this mix of Apache 2.4 / Mysql 5.6 or considering cloud Linux trialling it on a dev server found the migration to be painful. We would also consider a dedicated mysql server and webserver load balance if thats the better answer than struggling inside one server ?
BTW Apache logs the Restart 2 was triggered by a script coming from a GCP hosted server.
Kind Regards
Matt
We experienced Out of Memory and MYsql restarts PHP and httpd on our Centos 6 platform of WHM version 60 and Centos 6.8 with server memory 8GB
/var/log/messages
Jan 12 Restart 1
php invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
Jan 30 Restart 2
httpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
After Restart 1
We ran the mysqltuner.pl everyone talks about for tweaking mysql.cnf
Also we increase server memory from 8 - 12GB
Then added these settings as recommended.
After Restart 1
We ran the mysqltuner.pl it now recommends this ?
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[--] InnoDB Thread Concurrency: 8
[OK] InnoDB File per table is activated
[OK] InnoDB buffer pool / data size: 9.0G/2.1G
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (2.77777777777778 %): 128.0M * 2/9.0G should be equal 25%
[!!] InnoDB buffer pool instances: 8
[--] InnoDB Buffer Pool Chunk Size not used or defined in your version
[OK] InnoDB Read buffer efficiency: 99.98% (345174626 hits/ 345244918 total)
[!!] InnoDB Write Log efficiency: 65.86% (109652 hits/ 166496 total)
[OK] InnoDB log waits: 0.00% (0 waits / 56844 writes)
Variables to adjust:
table_open_cache (> 2000)
key_buffer_size (> 88.1M)
innodb_log_file_size should be equals to 1/4 of buffer pool size (=2G) if possible.
innodb_buffer_pool_instances(=9)
Has anyone experience enough to verify the above configuration or experience with sar analysis for server and memory optimisation ?
Architecturally should we stick with this mix of Apache 2.4 / Mysql 5.6 or considering cloud Linux trialling it on a dev server found the migration to be painful. We would also consider a dedicated mysql server and webserver load balance if thats the better answer than struggling inside one server ?
BTW Apache logs the Restart 2 was triggered by a script coming from a GCP hosted server.
Kind Regards
Matt