Bug #10860 | rpl_openssl test hangs | ||
---|---|---|---|
Submitted: | 25 May 2005 14:06 | Modified: | 12 Aug 2005 0:29 |
Reporter: | Kathiravan Velusamy | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1.10a | OS: | HP/UX (HP-Unix) |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
[25 May 2005 14:06]
Kathiravan Velusamy
[12 Jul 2005 2:35]
[ name withheld ]
I'm seeing this on recent Fedora Core (4 and up) as well. What is happening is simple enough: the replssl user is defined as replssl@'%', which the server considers less specific than the anonymous user account ''@'buildmachine%'. So the slave's login requests are taken as being anonymous and hence fail for lack of permissions. I am not sure why this is seen on some platforms and not others --- it probably has something to do with the local DNS configuration. But it's definitely the test script's fault for setting up a bogus combination of users. (Or maybe the bug is that the sorting rules for users suck. But it's not specifically an SSL issue at all.) By the by, I suspect that the openssl_1 test is actually failing invisibly, and that the "ssl users" are being connected as anonymous just like replssl. It would be entertaining to see how much of the regression suite fails with anonymous logins disabled...
[10 Aug 2005 20:30]
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/28131
[12 Aug 2005 0:29]
Jim Winstead
Fixed in 5.0.12.
[5 Oct 2005 19:32]
[ name withheld ]
The proposed patch does not work for me, because the slave tries to log in as replssl@actual.machine.name, not replssl@localhost. Again, this issue probably has some dependence on the local DNS configuration, but that's the behavior I see (at least in 4.1).