Bug #50223 | mysql is not running but lock exists | ||
---|---|---|---|
Submitted: | 11 Jan 2010 9:30 | Modified: | 7 Dec 2016 16:14 |
Reporter: | lalit gera | Email Updates: | |
Status: | Unsupported | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | 5.0.64-enterprise MySQL Enterprise Server (Commercial) | OS: | Linux (Red Hat EnterPrise edition ) |
Assigned to: | CPU Architecture: | Any |
[11 Jan 2010 9:30]
lalit gera
[11 Jan 2010 10:31]
Valeriy Kravchuk
What exact OS and MySQL server version, x.y.z, you are talking about?
[11 Jan 2010 12:56]
lalit gera
Mysql version : 5.0.64-enterprise MySQL Enterprise Server (Commercial) Linux : Linux version 2.6.9-55.ELsmp
[11 Jan 2010 23:24]
Sveta Smirnova
Thank you for the feedback. This looks like not a bug, but MySQL PID file left after system restart. (I assume MySQL server was not stopped properly?) Please check if PID file exists while MySQL server is not running and if yes, remove PID file.
[12 Feb 2010 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[7 Dec 2016 16:14]
Yngve Svendsen
Posted by developer: This relates to EOL (no longer supported) versions of MySQL Server. Thus closing.