Hi, today my MySQL 5.0.32 server crashed on my Debian Etch system. This never happened before so I'm not sure where to look for the reason. It seemed that MySQL started automatically after the crash but the other servers (postfix, courier) were not able to connect to it until I restarted MySQL manually.
I read the logfiles but I can not find anything leading me to the reason: Nov 22 15:32:15 localhost mysqld_safe[12714]: Number of processes running now: 0 Nov 22 15:32:15 localhost mysqld_safe[12716]: restarted Nov 22 15:32:15 localhost mysqld[12720]: 071122 15:32:15 InnoDB: Database was not shut down normally! Nov 22 15:32:15 localhost mysqld[12720]: InnoDB: Starting crash recovery. Nov 22 15:32:15 localhost mysqld[12720]: InnoDB: Reading tablespace information from the .ibd files... Nov 22 15:32:15 localhost mysqld[12720]: InnoDB: Restoring possible half-written data pages from the doublewrite Nov 22 15:32:15 localhost mysqld[12720]: InnoDB: buffer... Nov 22 15:32:16 localhost mysqld[12720]: 071122 15:32:16 InnoDB: Starting log scan based on checkpoint at Nov 22 15:32:16 localhost mysqld[12720]: InnoDB: log sequence number 0 44670615. Nov 22 15:32:16 localhost mysqld[12720]: InnoDB: Doing recovery: scanned up to log sequence number 0 44670615 Nov 22 15:32:16 localhost mysqld[12720]: InnoDB: Last MySQL binlog file position 0 1991372, file name /var/log/mysql/mysql-bin.000580 Nov 22 15:32:16 localhost mysqld[12720]: 071122 15:32:16 InnoDB: Started; log sequence number 0 44670615 Nov 22 15:32:16 localhost mysqld[12720]: 071122 15:32:16 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Nov 22 15:32:16 localhost mysqld[12720]: 071122 15:32:16 [Note] Starting crash recovery... Nov 22 15:32:16 localhost mysqld[12720]: 071122 15:32:16 [Note] Crash recovery finished. Nov 22 15:32:16 localhost mysqld[12720]: 071122 15:32:16 [Note] /usr/sbin/mysqld: ready for connections. Nov 22 15:32:16 localhost mysqld[12720]: Version: '5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution Is there a way to find out why MySQL crashed? Regards, Frank -- View this message in context: http://www.nabble.com/MySQL-crash-on-Debian-Etch-system-tf4857583.html#a13900443 Sent from the MySQL - General mailing list archive at Nabble.com. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
