Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
litespeed_wiki:troubleshooting:mysql-killed-when-pid-max-too-small [2019/03/20 20:34] Lisa Clarke |
litespeed_wiki:troubleshooting:mysql-killed-when-pid-max-too-small [2020/01/13 18:45] (current) Joshua Reynolds [Solution] |
||
---|---|---|---|
Line 14: | Line 14: | ||
===== Solution ===== | ===== Solution ===== | ||
Increase ''pid_max'' from ''32768'' to a larger number, such as ''1048576'', like so: | Increase ''pid_max'' from ''32768'' to a larger number, such as ''1048576'', like so: | ||
- | sysctl kernel.pid_max | + | sysctl kernel.pid_max |
- | kernel.pid_max = 32768 | + | kernel.pid_max = 32768 |
- | sysctl -w kernel.pid_max=1048576 | + | sysctl -w kernel.pid_max=1048576 |
- | kernel.pid_max = 1048576 | + | kernel.pid_max = 1048576 |
- | **NOTE**:Sometimes the CRIU feature may cause similar trouble when it resets the PID to restore a process. This causes the PID to be reused too quickly, and can be a problem even with a large ''pid_max'' setting. | + | **NOTE**:Sometimes the CRIU feature may cause similar trouble when it resets the PID to restore a process. This causes the PID to be reused too quickly, and can be a problem even with a large ''pid_max'' setting. |