I'm unable to start KMail in Fedora-18, with the error message "The Akonadi personal information service is not operational"
Further details are: "MySQL server log contains errors. Akonadi control process not registered at D-Bus. Akonadi server process not registered at D-Bus."
I think this happened on updating kdepim last night as part of a general update after installing Fedora-18. (KMail worked find under Fedora-18 before the update.)
The error seems to lie in mysql-server, so I have downgraded this, which required downgrading mysql and mysql-libs also: -------------------------------- [tim@blanche ~]$ sudo yum downgrade mysql-server mysql-libs mysql -------------------------------- But this didn't do the trick ...
MySQL error log reads: -------------------------------- 130203 12:39:34 [Note] Plugin 'FEDERATED' is disabled. 130203 12:39:34 InnoDB: The InnoDB memory heap is disabled 130203 12:39:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130203 12:39:34 InnoDB: Compressed tables use zlib 1.2.7 130203 12:39:34 InnoDB: Using Linux native AIO 130203 12:39:34 InnoDB: Initializing buffer pool, size = 8.0M 130203 12:39:34 InnoDB: Completed initialization of buffer pool 130203 12:39:34 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 44067934793 130203 12:39:34 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: Error: tried to read 16384 bytes at offset 0 23822336. InnoDB: Was only able to read -1. 130203 12:39:38 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error- codes.html InnoDB: File operation call: 'read'. InnoDB: Cannot continue operation. --------------------------------
Any suggestions gratefully received.
Timothy Murphy wrote:
130203 12:39:34 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: Error: tried to read 16384 bytes at offset 0 23822336. InnoDB: Was only able to read -1. 130203 12:39:38 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'.
Your Akonadi MySQL database appears to be corrupt.
To fix this, you probably need to recreate the database somehow, maybe the Akonadi console can help?
Kevin Kofler
On Monday 04 of February 2013 09:13:04 Kevin Kofler wrote:
Timothy Murphy wrote:
130203 12:39:34 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: Error: tried to read 16384 bytes at offset 0 23822336. InnoDB: Was only able to read -1. 130203 12:39:38 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'.
Your Akonadi MySQL database appears to be corrupt.
To fix this, you probably need to recreate the database somehow, maybe the Akonadi console can help?
The backend database cannot be recovered from Akonadi Console. You can try using some MySQL-InnoDb recovery tools. If that does not work, the only way is to remove your Akonadi database (~/.local/share/akonadi) and it will be recreated on start up.
Cheers, Dan
Kevin Kofler
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org