Re: MySQL 5.6 startup issues with replication and server-id
Managed to solve the issue, finally. It was a combination of "not-knowing-how" and supposedly bad luck.
First, got rid of those deprecation warnings by following instructions.
In my.cnf:
key_buffer --> key_buffer_size
myisam-recover --> myisam-recover-options
explicit_defaults_for_timestamp = TRUE #added line
Then, since I already tried commenting "bind-address 127.0.0.1" to no avail, I tried "bind-address my.ip.right.here". No luck, but finally "bind-address 0.0.0.0" did the trick. Now I got the server listening.
For some reason one of those bin-files located in /var/log/mysql was corrupted (couldn't be found, errorcode 2 - not 13). Maybe they all were (atleast ...bin000027 and ...bin000026), and possibly due to multiple attempts with different settings, so I removed them all from mysql-bin.index-file. Then a restart and everything was ok. Can't say before tomorrow if the actual replication goes smoothly, but so far so good.
Subject
Views
Written By
Posted
3627
May 07, 2014 11:52PM
Re: MySQL 5.6 startup issues with replication and server-id
1117
May 08, 2014 05:21AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.