MySQL Bugs: #35737: master.info gets corrupted at the time of sude reboot

Bug #35737	master.info gets corrupted at the time of sude reboot
Submitted:	1 Apr 2008 10:32	Modified:	15 May 2008 13:47
Reporter:	Gaurang Popat	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.0.45, for pc-linux-gnu (i686)	OS:	Linux (RHEL 5.5)
Assigned to:		CPU Architecture:	Any

Description:
Hi ,

 We are using master-master replication.

 Following is the content of my.cnf on server 1

set-variable = max_connections=10000
set-variable = table_cache=256
set-variable = thread_cache=10
set-variable = read_buffer_size=524288
set-variable = read_rnd_buffer_size=1048576
set-variable = sort_buffer_size=8388608
set-variable = innodb_buffer_pool_size=34217728
set-variable = innodb_flush_log_at_trx_commit=1
set-variable = innodb_log_buffer_size=8388608
set-variable = long_query_time=5
log-bin=/usr/abc/mysql/lreericsson-bin
relay-log=/usr/abc/mysql/lreericsson-bin-relay-bin
server-id=101
auto_increment_increment=2
auto_increment_offset=2
replicate-same-server-id=0
master-host=10.77.210.229
master-port=3306
master-user=posuser
master-password=pos-user
master-connect-retry=60
replicate-do-db=osfdb
set-variable = sync_binlog=1
master-ssl=0

 Following is the content of my.cnf on server 2

[mysqld]
set-variable = max_connections=10000
set-variable = table_cache=256
set-variable = thread_cache=10
set-variable = read_buffer_size=524288
set-variable = read_rnd_buffer_size=1048576
set-variable = sort_buffer_size=8388608
set-variable = innodb_buffer_pool_size=34217728
set-variable = innodb_flush_log_at_trx_commit=1
set-variable = innodb_log_buffer_size=8388608
set-variable = long_query_time=5
log-bin=/usr/abc/mysql/RHEL4SERVER-bin
relay-log=/usr/abc/mysql/RHEL4SERVER-bin-relay-bin
server-id=100
auto_increment_increment=2
auto_increment_offset=1
replicate-same-server-id=0
master-host=10.77.210.10
master-port=3306
master-user=posuser
master-password=pos-user
master-connect-retry=60
replicate-do-db=osfdb
set-variable = sync_binlog=1
master-ssl=0

In case of sudo reboot I get following error in 

080331 18:36:59 [ERROR] Slave I/O thread: error connecting to master '@10.77.210.229:0': Error: 'Lost connection to MySQL server at 'reading initial communication packet', system error: 113'  errno: 2013  retry-time: 3306  retries: 86400

Following is the content of master.info

14
RHEL4SERVER-bin.000001
46015434
10.77.210.229

posuser
0
3306
60
0

0
~

I assume that the credential is deleted from master.info and one blank line is added in master.info that casue this problem

How to repeat:
-setup master master replication 
-sudo reboot one server

Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

As master.info got corrupted during not clean mysql shutdown problem can not be considered MySQL bug. Please read user notes to http://dev.mysql.com/doc/refman/5.1/en/replication-problems.html for workaround.

Hi Sveta ,

Thank you very much for quick reply.I agree with you that as master.info got corrupted during not clean mysql shutdown problem can not be considered MySQL bug.
Now I am only concern with workaround, I have update corrupted master.info by just giving credential at proper line number and then restarted of mysql had started replication.
So can I consider this as workaround as I don’t find any other from http://dev.mysql.com/doc/refman/5.1/en/replication-problems.html

I past here the content of currpted master.inof and updated master.info for your reference

*********** corrupted master.info**********8
14
r2-ind10-bin.000001
46015434
10.77.210.45

posuser
0
3306
60
0

0

************* updated master.info **********8
14
r2-ind10-bin.000001
46415258
10.77.210.45
posuser
pos-user
3306
60
0

0

0

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Hi,

I could see this sometimes while stoping  mysql and then start it again.

Can you please go through the all files once, may be I am missing something.
Please note that we have 2 NIC cards for both of the nodes.

Regards,
Gaurang

As Sveta told you two times before. Bugs system is for reporting bugs. 

When you want to get support please contact our sales center:
You can find all necessary data here: 

http://www.mysql.com/about/contact/

Or use  http://www.mysql.com/support/

when you want to get free support then please use: http://forums.mysql.com/