MySQL Bugs: #22989: START SLAVE causes Error on COM_REGISTER

Bug #22989	START SLAVE causes Error on COM_REGISTER_SLAVE: 1105 'Wrong parameters to functi
Submitted:	4 Oct 2006 19:06	Modified:	29 Mar 2008 13:22
Reporter:	Ian Gulliver
Status:	Closed
Category:	Server: Replication	Severity:	S2 (Serious)
Version:	5.0.18	OS:	Linux (Debian Sarge)
Assigned to:	Sergey Vojtovich	Target Version:	5.0+,5.1.24
Triage:	D2 (Serious)

Description:
Starting slave fails to start the slave IO thread.  The log records:

061004 13:00:08 [Note] Slave SQL thread initialized, starting replication in log 'FIRST'
at position 0, relay log './db2-relay-bin.000001' position: 4
061004 13:00:08 [Note] Slave I/O thread: connected to master
'db2@db1.waytechnology.coresense.com:3306',  replication started in log 'FIRST' at
position 4
061004 13:00:08 [ERROR] Error on COM_REGISTER_SLAVE: 1105 'Wrong parameters to function
register_slave'
061004 13:00:08 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4

How to repeat:
Exact cause unknown; environment has both MyISAM and InnoDB tables, stored procedures and
triggers.

Thank you for a problem report. Please, try to repeat with a newer version of master and
slave, 5.0.24a. In case of similar problem, please, send my.cnf from both servers and
upload problematic binary log that can not be replicated.

I'm afraid I can't do either of these.  We're bound to the MySQL version by distribution
needs and the binary log contains sensitive customer info.

If this problem is a result of a bug, please, note, that the bug will be fixed in the
latest version anyway.

To check if it is a bug we need a repeatable test case. Can you try to send statement at
position 4 of that ./db2-relay-bin.000001 (as private comments, or with data changed)?
What version do you have as slave? 5.0.18? Then what version master is?

The mysterious error turned out to have nothing to do with the log on either machine; the
slave couldn't handshake because its report-host variable was too long.

So, can we close this bug report as not a bug now?

Looks like a bug to me; MySQL should either support arbitrary-length report-host names or
provide a useful error when it fails due to a long hostname.

This is either a bug, or, if there is some well-known hardcoded limit, it should be
described at http://dev.mysql.com/doc/refman/5.0/en/replication-options.html.

See also BUG#19328

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/commits/41365

ChangeSet@1.2594, 2008-01-29 18:05:14+04:00, svoj@mysql.com +1 -0
  BUG#22989 - START SLAVE causes Error on COM_REGISTER_SLAVE: 1105
              'Wrong parameters to functi
  
  START SLAVE reports vague error when it fails to register on master:
  "Wrong parameters to function register_slave".
  
  If master failed to register slave because of too long
  'report-host'/'report-user'/'report-password', return better error
  messages:
  "Failed to register slave: too long 'report-host'"
  "Failed to register slave: too long 'report-user'"
  "Failed to register slave; too long 'report-password'"
  
  No test case for this fix.

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/commits/41504

ChangeSet@1.2569, 2008-01-31 18:51:20+04:00, svoj@mysql.com +1 -0
  BUG#22989 - START SLAVE causes Error on COM_REGISTER_SLAVE: 1105
              'Wrong parameters to functi
  
  START SLAVE reports vague error when it fails to register on master:
  "Wrong parameters to function register_slave".
  
  If master failed to register slave because of too long
  'report-host'/'report-user'/'report-password', return better error
  messages:
  "Failed to register slave: too long 'report-host'"
  "Failed to register slave: too long 'report-user'"
  "Failed to register slave; too long 'report-password'"
  
  No test case for this fix.

Pushed into 5.1.24-rc

Pushed into 5.0.60

Pushed into 6.0.5-alpha

Bugfix documented as follows in the 5.0.60, 5.1.24, and 6.0.5 changelogs:

        The inspecific error message Wrong parameters to
        function register_slave resulted when START SLAVE failed to register on the
        master due to excess length of any the slave server options --report-host,
        --report-user, or --report-password. An error message specific to each
        of these options is now returned in such cases. The new error messages
        are:
        
        Failed to register slave: too long 'report-host'
        
        Failed to register slave: too long 'report-user'
        
        Failed to register slave; too long 'report-password'

Also documented in 5.1.23-ndb-6.3.11 changelog.