Bug #74445 Unhelpful error for IO Thread

Submitted: 20 Oct 2014 7:47 Modified: 20 Oct 2014 13:07
Reporter: Daniël van Eeden Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:5.6.20, 5.6.22 OS:Any
Assigned to: CPU Architecture:Any
Tags: replication, usability

[20 Oct 2014 7:47] Daniël van Eeden
Description:
Situation: A 5.6 slave replicating from an older release after upgrading the slave.

Show in 'SHOW SLAVE STATUS' output:
Slave_IO_Running: Connecting
Last_IO_Errno: 2049
Last_IO_Error: error connecting to master 'xxxx@xxxxxxx:3306' - retry-time: 60  retries: 5

The perror utility is of no help.  
$ perror 2049
Illegal error code: 2049

It it listed in the reference manual:
http://dev.mysql.com/doc/refman/5.6/en/error-messages-client.html#error_cr_secure_auth

Lucklily I was able to change the password hash for the replication user on the master from a pre-4.1 hash to the newer format. I don't know

- It seems like it is not possible to disable secure_auth for the I/O thread?
- Why isn't there a more helpfull error message? (e.g.: 'error connecting to master: error 2049 (CR_SECURE_AUTH): please upgrade the password hash on the master, pre-4.1 hash is not allowed')
- Shouldn't this be documented on http://dev.mysql.com/doc/refman/5.6/en/replication-upgrade.html ?

How to repeat:
See description

Suggested fix:
- Report better error message
- Update documentation
[20 Oct 2014 12:08] MySQL Verification Team
Hello Daniël,

Thank you for the bug report.
Observed issue while replicating from 5.1.73->5.6.22.

Thanks,
Umesh
[20 Oct 2014 13:07] Daniël van Eeden
I've created Bug #74457 for the documentation part.
[25 Nov 2020 20:19] Olatunji Ayodeji
I can't connect through the workbench

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.