Bug #35513 mysqlmanager incorrectly handles PID file
Submitted: 24 Mar 2008 13:35 Modified: 13 Jun 2013 12:35
Reporter: Matthew Lord Email Updates:
Status: Unsupported Impact on me:
None 
Category:Instance Manager Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: instance manger, mysqlmanager, pid, pidfile

[24 Mar 2008 13:35] Matthew Lord
Description:
mysqlmanager will delete a PID file for an existing process

How to repeat:
Use my.cnf file attached:

/etc/init.d/mysql start
# mysqlmanager now running but mysqld failed to start
/etc/init.d/mysql start
# mysqlmanager now started up again and when shutting back down removed the pid file
/etc/init.d/mysql stop
# cannot stop mysqlmanager now as the pid file has been removed

Suggested fix:
We should only be removing the pid file if it contains our PID
[24 Mar 2008 13:39] Matthew Lord
my.cnf to repeat the problem

Attachment: my.cnf (application/octet-stream, text), 312 bytes.

[13 Jun 2013 12:35] Erlend Dahl
MySQL Instance Manager was deprecated in MySQL 5.1 and removed in MySQL 5.5.