Timeline for Why is mariadb.service not restarted by systemd after OOM kill
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 25 at 6:00 | history | suggested | danblack |
add mariadb
|
|
| Apr 24 at 7:02 | review | Suggested edits | |||
| S Apr 25 at 6:00 | |||||
| Apr 24 at 7:01 | answer | added | danblack | timeline score: 0 | |
| Jul 31, 2024 at 7:49 | answer | added | Digdilem | timeline score: 0 | |
| Jun 6, 2024 at 9:07 | comment | added | Lutz | you could change to Restart to on-failure, then it should restart on either signal | |
| Jun 4, 2024 at 12:41 | comment | added | bluefish | @Lutz You are probably right. kernel.org/doc/gorman/html/understand/understand016.html says "If the process has CAP_SYS_RAWIO capabilities, a SIGTERM is sent to give the process a chance of exiting cleanly, otherwise a SIGKILL is sent." But getcaps <PID_of_mysql> is empty. So the question is why is OOM sending sigterm not sigkill. | |
| Jun 4, 2024 at 12:33 | history | edited | bluefish | CC BY-SA 4.0 |
Added more Information
|
| Jun 4, 2024 at 9:11 | comment | added | Lutz | Not an expert here - but the oom killer sends either sigterm(15) or sigkill (9) depending on "something" - so probably it got the sigterm. | |
| Jun 3, 2024 at 23:48 | comment | added | Nasir Riley |
Is it myql.service or mariadb.service? What operating system and release? Add the rest of the service file to the question.
|
|
| Jun 3, 2024 at 20:48 | history | asked | bluefish | CC BY-SA 4.0 |