Bug #12216 Permission error does not show in slave status
Submitted: 27 Jul 2005 16:42 Modified: 19 Apr 2007 7:55
Reporter: Jonathan Miller Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.1 OS:Linux (Linux)
Assigned to: Assigned Account CPU Architecture:Any

[27 Jul 2005 16:42] Jonathan Miller
Description:
The permissions error does not show when you do a "show slave status\G;"

050727 18:29:44 [ERROR] Slave I/O thread: error connecting to master 'rep@ndb08:3306': Error: 'Host 'ndb10.mysql.com' is not allowed to connect to this MySQL server'  errno: 1130  retry-time: 1  retries: 86400

mysql> show slave status\G;
*************************** 1. row ***************************
             Slave_IO_State: Connecting to master
                Master_Host: ndb08
                Master_User: rep
                Master_Port: 3306
              Connect_Retry: 1
            Master_Log_File:
        Read_Master_Log_Pos: 4
             Relay_Log_File: ndb10-relay-bin.000003
              Relay_Log_Pos: 102
      Relay_Master_Log_File:
           Slave_IO_Running: Yes
          Slave_SQL_Running: Yes
            Replicate_Do_DB:
        Replicate_Ignore_DB:
         Replicate_Do_Table:
     Replicate_Ignore_Table:
    Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
                 Last_Errno: 0
                 Last_Error:
               Skip_Counter: 0
        Exec_Master_Log_Pos: 0
            Relay_Log_Space: 102
            Until_Condition: None
             Until_Log_File:
              Until_Log_Pos: 0
         Master_SSL_Allowed: No
         Master_SSL_CA_File:
         Master_SSL_CA_Path:
            Master_SSL_Cert:
          Master_SSL_Cipher:
             Master_SSL_Key:
      Seconds_Behind_Master: NULL
1 row in set (0.00 sec)

How to repeat:
Start slave replicating from a master that it does not have permissions on.
[27 Jul 2005 18:53] Matthew Lord
This has always been true.  There are other reasons for replication not to be working which aren't listed in the last_error column.

This may be classified as a feature request but I will leave that for development.
[19 Apr 2007 7:55] Mats Kindahl
The reason that it does not show is that the Last_error only shows errors for the SQL thread, not for the I/O thread. With the patch for BUG#24954, both errors for the SQL thread and the I/O thread will be shown.