Here is what is in the error log: looks awful.... How do I determine if slave is running correctly. I though show Slave status \G did this...
041026 0:19:44 Slave I/O thread killed while reading event 041026 0:19:44 Slave I/O thread exiting, read up to log 'www-bin.001', position 5685 041026 0:19:44 Error reading relay log event: slave SQL thread was killed 041026 0:20:09 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:09 Run recovery again without -q 041026 0:20:09 Note: Retrying repair of: './dotproject/user_tasks' with keycache 041026 0:20:09 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:09 Run recovery again without -q 041026 0:20:09 Note: Retrying repair of: './openreports/REPORT' with keycache 041026 0:20:09 Delete link points outside datafile at 180 041026 0:20:09 Note: Retrying repair of: './openreports/REPORT_CHART' with keycache 041026 0:20:09 Delete link points outside datafile at 180 041026 0:20:10 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:10 Run recovery again without -q 041026 0:20:10 Note: Retrying repair of: './psa/ClientsTraffic' with keycache 041026 0:20:10 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:10 Run recovery again without -q 041026 0:20:10 Note: Retrying repair of: './psa/DomainsTraffic' with keycache 041026 0:20:10 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:10 Run recovery again without -q 041026 0:20:10 Note: Retrying repair of: './psa/IP_Addresses' with keycache 041026 0:20:11 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:11 Run recovery again without -q 041026 0:20:11 Note: Retrying repair of: './psa/data_bases' with keycache 041026 0:20:11 Delete link points outside datafile at 136 041026 0:20:11 Note: Retrying repair of: './psa/domains' with keycache 041026 0:20:11 Delete link points outside datafile at 136 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Note: Retrying repair of: './psa/lockout' with keycache 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Note: Retrying repair of: './psa/log_actions' with keycache 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Delete link points outside datafile at 4700 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Note: Retrying repair of: './psa/log_components' with keycache 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Delete link points outside datafile at 4112 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Note: Retrying repair of: './psa/mail_redir' with keycache 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:11 Note: Retrying repair of: './psa/sessions' with keycache 041026 0:20:11 Delete link points outside datafile at 0 041026 0:20:12 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:12 Run recovery again without -q 041026 0:20:12 Note: Retrying repair of: './psa/smtp_poplocks' with keycache 041026 0:20:12 Delete link points outside datafile at 480 041026 0:20:12 Note: Retrying repair of: './psa/sys_users' with keycache 041026 0:20:12 Delete link points outside datafile at 480 041026 0:20:12 Couldn't fix table with quick recovery: Found wrong number of deleted records 041026 0:20:12 Run recovery again without -q 041026 0:20:12 Note: Retrying repair of: './psa/web_users' with keycache 041026 0:20:13 Delete link points outside datafile at 0 041026 0:20:13 Note: Retrying repair of: './winklink/msg_sent' with keycache 041026 0:20:13 Delete link points outside datafile at 0 041026 0:20:20 Slave SQL thread initialized, starting replication in log 'www-bin.001' at position 4, relay log './www-relay-bin.000001' position: 4 041026 0:20:20 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'www-bin.001' at position 4 [EMAIL PROTECTED] mysql5]# -----Original Message----- From: Egor Egorov [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 12:21 PM To: [EMAIL PROTECTED] Subject: Re: Replication Issue "Randy Johnson" <[EMAIL PROTECTED]> wrote: > I have mysql master and mysql slave on same machine running > separately. > I have master and slave setup. > I was able to do the LOAD DATA FROM MASTER; > > to get the data but the data does not replicate after that. =20 > > Looking at the info below can you tell why replication is not taking = > place. > Can I provide you with any other information? Look in the tail of .err file, which may contain some clue info. Are you sure that replication slave is running? See http://dev.mysql.com/doc/mysql/en/Replication.html, most issues are covered there. -- -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- 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]
