Error during mysql slave replication

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you describe your replication configuration? Could you post the mysql configuration file on both the master and slave?

Ok I did some additional tests and there is a time to give some result:

First of all I am doing a master-master replication. On Ubuntu 8.04 my configuration works for months so I rather expect an error on Ubuntu 9.04 site. The problem is the configuration is almost the same (exludind server-id of cource). In addition I say I used new my.cnf file delivered with new version of mysql server in 9.04.

My changes are:

# bind-address = 127.0.0.1
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
server-id = 1
log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_ignore_db = include_database_name
binlog_do_db = .......
binlog_do_db = .......

replicate-do-db=......
replicate-do-db=......

auto_increment_increment = 2
auto_increment_offset = 1
slave-skip-errors = 1062

Secondly after reboot
In /var/lib/mysql/

cat relay-log.info
./mysqld-relay-bin.000005
98

0

ls mysqld-relay-*
mysqld-relay-bin.000006 mysqld-relay-bin.000007 mysqld-relay-bin.index

So there is a inconsistency.
After RESET SLAVE; START SLAVE;command

info in relay-log.info and files are consistent.

Because this bug disappear after some update probably may be closed.

Marking invalid as requested by the reporter.