Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:troubleshooting:mysql-killed-when-pid-max-too-small [2019/03/20 20:33] Lisa Clarke Copyediting |
litespeed_wiki:troubleshooting:mysql-killed-when-pid-max-too-small [2019/03/20 20:34] Lisa Clarke [Solution] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| ====== LiteSpeed Kills Apps Using Recycled PIDs ====== | ====== LiteSpeed Kills Apps Using Recycled PIDs ====== | ||
| A small ''pid_max'' value may cause applications to be accidentally killed when they are using a recycled PID. | A small ''pid_max'' value may cause applications to be accidentally killed when they are using a recycled PID. | ||
| Line 13: | 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. | ||