- The following errors can be seen in logs
[UID:1001] master: worker is killed by SEGV signal - probably lve PMEM limit or PHP memory_limit hit
[UID:1001] Child process with pid: 722551 was killed by signal: 9, core dumped: no
[UID:1001] master: worker is killed by SIGKILL signal - it may have been happened due to exceeding lve PMEM limit. Please check /var/l
og/messages for message "Memory cgroup out of memory: Kill process 722551 (lsphp)" (LVE ID 1001)
- DB Governor is enabled
- CloudLinux 7
- DB Governor
- Open MySQL Governor config file
/etc/container/mysql-governor.xmland check if it contains "0" as read/write limits for the affected user.
Replace zeros with "-1" in read/write limits and restart MySQL Governor service.
This error is related to exceeding the PMem limit. From the error code we know that such errors may be due to the fact that the PHP process runs some actions on the database and in case of bad optimization or incorrect query, for example, this process hangs and consumes resources. And since Governor works in abusers mode, i.e. transfers the user processes when reaching the limit in its LVE, then such a hanging process leads to the fact that the entire user resource is used, reaching the limit and you get the error 503.
Value -1 removes limit from user's requests to database and they can be executed in any case. Accordingly, everything works and you don't get an error.