Re: replication problems

2002-06-18 Thread Jeff Hill 

I'm having the same problems, but I've noticed that the reported error 
doesn't seem to be  a real failure. The databases seem to be updated correctly.

When I look at my slave error log, I can see that the at position  is 
a number that always matches the size of the log file on the master. This 
cannot be a coincidence. Is it perhaps trying to read past the end of the 
log file or something?

I haven't really looked at MySql in years because it's been working fine, 
but in setting up replication, I see now that I have some Innobase tables, 
some not. Haven't a clue how that happened, but my my.cnf does not have the 
related directives uncommented. This could be related to problems reading 
the logs, I assume?

I'm doing some testing, but any suggestions appreciated. I don't have a 
spare server to play with and the master is our main production server, so 
I have to play carefully to remain employed.

I tried with both master and slave running mysql-3.23.47-pc-linux-gnu-i686 
and then tried moving the slave to 3..23.51 with the same error results.

Thanks for any assistance,

Jeff



Jeff Hill
www.HRpost.com
Ph: 416-604-7251
Fx: 647-439-1414




-
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 mysql-unsubscribe-##L=##[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: replication problems -- resolution

2002-06-18 Thread Jeff Hill 

Just to let you know that when I installed 3.23.51 binary on both Debian 
Linux boxes, same problem, but when I re-installed the 3.23.49a  binary on 
both boxes the problem went away. Uncertain why.

Regards,

Jeff Hill

At 08:25 AM 18/06/2002 -0400, Jeff Hill wrote:
I'm having the same problems, but I've noticed that the reported error 
doesn't seem to be  a real failure. The databases seem to be updated correctly.

When I look at my slave error log, I can see that the at position  
is a number that always matches the size of the log file on the master. 
This cannot be a coincidence. Is it perhaps trying to read past the end of 
the log file or something?

I haven't really looked at MySql in years because it's been working fine, 
but in setting up replication, I see now that I have some Innobase tables, 
some not. Haven't a clue how that happened, but my my.cnf does not have 
the related directives uncommented. This could be related to problems 
reading the logs, I assume?

I'm doing some testing, but any suggestions appreciated. I don't have a 
spare server to play with and the master is our main production server, so 
I have to play carefully to remain employed.

I tried with both master and slave running mysql-3.23.47-pc-linux-gnu-i686 
and then tried moving the slave to 3..23.51 with the same error results.

Thanks for any assistance,

Jeff



Jeff Hill
www.HRpost.com
Ph: 416-604-7251
Fx: 647-439-1414




-
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 mysql-unsubscribe-##L=##[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php



Jeff Hill, Editor, HRpost / HR On-Line
www.HRpost.com
Ph: 416-858-3440
Fx: 647-439-1414




-
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 mysql-unsubscribe-##L=##[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php