Hi, last night I've upgraded on a Debian Etch Server the MySQL-Server from 4.1 to 5.0.22. After this the MySQL-Server started to crash regulary. The installed architecture is AMD64.
In the MySQL-Error-Log I find this: --- 060603 10:25:40 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... 060603 10:25:40 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 210480. InnoDB: Doing recovery: scanned up to log sequence number 0 210480 060603 10:25:40 InnoDB: Started; log sequence number 0 210480 060603 10:25:40 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.22-Debian_1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=134217728 read_buffer_size=1044480 max_used_connections=1 max_connections=500 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1665068 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. --- Then I downgraded the MySQL-Server from 5.0.22 to 5.0.20 and the Server seems now running fine. What bug or problem this could be? Thanks. -- Best regards, Thomas Babut <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
