vinnocorp

Hello @wfadam

Thank you for your rapid response.

Yeah that’s right, the server syslog file contains the following recurring records:

============================
Jul 30 10:24:58 servername kernel: [ 643.120063] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/mysql.service,task=mysqld,pid=881,uid=112
Jul 30 10:24:58 servername kernel: [ 643.120123] Out of memory: Killed process 881 (mysqld) total-vm:1292100kB, anon-rss:446396kB, file-rss:0kB, shmem-rss:0kB, UID:112 pgtables:1224kB oom_score_adj:0
Jul 30 10:24:58 servername kernel: [ 643.156482] oom_reaper: reaped process 881 (mysqld), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Jul 30 10:24:58 servername systemd[1]: mysql.service: Main process exited, code=killed, status=9/KILL
Jul 30 10:24:58 servername systemd[1]: mysql.service: Failed with result ‘signal’.
Jul 30 10:24:58 servername systemd[1]: mysql.service: Scheduled restart job, restart counter is at 1.
Jul 30 10:24:58 servername systemd[1]: Stopped MySQL Community Server.
Jul 30 10:24:58 servername systemd[1]: Starting MySQL Community Server…
Jul 30 10:25:00 servername systemd[1]: Started MySQL Community Server.
============================

So, I guess no server tuning would be helpful and the only solution is to expand RAM?

Regards,
vinnocorp