Benjamin Pflugmann writes: >Hi. Does the error log of the master contain any error?
Nothing at all in the master logs. >Does the new log position make sense? Yes, the position is ok, and the slave gets the updates. Its just that strange error messages about dropped connections and 0-byte packets, and only on one of the slaves. >It hangs always on the same offset. So it doesn't get forward at >all. That's why I assume some priciple error. No, no, the log position changes as the updates are arriving from the master. >There is some file called master.info in the database directory of >the client. Could you redo the reload and delete that file after you >stop the slave in the process. No, nothing, still the same message. Thanks for trying to track this, but I dont think that this is some principle problem, because I have a whole bunch of servers running replication, and running it for quite some time, they are all working fine, except for these messages on jus one slave. I suspect that this is either some really wierd quirk in replication process or I am overlooking something in the configuration of that particular server, even though I checked everything thousand times already. >Bye, > Benjamin. >On Thu, Oct 04, 2001 at 10:27:16AM +0200, [EMAIL PROTECTED] wrote: >> Benjamin Pflugmann writes: >> >> >Hi. My first guess would be that somehow the slave got out of >> >sync. I would try to update the slave by hand and see what happens >> >after restart. >> >> >Sorry, I don't see what could be the cause. >> >> I tried the following: >> >> on master: >> >> reset master >> >> on all slaves: >> >> slave stop >> >> drop table xxx load table xxx from master ... repeat for every >> replicated table ... >> >> slave start >> >> Still the same problem. >> >> >Bye, >> >> > Benjamin. >> >> >> >On Tue, Oct 02, 2001 at 06:07:29PM +0200, [EMAIL PROTECTED] >> >wrote: [...] >> >> I have 28 linux boxes configured identically, 27 as slaves, one >> >> as master. On all 27 slaves, everything works fine, but only on >> >> one I have strange errors in the logs: >> >> >> >> 011002 17:49:49 Slave: received 0 length packet from server, >> >> apparent master shutdown: (0) 011002 17:50:49 Slave: Failed >> >> reading log event, reconnecting to retry, log 'cp4230-bin.005' >> >> position 664857 011002 17:50:49 Slave: reconnected to master >> >> 'repl@xxx:3306',replication resumed in log 'xxx-bin.005' at >> >> position 664857 011002 17:51:49 Slave: received 0 length packet >> >> from server, apparent master shutdown: (0) >> >> >> >> This repeats every minute. >> >[...] >> >> >> >-- [EMAIL PROTECTED] >> >> >> -- Alex Ivanisevic, 2e systems Tel: +49 6192 978 497 Handy: +49 >> 0174 310 9333 >-- [EMAIL PROTECTED] -- Alex Ivanisevic, 2e systems Tel: +49 6192 978 497 Handy: +49 0174 310 9333 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
