seems like there is a problem of consistency of innodb data and recovery does not go well. try to take a look at innodb status:
>show engine innodb status http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html http://dev.mysql.com/doc/refman/5.0/en/innodb-monitors.html Cheers Claudio 2009/4/17 Mihail Vetchinov <m.vetchi...@rambler-co.ru> > Anybody can tell me about way which will force the mysqld write more > information into logs (.err file)? > > My mysqld restarted every 20-30 minutes without reasonable info in log file > and I dont understand why it occurs. > > I see only string "mysqld restarted" and nothing more! :( > > Example of log: > > 090417 16:34:14 InnoDB: Started; log sequence number 0 73771 > 090417 16:34:14 [Note] /usr/local/libexec/mysqld: ready for connections. > Version: '5.0.77-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: > mysql-server-5.0.77_1 > 090417 16:34:14 [Note] Slave SQL thread initialized, starting replication > in log 'mysql-bin.000576' at position 530085643, relay log > './beta23-relay-bin.000174' position: 93504 > 090417 16:34:14 [Note] Slave I/O thread: connected to master ' > bet...@beta27.rambler.ru:3306', replication started in log > 'mysql-bin.000576' at position 530085643 > 090417 16:39:38 mysqld restarted > InnoDB: The log sequence number in ibdata files does not match > InnoDB: the log sequence number in the ib_logfiles! > 090417 16:39:39 InnoDB: Database was not shut down normally! > InnoDB: Starting crash recovery. > InnoDB: Reading tablespace information from the .ibd files... > InnoDB: Restoring possible half-written data pages from the doublewrite > InnoDB: buffer... > 090417 16:39:39 InnoDB: Started; log sequence number 0 73781 > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com > >
