Replication Problem: I/O Thread exits every night randomly
Hi all We have the following setup: - Master mySQL Server 4.0.11-gamma (sun-solaris2.9-sparc-64bit) - Slave mySQL Server 4.1.7 (sun-solaris2.9-sparc-64bit) Everything worked fine with both servers having the same Version (4.0.11-gamma). As a first step in updating to Rel. 4.1 we migrated the replika. Since then, we encounter the following problem: Every night replication stops. To be more precise: the I/O thread on Slave stops: mysql SHOW SLAVE STATUS\G *** 1. row *** Slave_IO_State: Master_Host: spas.mysql.prod.glue.ch Master_User: replica Master_Port: 26001 Connect_Retry: 60 Master_Log_File: appl02-bin.628 Read_Master_Log_Pos: 30621 Relay_Log_File: appl01-relay-bin.24 Relay_Log_Pos: 412019 Relay_Master_Log_File: appl02-bin.628 Slave_IO_Running: No Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 30621 Relay_Log_Space: 412019 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 18563 1 row in set (0.00 sec) The error log on replika says: 041103 3:37:50 [ERROR] While trying to obtain the list of slaves from the master 'spas.mysql.prod.glue.ch:26001', user 'replica' got the following error: 'Lost connection to MySQL server during query' 041103 3:37:50 [ERROR] Slave I/O thread exiting, read up to log 'appl02-bin.628', position 30621 Doing a mysqlbinlog on both relay log and master log do not show any problems. After a START SLAVE the slave does not recover operation completely. It looks, like the relay log file is filled, but the statements are not executed and the Seconds_Behind_Master are not decreased. Only after a complete restart of mysql (replica) the replica recovers. Any idea? Thanks for any help! Stephan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: All Tables MyISAM and still InnoDB Datafiles?
The content of the my.cnf (Master) [client] port=26001 socket=/tmp/mysql.prod.sock [mysqld] port=26001 socket=/tmp/mysql.prod.sock pid-file=/nas/prod/app/mysql/etc/prod.pid datadir=/store/prod/mysql/data log-bin server-id=1 [mysql.server] basedir=/nas/prod/app/mysql/current The my.cnf of the replika: [client] port=26000 socket=/tmp/mysql.replika.sock [mysqld] port=26000 socket=/tmp/mysql.replika.sock pid-file=/nas/prod/app/mysql/etc/replika.pid datadir=/nas/prod/store/mysql/data master-host= ... mysql server name master-user= ... mysql replika user master-password= ... mysql replika user password master-port=26001 server-id=2 I don't see any InnoDB settings...? Both, Master and Replika have the InnoDB Files in the DataDir... Thanks, Stephan Jeremy Zawodny wrote: On Thu, Mar 27, 2003 at 10:55:28AM +0100, Stephan Amann wrote: The InnoDB files are created in the standard data directory; I did not configure any InnoDB Option, since we are not currently using InnoDB. What's wrong? Why do I get InnoDB datafiles (ib_arch_log_00, ib_logfile0, ib_logfile1, ibdata1) with only MyISAM Tables? Please post your my.cnf file. There is probably a setting in there which specifies the innodb options. If you don't want to use InnoDB at all, simply add: skip-innodb to your my.cnf file. Jeremy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
All Tables MyISAM and still InnoDB Datafiles?
Hi all! I've downloaded the binary distribution mysql-standard-4.0.9-gamma-sun-solaris2.9-sparc-64bit.tar.gz from www.mysql.org. I have a couple of databases on this installation, with all tables of type MyISAM. However, on first start of mysqld the error log contains: 030226 12:39:48 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 030226 12:39:48 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 030226 12:39:49 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 030226 12:39:49 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 030226 12:39:50 InnoDB: Started /nas/prod/app/mysql/mysql-standard-4.0.11-gamma-sun-solaris2.9-sparc-64bit/bin/mysqld: ready for connections. Version: '4.0.11-gamma-standard' socket: '/tmp/mysql.prod.sock' port: 26001 030226 13:53:30 mysqld restarted The InnoDB files are created in the standard data directory; I did not configure any InnoDB Option, since we are not currently using InnoDB. What's wrong? Why do I get InnoDB datafiles (ib_arch_log_00, ib_logfile0, ib_logfile1, ibdata1) with only MyISAM Tables? Thanks for your help! Stephan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
