[15 Mar 2007 13:14] Kristian Koehntopp Description: In the error log of a customers server I get070315 13:43:01 mysqld started 070315 13:43:01 InnoDB: Started; log sequence number 0 24665690 070315 13:43:01 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.36-enterprise-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Enterprise Server (Commercial) 070315 14:03:32 [Warning] Warning: Enabling keys got errno 137, retryingand perror 137 reportsnvag-blade0106:/var/lib/mysql # perror 137 MySQL error code 137: No more records (read after end of file)So a table has a problem, but the message does not indicate which table and database schema are affected.How to repeat: I have no idea how to provoke that message artificially.Suggested fix: Check that this (and all other table related messages) include schema name and table name, when index related also the index name and number.
Description:
In the error log of a customers server I get070315 13:43:01 mysqld started
070315 13:43:01 InnoDB: Started; log sequence number 0 24665690
070315 13:43:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.36-enterprise-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL
Enterprise Server (Commercial)
070315 14:03:32 [Warning] Warning: Enabling keys got errno 137, retryingand perror 137 reportsnvag-blade0106:/var/lib/mysql # perror 137
MySQL error code 137: No more records (read after end of file)So a table has a problem, but the message does not indicate which table and database
schema are affected.How to repeat:
I have no idea how to provoke that message artificially.Suggested fix:
Check that this (and all other table related messages) include schema name and table
name, when index related also the index name and number.