RE: ERROR 1201 - Brian Piere - com.mysql.lists.bugs

7 messages in com.mysql.lists.bugsRE: ERROR 1201

From	Sent On	Attachments
Brian Piere	10 Dec 2003 00:50
Sinisa Milivojevic	10 Dec 2003 05:43
Guilhem Bichot	10 Dec 2003 06:25
Brian Piere	10 Dec 2003 18:59
Sergei Golubchik	11 Dec 2003 01:43
Brian Piere	11 Dec 2003 18:51
Guilhem Bichot	16 Dec 2003 13:33

Subject:	RE: ERROR 1201
From:	Brian Piere (Bri...@PrintsMadeEasy.com)
Date:	12/10/2003 06:59:56 PM
List:	com.mysql.lists.bugs

Hi there,

Thank you for the quick reply. However, nothing I have done will get the master.info file to load. The file is owned by `mysql' (which is what it should be). I have even tried setting the permissions to 777. This is strange because I did have replication working for a while before it stopped, and I never touched the server.

Any command with "CHANGE MASTER TO" fails with the same error.

Do you have any more details on what would trigger that error message?

Thanks, Brian

-----Original Message----- From: Sinisa Milivojevic [mailto:sin...@mysql.com] Sent: Wednesday, December 10, 2003 5:44 AM To: Bri...@PrintsMadeEasy.com Cc: bu...@lists.mysql.com Subject: Re: ERROR 1201

Brian Piere writes:

Hi guys,

I think I found a bug in the replication but I am not quite sure. I am an experienced programmer, I have spent 3 hours searching for a reason/solution to this problem throughout your documentation and newsgroups and have come up with nothing.

I am using... Ver 4.0.15-standard for pc-linux on i686 with RedHat 8 The same version of Mysql is running on both the master and the slave.

I have had replication running for about a month now. It was working fine for a while and then it just stopped. When I run START SLAVE I get the error.

ERROR 1201: Could not initialize master info structure, check permissions on master.info

I have checked the permissions on the file and even tried setting to 777 to be sure. The same problem. This is the contents of the file.

-------------- server-bin.001 230799702 www.printsmadeeasy.com UserName Password 3306 60

-----

I don't want to run any commands such as "RESET SLAVE" or take a new snapshot of the DB and start clean because I bet that it will start working fine again. If I do this I might need to wait another week to see it fail again. So I am a little bit limited in troubleshooting the problem.

What do you think?

HI!

Please re-check ownerships and mode of the file.

Check that the owner is user under whose UID MySQL server is running, unless it is ran by root.

Sincerely,