Thanks, but actually I just found the answer a second ago, and I'm including it here so hopefully it'll be archived around the internet and whatnot so the next poor sap like me with the same problem who tries to find it can:
What happened was that somehow the servername-relay-bin.009 file got corrupted, and that caused the whole mess. I noticed that I had a list of files like so: servername-relay-bin.009 servername-relay-bin.010 servername-relay-bin.011 servername-relay-bin.012 servername-relay-bin.013 servername-relay-bin.014 servername-relay-bin.015 servername-relay-bin.016 etc.. and they were all 4 bytes except the 009 one which was 1 byte. They were confusing me because I had run "reset master" and "reset slave" a few times while trying to figure this problem out, but those still were sitting there. So, all I did was copy one of the good servername-relay-bin.010 files over the bad servername-relay-bin.009 file, and that solved it. I don't know if this would be a good idea on a server where that might mess up the syncing (or where the broken relay-bin file was different from the non-broken one), but in my case I could do that and now I just need to copy the current database over to that server and start fresh. I hope I have explained that somewhat clearly, it's late here, but yeah, essentially the whole problem can be summed up as this: A corrupted servername-relay-bin file will cause the master.info and relay-log.info to be created but be empty, and when you try "slave start" it'll tell you: "ERROR 1201: Could not initialize master info structure, check permisions on master.info" Hope that helps someone down the line! Andrew > From: "Lightware Software" <[EMAIL PROTECTED]> > Date: Thu, 29 Jan 2004 10:25:24 +0200 > To: [EMAIL PROTECTED] > Subject: Re: weird replication problem with master.info being created empty > > Maybe you should check if the ip address resolved for the > master's url is correct ? > > Also try using CHANGE MASTER TO > MASTER_HOST='<master host name>', > MASTER_USER='<replication user name>', > MASTER_PASSWORD='<replication password>'; > > and then START SLAVE; and see what happens. > > regards Jurgen > > >> Tried that, but no luck, they get recreated, but they >> still have 0 bytes in >> them. This is really driving me crazy because although >> it's come up before >> on lists, noone has ever really had an answer for it that >> makes sense. The >> url I mentioned earlier does say something about the >> hostname of the server >> changing, but that isn't the case here, the hostname is >> the same as always >> (should have added that in the first place). >> >> >>> >>> You need to shutdown mysql, delete the master.info and >>> relay-log.info files and then start mysql again. >>> >>> The reason for this is because if the info files are >>> present then mysql uses them as is and only recreates >> them >>> from my.ini or my.cnf if absent. >>> >>> This should get your replication going again. >>> regards Jurgen >>> >>>> Have a problem, running a master/slave setup which >> worked >>>> until tonight and >>>> mysteriously broke with no changes to the setup at >> all. >>>> My server starts up >>>> fine, but the master.info and relay-log.info that are >>>> created are 0 bytes >>>> and empty. In the logfile, I get this: >>>> >>>> 040128 23:00:29 Error reading slave log configuration >>>> 040128 23:00:29 Failed to initialize the master info >>>> structure >>>> >>>> and when I run "slave start" >>>> >>>> I get this: >>>> >>>> ERROR 1201: Could not initialize master info >> structure, >>>> check permisions on >>>> master.info >>>> >>>> The blank files in question have okay permissions >>>> (mysql:mysql) as does the >>>> directory they're in, and they ARE getting written to, >>>> just nothing is being >>>> written. The my.cnf file also has appropriate >> permissions >>>> and is readable by >>>> mysql (so it's not a case of the server not knowing >> what >>>> to write in those >>>> files). Moreover, nothing has changed on the server >>>> config at all. I've >>>> tried resetting the master and slave but it doesn't >> help. >>>> >>>> I was running version 4.0.12-0 but just upgraded to >>>> 4.0.17-0 which hasn't >>>> helped at all, and the only thing I can find in the >>>> archives are similar >>>> problems with the same error number that either turn >> out >>>> to be legit >>>> permissions errors (which isn't the case here), and >> this: >>>> http://lists.mysql.com/bugs/15135 which I don't really >>>> follow as far as what >>>> the final solution was. >>>> >>> >> > __________________________________________________________________________ > http://www.webmail.co.za/dialup Webmail ISP - Cool Connection, Cool Price > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
