Bug #14315 mysqlmanager consumes all available CPU
Submitted: 26 Oct 2005 3:19 Modified: 27 Oct 2005 16:03
Reporter: Kenneth Girrard Email Updates:
Status: Duplicate Impact on me:
None 
Category:Instance Manager Severity:S2 (Serious)
Version:5.0.15 OS:Linux (RHEL 4 U2)
Assigned to: CPU Architecture:Any

[26 Oct 2005 3:19] Kenneth Girrard
Description:
mysqlmanager correctly starts multiple MySQL instances but then appears to be spinning,  consuming all available CPU until terminated. Normal behavior otherwise, including accepting connections, executing commands, starting/stopping instances.
UserID   PID   CPU%   Process
mysql     4969 99.5  /usr/sbin/mysqlmanager --user=mysql...
mysql     4977  0.6  /usr/sbin/mysqld --no-defaults --po...
mysql     4978  0.5  /usr/sbin/mysqld --no-defaults --por...

Installed from Redhat Linux RHEL 4 RPMs

How to repeat:
Two instances launced from the same binary installation; no directories or files in common. Defaults for all [manager] parameters except a couple file locations:

log = /var/lib/mysql/mysqlmanager.log
pid-file = /var/lib/mysql/mysqlmanager.pid
socket = /var/lib/mysql/mysqlmanager.sock
bind-address = (No default value)
port =  2273
password-file = /etc/mysqlmanager.passwd
default-mysqld-path = /usr/sbin/mysqld
monitoring-interval = 20
run-as-service = FALSE
user = mysql
[27 Oct 2005 16:03] Valeriy Kravchuk
Duplicate of http://bugs.mysql.com/bug.php?id=14388.