Bug #81838 | Socket lockfile is not cleaned up if write fails, leading to crashlooping. | ||
---|---|---|---|
Submitted: | 13 Jun 2016 21:14 | Modified: | 2 Sep 2016 1:54 |
Reporter: | David Gow (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | 5.7.11, 5.7.13 | OS: | Ubuntu (Kernel 3.13.0-87-generic) |
Assigned to: | CPU Architecture: | Any |
[13 Jun 2016 21:14]
David Gow
[14 Jun 2016 8:17]
MySQL Verification Team
Hello David Gow, Thank you for the report and feedback! Thanks, Umesh
[2 Sep 2016 1:54]
Paul DuBois
Posted by developer: Noted in 8.0.1 changelog. During startup, the server creates a lock file for the Unix socket file (for example, mysql.sock.lock as a lock file for mysql.sock). If the server failed to write the process ID to the lock file, it failed to remove that file, which could cause subsequent server startups to fail until the file was removed manually.