Bug #49219 | ndb_mgm segfaults when receiving command after ndb_mgmd restart | ||
---|---|---|---|
Submitted: | 30 Nov 2009 17:34 | Modified: | 3 Mar 2010 12:27 |
Reporter: | Erik Ljungstrom | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Linux (CentOS 5.3) |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
Tags: | 7.0.9, NDB_MGM |
[30 Nov 2009 17:34]
Erik Ljungstrom
[30 Nov 2009 17:43]
MySQL Verification Team
Thank you for submitting this bug report. Verified as described.
[17 Feb 2010 14:10]
Magnus Blåudd
Can't get it to crash but running in valgrind shows several warnings while reconnecting after SIGPIPE.
[17 Feb 2010 14:13]
Magnus Blåudd
Occurs also in 6.3
[17 Feb 2010 15:28]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/100640
[3 Mar 2010 10:17]
Magnus Blåudd
Pushed to 6.3.33, 7.0.14 and 7.1.2-beta
[3 Mar 2010 12:27]
Jon Stephens
Documented bugfix in the NDB-6.3.33, 7.0.14, and 7.1.2 changelogs, as follows: Issuing a command in the ndb_mgm client after it had lost its connection to the management server could cause the client to crash. Closed.