<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">Am 17.11.2014 23:34, schrieb Ingo
Klöcker:<br>
</div>
<blockquote cite="mid:2357653.ZrXMIMknVK@collossus.ingo-kloecker.de"
type="cite">
<pre wrap="">On Monday 17 November 2014 15:21:23 dirk wrote:
</pre>
<blockquote type="cite">
<pre wrap="">What to do to make akonadi run again?
And how to get access to my old mails, notes, dates etc.?
By startin akonadi in an text console I get the following error messages:
</pre>
</blockquote>
<pre wrap="">[snip]
</pre>
<blockquote type="cite">
<pre wrap="">Invalid database object during database server startup
</pre>
</blockquote>
<pre wrap="">[snip]
</pre>
<blockquote type="cite">
<pre wrap="">ProcessControl: Application 'akonadiserver' returned with exit code 255
(Unknown error)
"akonadiserver" crashed too often and will not be restarted!
</pre>
</blockquote>
<pre wrap="">
It seems that Akonadi's database is corrupt. I had the same problem (Invalid
database object during database server startup) last Friday. Restarting
Akonadi didn't help. So, I tried to reboot the computer. But the computer
didn't boot anymore. The boot loader panicked because it couldn't unpack the
kernel (corrupt zip file). I fear that my SSD is dying. :-(
Therefore I suggest that you make a full backup of your hard disk/SSD before
you do anything else. Afterward check the file
~/.local/share/akonadi/db_data/mysql.err
It might contain details concerning the database problem.
Renaming ~/.local/share/akonadi should have made Akonadi recreate its
database. Maybe it didn't work because the database process was still running.
Or maybe it didn't work because the new database was also corrupted (e.g.
because of a failing hard disk/SSD).
Regards,
Ingo
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
KDE PIM users mailing list
Subscription management:
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/kdepim-users">https://mail.kde.org/mailman/listinfo/kdepim-users</a>
</blockquote>
<br>
<br>
Hi Ingo,<br>
<br>
in mysql.err there are errors mentioned as listet below. But the
entries doesn't help me:<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:dirk@azid:~/.local/share/akonadi/db_data">dirk@azid:~/.local/share/akonadi/db_data</a>> less mysql.err<br>
<br>
141118 9:06:17 InnoDB: The InnoDB memory heap is disabled<br>
141118 9:06:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins<br>
141118 9:06:17 InnoDB: Compressed tables use zlib 1.2.7<br>
141118 9:06:17 InnoDB: Using Linux native AIO<br>
141118 9:06:17 InnoDB: Initializing buffer pool, size = 80.0M<br>
141118 9:06:17 InnoDB: Completed initialization of buffer pool<br>
InnoDB: Unable to lock ./ibdata1, error: 11<br>
InnoDB: Check that you do not already have another mysqld process<br>
InnoDB: using the same InnoDB data or log files.<br>
<br>
snip<br>
...<br>
snip<br>
<br>
InnoDB: Unable to lock ./ibdata1, error: 11<br>
InnoDB: Check that you do not already have another mysqld process<br>
InnoDB: using the same InnoDB data or log files.<br>
141118 9:07:57 InnoDB: Unable to open the first data file<br>
InnoDB: Error in opening ./ibdata1<br>
141118 9:07:57 InnoDB: Operating system error number 11 in a file
operation.<br>
InnoDB: Error number 11 means 'Resource temporarily unavailable'.<br>
InnoDB: Some operating system error numbers are described at<br>
InnoDB:
<a class="moz-txt-link-freetext" href="http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html">http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html</a><br>
141118 9:07:57 InnoDB: Could not open or create data files.<br>
141118 9:07:57 InnoDB: If you tried to add new data files, and it
failed here,<br>
141118 9:07:57 InnoDB: you should now edit innodb_data_file_path in
my.cnf back<br>
141118 9:07:57 InnoDB: to what it was, and remove the new ibdata
files InnoDB created<br>
141118 9:07:57 InnoDB: in this failed attempt. InnoDB only wrote
those files full of<br>
141118 9:07:57 InnoDB: zeros, but did not yet use them in any way.
But be careful: do not<br>
141118 9:07:57 InnoDB: remove old data files which contain your
precious data!<br>
141118 9:07:57 [ERROR] Plugin 'InnoDB' init function returned
error.<br>
141118 9:07:57 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.<br>
141118 9:07:57 [ERROR] Unknown/unsupported storage engine: innodb<br>
141118 9:07:57 [ERROR] Aborting<br>
<br>
141118 9:07:57 [Note] /usr/sbin/mysqld: Shutdown complete<br>
<br>
--<br>
Dirk<br>
<br>
<br>
<br>
</body>
</html>