3 added 85 characters in body
source | link

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.

EDIT: Did you mask the actual binlog filename in show master status output? I'm asking because the setting in my.cnf does not match the binlog name. If so, could you provide the actual filename, and the output of show slave status like Aaron mentioned? So far other than name mismatch for bin-log, nothing stands out in your my.cnf file.

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.

EDIT: Did you mask the actual binlog filename in show master status output? I'm asking because the setting in my.cnf does not match the binlog name. If so, could you provide the actual filename, and the output of show slave status like Aaron mentioned?

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.

EDIT: Did you mask the actual binlog filename in show master status output? I'm asking because the setting in my.cnf does not match the binlog name. If so, could you provide the actual filename, and the output of show slave status like Aaron mentioned? So far other than name mismatch for bin-log, nothing stands out in your my.cnf file.

2 added 192 characters in body
source | link

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.

EDIT: Did you mask the actual binlog filename in show master status output? I'm asking because the setting in my.cnf does not match the binlog name. If so, could you provide the actual filename, and the output of show slave status like Aaron mentioned?

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.

EDIT: Did you mask the actual binlog filename in show master status output? I'm asking because the setting in my.cnf does not match the binlog name. If so, could you provide the actual filename, and the output of show slave status like Aaron mentioned?

1
source | link

Could it be that my.cnf file is mis-configured and master binary logs are named as relay logs?

Or maybe your master has hard coded replication settings in my.cnf file, which are picked up at MySQL instance restart.