It's impossible to say pretty much without more information. Have you checked the error log on the slave? How about 'SHOW SLAVE STATUS'? Did your "backup guy" gzip all binlogs, if so that would most definitely stop replication.
Atle - Flying Crocodile Inc, Unix Systems Administrator On Fri, 3 Jun 2005 [EMAIL PROTECTED] wrote: > > I took a couple of days vacation last week and naturally the /data > partition of my database server filled up because of something I was > running and had forgotten about. So my backup guy, thinking to help > out, gzipped all my .bin logs. Now I am noticing replication seems to > have stopped on my other server. Not sure if the two events are related > or not. It could be that things got all hosed up not because of the > gzipping but because the partition filled up in the first place? > Anyway, what do I do now? Do I need to do a new dump and start > replication all over again? > > --ja > > -- > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
