Replication troubles
I thought I had most things figured out for our challenging replication setup. However this morning we have a failure I can't figure out... Here are the errors: 030613 5:13:50 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'binary-log.035' at position 11496356 030613 5:13:50 Error reading packet from server: log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master (server_errno=1236) 030613 5:13:50 Got fatal error 1236: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master' from master when reading data from binary log 030613 5:13:50 Slave I/O thread exiting, read up to log 'binary-log.035', position 11496356 In the case of both the master and the slave the max_allowed_packet is set to 1047552. In both cases I raised it to 2047552 just to be generous. Same failure. I can stop and start this slave as it's not in live production, I can't stop and start the master which feeds live discussion boards. Any ideas? Best Regards, Bruce -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Replication troubles
Hi Bruce, I dont know the solution, but error 1236 is a server issue as described below. Starting and stopping the slave wont help anything. Are you sure that the servers binary log is not corrupted ? Try to reset the master. 4.10.7.5 RESET MASTER (master) Deletes all binary logs listed in the index file, resetting the binlog index file to be empty. Previously named FLUSH MASTER . By doing this you eliminate all old master file and start over at FILENAME-bin-001 position 79. Best regards Nils Valentin Tokyo/Japan 2003 6 13 21:23Bruce Dembecki : I thought I had most things figured out for our challenging replication setup. However this morning we have a failure I can't figure out... Here are the errors: 030613 5:13:50 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'binary-log.035' at position 11496356 030613 5:13:50 Error reading packet from server: log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master (server_errno=1236) 030613 5:13:50 Got fatal error 1236: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master' from master when reading data from binary log 030613 5:13:50 Slave I/O thread exiting, read up to log 'binary-log.035', position 11496356 In the case of both the master and the slave the max_allowed_packet is set to 1047552. In both cases I raised it to 2047552 just to be generous. Same failure. I can stop and start this slave as it's not in live production, I can't stop and start the master which feeds live discussion boards. Any ideas? Best Regards, Bruce -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Replication troubles
In the case of both the master and the slave the max_allowed_packet is set to 1047552. In both cases I raised it to 2047552 just to be generous. In order for changes to the max_allowed_packet to take effect, you'll need to restart mysqld on that server. Cheers, Andrew -Original Message- From: Bruce Dembecki [mailto:[EMAIL PROTECTED] Sent: Friday 13 June 2003 13:24 To: [EMAIL PROTECTED] Subject: Replication troubles I thought I had most things figured out for our challenging replication setup. However this morning we have a failure I can't figure out... Here are the errors: 030613 5:13:50 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'binary-log.035' at position 11496356 030613 5:13:50 Error reading packet from server: log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master (server_errno=1236) 030613 5:13:50 Got fatal error 1236: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master' from master when reading data from binary log 030613 5:13:50 Slave I/O thread exiting, read up to log 'binary-log.035', position 11496356 In the case of both the master and the slave the max_allowed_packet is set to 1047552. In both cases I raised it to 2047552 just to be generous. Same failure. I can stop and start this slave as it's not in live production, I can't stop and start the master which feeds live discussion boards. Any ideas? Best Regards, Bruce -- 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]
RE: Replication troubles
Just a follow up- I got replication working, the error was (as usual) simple... in the MySQL Replication HOWTO, it says 'Add the following to my.cnf on the slave(s): I of course (:P) put them at the end of the file, they must go under [mysqld]. But hey, it works! Thanks -Original Message- From: Jeremy D . Zawodny [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 25, 2001 3:30 AM To: Bryan Coon Cc: [EMAIL PROTECTED] Subject: Re: Replication troubles On Fri, Mar 23, 2001 at 10:45:00AM -0800, Bryan Coon wrote: I have two machines which I am trying to set up replication on. I followed the howto as describe in the manual, and everything seemed to be okay (i.e. no errors), but it simply doesn't work. Heres what I did on the master: 1. Copied /usr/share/my-large.cnf to /etc/my.cnf 2. my.cnf already had log-bin, server-id=1, so I didnt touch anything else 3. Granted file to user repl as in howto 4. Shut down master 5. Tarred data dir, copied it to slave 6. Restarted master Heres what I did on the slave: 1. Copied /usr/share/my-large.cnf to /etc/my.cnf 2. Added following info: master-host = 172.34.123.34 # IP of master master-user = repl master-password = repl master-port = 3306 server-id = 2 3. Untarred data directories to /var/lib/mysql 4. Verified permissions on directories/files untarred 5. Restarted slave The my.cnf file appears to be read okay, because on both machines began generating the binary log files immediately. Both machines report everything normal and happy, with no entries in the .err log files. Users can connect to each machine independently and its business as usual. There is no file 'master.info' generated on the slave (I even checked on the master too)... That's sort of strange... Does "SHOW SLAVE STATUS" on the slave say anything interesting? What if you do a "SLAVE START" on the slave? You're sure that there is literally nothing related in the *.err file on the slave? Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - 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
Re: Replication troubles
On Fri, Mar 23, 2001 at 10:45:00AM -0800, Bryan Coon wrote: I have two machines which I am trying to set up replication on. I followed the howto as describe in the manual, and everything seemed to be okay (i.e. no errors), but it simply doesn't work. Heres what I did on the master: 1. Copied /usr/share/my-large.cnf to /etc/my.cnf 2. my.cnf already had log-bin, server-id=1, so I didnt touch anything else 3. Granted file to user repl as in howto 4. Shut down master 5. Tarred data dir, copied it to slave 6. Restarted master Heres what I did on the slave: 1. Copied /usr/share/my-large.cnf to /etc/my.cnf 2. Added following info: master-host = 172.34.123.34 # IP of master master-user = repl master-password = repl master-port = 3306 server-id = 2 3. Untarred data directories to /var/lib/mysql 4. Verified permissions on directories/files untarred 5. Restarted slave The my.cnf file appears to be read okay, because on both machines began generating the binary log files immediately. Both machines report everything normal and happy, with no entries in the .err log files. Users can connect to each machine independently and its business as usual. There is no file 'master.info' generated on the slave (I even checked on the master too)... That's sort of strange... Does "SHOW SLAVE STATUS" on the slave say anything interesting? What if you do a "SLAVE START" on the slave? You're sure that there is literally nothing related in the *.err file on the slave? Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - 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
