RE: What is wrong with this bloody MySQL?
Yes my GRANTAS are ok, and it has also worked before. The show table status from database_name tells me that they all are MyISAM. What to do next, how do I figure out whats wrong, and how do I solve it? Best regards Søren -Original Message- From: Thierno Cissé [mailto:[EMAIL PROTECTED] Sent: 9. oktober 2003 17:19 To: Søren Neigaard; [EMAIL PROTECTED] Subject: Re: What is wrong with this bloody MySQL? Hi, i suppose you do the necessary GRANTS on the master (before executing LOAD DATA FROM MASTER) as : - file - super - reload - select (on all tables you want to load) If not do this, and try again You can check if you are using only MyISAM tables with the client console by : show table status from database_name ; and look s in the column labelled TYPE. Regards Thierno 6C - MySQL 4.0.15 - Original Message - From: Søren Neigaard [EMAIL PROTECTED] To: 'Thierno Cissé' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 2:39 PM Subject: RE: What is wrong with this bloody MySQL? Here is my my.cnf (had to zip it, my Windoze would not let me attache it??). As far as I know, im only using MyISAM (thats the standard version right), but how do I check this? Best regards Søren -Original Message- From: Thierno Cissé [mailto:[EMAIL PROTECTED] Sent: 9. oktober 2003 16:28 To: Søren Neigaard; [EMAIL PROTECTED] Subject: Re: What is wrong with this bloody MySQL? Hi, can you indicates your configuration about : - my.cnf - all tables type your using in the master (MyISAM, INNODB, BDB) This may help to see what goes wrong . Regards Thierno 6C - MySQL 4.0.15 - Original Message - From: Søren Neigaard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 1:32 PM Subject: What is wrong with this bloody MySQL? I have posted the message with the subject Serious problem with replication, but nobody seems to know what to do? Now I have even tried to completly uninstall MySQL (with rpm -e), delete the /var/lib/mysql dir, and reinstall MySQL with rpm -i MySQL-server-4.0.15-0.i386.rpm. Then I create my database, create the tables, set up replication (as slave), and do a LOAD DATA FROM MASTER;, and still I get this bloody error: Version: '4.0.15-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 031009 15:33:48 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 031009 15:34:33 Slave I/O thread exiting, read up to log 'mysql-bin.006', position 1408472 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/otafrontenduser' with keycache 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/profile' with keycache 031009 15:34:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 Is there really nothing to do here, what the hell is the problem with MySQL? Med venlig hilsen/Best regards Søren Neigaard System Architect Mobilethink A/S Arosgaarden Åboulevarden 23, 4.sal DK - 8000 Århus C Telefon: +45 86207800 Direct: +45 86207810 Fax: +45 86207801 Email: [EMAIL PROTECTED] Web: www.mobilethink.dk -- 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] -- 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]
UPDATE - What is wrong with this bloody MySQL?
I found a bugreport that i though might have a saying here (only an idea, was not sure at all), and therefore I installed 4.1.0-alpha and started from scratch again, and then when I did a LOAD DATA FROM MASTER; I now got this (maybe this info helps you guys to help me, I sure hope so because Im really really stuck here): 031009 16:39:14 Slave I/O thread exiting, read up to log 'mysql-bin.006', position 1535724 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/otafrontenduser' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/profile' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/profiletemplatenn' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/setting' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/settingparam' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/template' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/templateparam' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:14 Note: Retrying repair of: './otamanager/wizardbookmarks' with keycache 031009 16:39:14 Key 1 - Found wrong stored record at 0 031009 16:39:15 Key 1 - Found wrong stored record at 0 031009 16:39:15 Note: Retrying repair of: './otaserver/history' with keycache 031009 16:39:15 Key 1 - Found wrong stored record at 0 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 874672 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 874972 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 875232 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 875492 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 876184 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 876460 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 880096 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 880424 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 881788 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 882096 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 883344 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 884868 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 886736 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 44 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 891188 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 891616 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 892648 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 893076 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 893684 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 894288 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 896216 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 897136 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 898144 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 898432 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 900396 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 903980 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 904380 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 904752 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 906372 031009 16:39:15 Found link that points at 8317988461515599455 (outside data file) at 906744 031009 16:39:15 Found link
What is wrong with this bloody MySQL?
I have posted the message with the subject Serious problem with replication, but nobody seems to know what to do? Now I have even tried to completly uninstall MySQL (with rpm -e), delete the /var/lib/mysql dir, and reinstall MySQL with rpm -i MySQL-server-4.0.15-0.i386.rpm. Then I create my database, create the tables, set up replication (as slave), and do a LOAD DATA FROM MASTER;, and still I get this bloody error: Version: '4.0.15-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 031009 15:33:48 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 031009 15:34:33 Slave I/O thread exiting, read up to log 'mysql-bin.006', position 1408472 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/otafrontenduser' with keycache 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/profile' with keycache 031009 15:34:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 Is there really nothing to do here, what the hell is the problem with MySQL? Med venlig hilsen/Best regards Søren Neigaard System Architect Mobilethink A/S Arosgaarden Åboulevarden 23, 4.sal DK - 8000 Århus C Telefon: +45 86207800 Direct: +45 86207810 Fax: +45 86207801 Email: [EMAIL PROTECTED] Web: www.mobilethink.dk -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What is wrong with this bloody MySQL?
Hi, can you indicates your configuration about : - my.cnf - all tables type your using in the master (MyISAM, INNODB, BDB) This may help to see what goes wrong . Regards Thierno 6C - MySQL 4.0.15 - Original Message - From: Søren Neigaard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 1:32 PM Subject: What is wrong with this bloody MySQL? I have posted the message with the subject Serious problem with replication, but nobody seems to know what to do? Now I have even tried to completly uninstall MySQL (with rpm -e), delete the /var/lib/mysql dir, and reinstall MySQL with rpm -i MySQL-server-4.0.15-0.i386.rpm. Then I create my database, create the tables, set up replication (as slave), and do a LOAD DATA FROM MASTER;, and still I get this bloody error: Version: '4.0.15-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 031009 15:33:48 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 031009 15:34:33 Slave I/O thread exiting, read up to log 'mysql-bin.006', position 1408472 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/otafrontenduser' with keycache 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/profile' with keycache 031009 15:34:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 Is there really nothing to do here, what the hell is the problem with MySQL? Med venlig hilsen/Best regards Søren Neigaard System Architect Mobilethink A/S Arosgaarden Åboulevarden 23, 4.sal DK - 8000 Århus C Telefon: +45 86207800 Direct: +45 86207810 Fax: +45 86207801 Email: [EMAIL PROTECTED] Web: www.mobilethink.dk -- 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: What is wrong with this bloody MySQL?
Here is my my.cnf (had to zip it, my Windoze would not let me attache it??). As far as I know, im only using MyISAM (thats the standard version right), but how do I check this? Best regards Søren -Original Message- From: Thierno Cissé [mailto:[EMAIL PROTECTED] Sent: 9. oktober 2003 16:28 To: Søren Neigaard; [EMAIL PROTECTED] Subject: Re: What is wrong with this bloody MySQL? Hi, can you indicates your configuration about : - my.cnf - all tables type your using in the master (MyISAM, INNODB, BDB) This may help to see what goes wrong . Regards Thierno 6C - MySQL 4.0.15 - Original Message - From: Søren Neigaard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 1:32 PM Subject: What is wrong with this bloody MySQL? I have posted the message with the subject Serious problem with replication, but nobody seems to know what to do? Now I have even tried to completly uninstall MySQL (with rpm -e), delete the /var/lib/mysql dir, and reinstall MySQL with rpm -i MySQL-server-4.0.15-0.i386.rpm. Then I create my database, create the tables, set up replication (as slave), and do a LOAD DATA FROM MASTER;, and still I get this bloody error: Version: '4.0.15-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 031009 15:33:48 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 031009 15:34:33 Slave I/O thread exiting, read up to log 'mysql-bin.006', position 1408472 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/otafrontenduser' with keycache 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/profile' with keycache 031009 15:34:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 Is there really nothing to do here, what the hell is the problem with MySQL? Med venlig hilsen/Best regards Søren Neigaard System Architect Mobilethink A/S Arosgaarden Åboulevarden 23, 4.sal DK - 8000 Århus C Telefon: +45 86207800 Direct: +45 86207810 Fax: +45 86207801 Email: [EMAIL PROTECTED] Web: www.mobilethink.dk -- 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] my.zip Description: Zip compressed data -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What is wrong with this bloody MySQL?
Hi, i suppose you do the necessary GRANTS on the master (before executing LOAD DATA FROM MASTER) as : - file - super - reload - select (on all tables you want to load) If not do this, and try again You can check if you are using only MyISAM tables with the client console by : show table status from database_name ; and look s in the column labelled TYPE. Regards Thierno 6C - MySQL 4.0.15 - Original Message - From: Søren Neigaard [EMAIL PROTECTED] To: 'Thierno Cissé' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 2:39 PM Subject: RE: What is wrong with this bloody MySQL? Here is my my.cnf (had to zip it, my Windoze would not let me attache it??). As far as I know, im only using MyISAM (thats the standard version right), but how do I check this? Best regards Søren -Original Message- From: Thierno Cissé [mailto:[EMAIL PROTECTED] Sent: 9. oktober 2003 16:28 To: Søren Neigaard; [EMAIL PROTECTED] Subject: Re: What is wrong with this bloody MySQL? Hi, can you indicates your configuration about : - my.cnf - all tables type your using in the master (MyISAM, INNODB, BDB) This may help to see what goes wrong . Regards Thierno 6C - MySQL 4.0.15 - Original Message - From: Søren Neigaard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 09, 2003 1:32 PM Subject: What is wrong with this bloody MySQL? I have posted the message with the subject Serious problem with replication, but nobody seems to know what to do? Now I have even tried to completly uninstall MySQL (with rpm -e), delete the /var/lib/mysql dir, and reinstall MySQL with rpm -i MySQL-server-4.0.15-0.i386.rpm. Then I create my database, create the tables, set up replication (as slave), and do a LOAD DATA FROM MASTER;, and still I get this bloody error: Version: '4.0.15-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 031009 15:33:48 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 031009 15:34:33 Slave I/O thread exiting, read up to log 'mysql-bin.006', position 1408472 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/otafrontenduser' with keycache 031009 15:34:33 Couldn't fix table with quick recovery: Found wrong number of deleted records 031009 15:34:33 Run recovery again without -q 031009 15:34:33 Note: Retrying repair of: './otamanager/profile' with keycache 031009 15:34:36 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'mysql-bin.006' at position 1408472 Is there really nothing to do here, what the hell is the problem with MySQL? Med venlig hilsen/Best regards Søren Neigaard System Architect Mobilethink A/S Arosgaarden Åboulevarden 23, 4.sal DK - 8000 Århus C Telefon: +45 86207800 Direct: +45 86207810 Fax: +45 86207801 Email: [EMAIL PROTECTED] Web: www.mobilethink.dk -- 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] -- 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]
