Bug #11886 Failed to get dynamic to connect to: -3
Submitted: 12 Jul 2005 15:12 Modified: 25 Aug 2005 10:08
Reporter: Jonathan Miller Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1 OS:Linux (Linux)
Assigned to: Assigned Account CPU Architecture:Any

[12 Jul 2005 15:12] Jonathan Miller
Description:
Error in mgm protocol parser. cmd: 'get connection parameter' status=1, curr=(null)
Failed to get dynamic port to connect to: -3

Been getting these in the mysql error log. I think you stated that you know what causes this.  We should either fix the cause of these messages, or have a better message that tells the customer what the issues is and that they do not need to worry about it.

Feed back on this would be great.

How to repeat:
Not sure.

Suggested fix:
We should either fix the cause of these messages, or have a better message that tells the customer what the issues is and that they do not need to worry about it.
[20 Jul 2005 3:32] Stewart Smith
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

The fix for BUG#10950 should also fix this.

It has not been pushed yet though.
[20 Jul 2005 15:33] Jonathan Miller
I do not see anything about "Failed to get dynamic to connect to: -3" in BUG#10950. These messages litter the server log when the cluster is down.
[22 Aug 2005 1:35] Stewart Smith
This should be fixed by the fix for BUG#10950. Different symptom for the same problem. Error handling has been improved for this area of the code, so we get nicer error messages. Or at least we should :)
[25 Aug 2005 10:08] Jon Stephens
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

Marked as duplicate per developer comments.