Bug #88463 | Add service notification via socket | ||
---|---|---|---|
Submitted: | 13 Nov 2017 14:33 | Modified: | 22 Mar 2018 17:33 |
Reporter: | Terje Røsten | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S3 (Non-critical) |
Version: | 8.0.4 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[13 Nov 2017 14:33]
Terje Røsten
[22 Mar 2018 17:33]
Paul DuBois
Posted by developer: Fixed in 8.0.11. For platforms that use systemd, systemd was not always able to infer the state of a double-forked mysqld process. Consequently, systemd would attempt to restart mysqld even when that process terminated with status 1. systemd is now configured to run mysqld as a normal process (Type=notify rather than Type=forking). If the name of a socket file is specified in the environment variable NOTIFY_SOCKET, mysqld attempts to open a connection for communicating with systemd and writes its state changes there.