copied the above commands to test.sh: $ sh test.sh insgesamt 0 srwxrwxrwx 1 user mygroup 0 2010-12-10 18:23 mysql.socket insgesamt 24 -rw-r--r-- 1 user mygroup 2736 2010-12-10 18:25 akonadiserver.error -rw-r--r-- 1 user mygroup 1114 2010-12-10 18:23 akonadiserver.error.old srwxr-xr-x 1 user mygroup 0 2010-12-10 18:23 akonadiserver.socket drwxr-xr-x 4 user mygroup 4096 2010-12-10 18:23 db_data drwxr-xr-x 2 user mygroup 4096 2010-12-10 18:23 db_misc drwxr-xr-x 2 user mygroup 4096 2010-05-08 21:57 file_db_data -rw-r--r-- 1 user mygroup 2033 2010-05-08 21:57 mysql.conf user 3276 3272 0 18:25 pts/1 00:00:00 grep mysql akonadi-server: Installiert: 1.3.1-0ubuntu3 Kandidat: 1.3.1-0ubuntu3 Versions-Tabelle: *** 1.3.1-0ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status -rwxr-xr-x 1 root root 469 2010-04-13 19:54 /etc/apparmor.d/usr.sbin.mysqld-akonadi insgesamt 143640 drwx------ 2 user mygroup 4096 2010-05-08 21:58 akonadi -rw-rw---- 1 user mygroup 5 2010-12-10 18:23 alpha.pid -rw-rw---- 1 user mygroup 5 2010-12-08 18:00 gamma.pid -rw-rw---- 1 user mygroup 10485760 2010-12-10 18:23 ibdata1 -rw-rw---- 1 user mygroup 67108864 2010-12-10 18:23 ib_logfile0 -rw-rw---- 1 user mygroup 67108864 2010-12-10 18:23 ib_logfile1 drwx------ 2 user mygroup 4096 2010-08-04 18:16 mysql -rw-rw---- 1 user mygroup 106 2010-12-08 06:20 mysql-bin.000488 -rw-rw---- 1 user mygroup 106 2010-12-08 06:20 mysql-bin.000489 -rw-rw---- 1 user mygroup 380 2010-12-08 06:20 mysql-bin.000490 -rw-rw---- 1 user mygroup 380 2010-12-08 06:39 mysql-bin.000491 -rw-rw---- 1 user mygroup 106 2010-12-08 09:45 mysql-bin.000492 -rw-rw---- 1 user mygroup 380 2010-12-08 09:46 mysql-bin.000493 -rw-rw---- 1 user mygroup 380 2010-12-08 18:00 mysql-bin.000494 -rw-rw---- 1 user mygroup 106 2010-12-09 05:46 mysql-bin.000495 -rw-rw---- 1 user mygroup 380 2010-12-09 05:47 mysql-bin.000496 -rw-rw---- 1 user mygroup 380 2010-12-09 17:59 mysql-bin.000497 -rw-rw---- 1 user mygroup 106 2010-12-10 05:59 mysql-bin.000498 -rw-rw---- 1 user mygroup 106 2010-12-10 05:59 mysql-bin.000499 -rw-rw---- 1 user mygroup 380 2010-12-10 06:00 mysql-bin.000500 -rw-rw---- 1 user mygroup 106 2010-12-10 18:23 mysql-bin.000501 -rw-rw---- 1 user mygroup 380 2010-12-10 18:23 mysql-bin.000502 -rw-rw---- 1 user mygroup 285 2010-12-10 18:23 mysql-bin.index -rw-rw---- 1 user mygroup 22453 2010-12-10 18:23 mysql.err -rw-r--r-- 1 user mygroup 2111134 2010-12-10 18:23 mysql.err.old -rw-r--r-- 1 user mygroup 6 2010-08-04 18:16 mysql_upgrade_info 101210 18:20:32 [Note] Plugin 'FEDERATED' is disabled. InnoDB: Log scan progressed past the checkpoint lsn 0 121898992 101210 18:20:33 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... InnoDB: Doing recovery: scanned up to log sequence number 0 121908902 101210 18:20:34 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 101210 18:20:34 InnoDB: Error: page 1 log sequence number 0 122811147 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 16 101210 18:20:34 InnoDB: Error: page 1 log sequence number 0 122695833 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 987, file name ./mysql-bin.000405 101210 18:20:35 InnoDB: Error: page 50 log sequence number 0 123476936 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:35 InnoDB: Error: page 58 log sequence number 0 121947213 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:35 InnoDB: Error: page 59 log sequence number 0 121947612 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:35 InnoDB: Error: page 60 log sequence number 0 122815544 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:35 InnoDB: Error: page 61 log sequence number 0 122978608 InnoDB: is in the future! Current system log sequence number 0 121908902. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:35 InnoDB: Started; log sequence number 0 121908902 101210 18:20:35 [Note] Recovering after a crash using mysql-bin 101210 18:20:35 [Note] Starting crash recovery... 101210 18:20:35 [Note] Crash recovery finished. 101210 18:20:35 [Note] /usr/sbin/mysqld-akonadi: ready for connections. Version: '5.1.41-3ubuntu11-log' socket: '/home/user/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Ubuntu) 101210 18:20:36 InnoDB: Error: page 3 log sequence number 0 122618532 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 4 log sequence number 0 122618497 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 3 log sequence number 0 122920267 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 2 log sequence number 0 122920267 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 24 log sequence number 0 123205374 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 15 log sequence number 0 123497525 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 23 log sequence number 0 123123388 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 14 log sequence number 0 123450806 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 27 log sequence number 0 123368727 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 4 log sequence number 0 122695833 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 13 log sequence number 0 122695833 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 10 log sequence number 0 122616496 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 26 log sequence number 0 122978590 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:36 InnoDB: Error: page 25 log sequence number 0 123286621 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 3 log sequence number 0 122952976 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 2 log sequence number 0 122952976 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 89 log sequence number 0 122626442 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 93 log sequence number 0 122734895 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 31 log sequence number 0 122617907 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 97 log sequence number 0 122844347 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 82 log sequence number 0 122056187 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 4 log sequence number 0 122811147 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 49 log sequence number 0 122811147 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 43 log sequence number 0 122604368 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 103 log sequence number 0 122978921 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 94 log sequence number 0 122762098 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 3 log sequence number 0 122618482 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 4 log sequence number 0 122618461 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:37 InnoDB: Error: page 33 log sequence number 0 122617907 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 81 log sequence number 0 122028627 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 83 log sequence number 0 122083912 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 84 log sequence number 0 122111213 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 85 log sequence number 0 122138994 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 86 log sequence number 0 122165801 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 87 log sequence number 0 122193380 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 88 log sequence number 0 122249883 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 90 log sequence number 0 122653049 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 91 log sequence number 0 122680125 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 92 log sequence number 0 122707598 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 95 log sequence number 0 122789199 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 96 log sequence number 0 122816582 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 98 log sequence number 0 122871086 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 99 log sequence number 0 122898118 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 100 log sequence number 0 122925809 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 101 log sequence number 0 122952976 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:38 InnoDB: Error: page 102 log sequence number 0 122952976 InnoDB: is in the future! Current system log sequence number 0 121908912. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 101210 18:20:45 - 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=8384512 read_buffer_size=131072 max_used_connections=4 max_threads=256 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566870 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = (nil) thread_stack 0x30000 /usr/sbin/mysqld-akonadi(my_print_stacktrace+0x2d) [0xa6e30d] /usr/sbin/mysqld-akonadi(handle_segfault+0x494) [0x73a3d4] [0x12d400] /usr/sbin/mysqld-akonadi(row_purge_step+0x3c8) [0x9ac398] /usr/sbin/mysqld-akonadi(que_run_threads+0x5b0) [0x9978b0] /usr/sbin/mysqld-akonadi(trx_purge+0x375) [0x9c9e65] /usr/sbin/mysqld-akonadi(srv_master_thread+0xdfc) [0x9c08cc] /lib/tls/i686/cmov/libpthread.so.0(+0x596e) [0x3ef96e] /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xe4da4e] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. $ -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in ubuntu. https://bugs.launchpad.net/bugs/676173 Title: kaddressbook fails to show addressbooks contents -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs