Bug #5457 mysqld prints [ERROR] in the log when replication is starting normally
Submitted: 7 Sep 2004 22:58 Modified: 8 Sep 2004 8:50
Reporter: Clint Byrum Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.4-gamma OS:Linux (RedHat Linux 8.0)
Assigned to: Sergei Golubchik CPU Architecture:Any

[7 Sep 2004 22:58] Clint Byrum 
Description:
When the slave SQL and slave I/O threads start in mysqld, it prints [ERROR] when they give their status messages.

040907 15:54:02  mysqld started
040907 15:54:03  InnoDB: Started; log sequence number 0 1024851
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.4-gamma-max-log'  socket: '/tmp/mysql.sock'  port: 3306  Official MySQL-max binary
040907 15:54:03  [ERROR] Slave SQL thread initialized, starting replication in log 'slap-bin.000002' at position 916424576, relay log './grab-relay-bin.000002' position: 903548332
040907 15:54:03  [ERROR] Slave I/O thread: connected to master 'repl@slap:3306',  replication started in log 'slap-bin.000002' at position 916424576

How to repeat:
Setup a MySQL 4.1.4 server as a replication slave and start mysqld.
[8 Sep 2004 8:50] Sergei Golubchik 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html
[8 Sep 2004 8:50] Sergei Golubchik 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

fixed in 4.1.5