Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Not a Bug
-
10.4.6
Description
Something caused 10.4.6 to fail on startup on our upgraded (from 10.3.16) node. I can't find any documentation as to what can be done to fix this, other then a rollback
[Note] Reading Master_info: 'master-db1.info' Relay_info:'relay-log-db1.info'
|
[Warning] Neither \-\-relay-log nor \-\-relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=db2-relay-bin' to avoid this problem.
|
[ERROR] Failed to open the relay log './mysql-relay-bin-db1.000002' (relay_log_pos 134241)
|
[ERROR] Could not find target log during relay log initialization
|
[ERROR] Initialized Master_info from 'master-db1.info' failed
|
[Note] Added new Master_info 'db1' to hash table
|
[Warning] Reading of some Master_info entries failed
|
[ERROR] Failed to initialize multi master structures
|
[ERROR] Aborting
|
but mysqlbinlog shows the specified relay_log_pos is actually present:
mysqlbinlog /var/lib/mysql/mysql-relay-bin-db1.000002|tail
# at 134210
{{#190628 11:25:49 server id 1 end_log_pos 133942 CRC32 0x8acb5d0c Xid = 4956}}
COMMIT/!/;
# at 134241
{{#190628 11:25:59 server id 2 end_log_pos 134264 CRC32 0xe059508d Stop}}
DELIMITER ;
# End of log file
ROLLBACK /* added by mysqlbinlog */;
/!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE/;
/!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0/;