Bug #12833 | ndb_mgm: setting clusterlog options doesn't work as advertised | ||
---|---|---|---|
Submitted: | 26 Aug 2005 13:34 | Modified: | 1 Sep 2005 14:41 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 4.1.12 | OS: | Linux (linux) |
Assigned to: | Tomas Ulin | CPU Architecture: | Any |
[26 Aug 2005 13:34]
Hartmut Holzgraefe
[26 Aug 2005 13:40]
Geert Vanderkelen
Verfied. Same goes for 5.0.11: ndb_mgm> ALL CLUSTERLOG INFO=15 ERROR=15; Connected to Management Server at: localhost:1186 Invalid loglevel specification: INFO=15 ERROR=15 Invalid loglevel specification: INFO=15 ERROR=15 Works individually: ndb_mgm> ALL CLUSTERLOG INFO=15; Executing CLUSTERLOG on node 2 OK! Executing CLUSTERLOG on node 3 OK! Best regards, Geert
[31 Aug 2005 20:01]
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/internals/29132
[31 Aug 2005 20:02]
Tomas Ulin
fixed in 4.1.15 and 5.0.12
[1 Sep 2005 14:41]
Paul DuBois
Noted in 4.1.15, 5.0.12 changelogs.