Re: akonadi error - fails to start

Am 17.11.2014 23:34, schrieb Ingo Klöcker:
> On Monday 17 November 2014 15:21:23 dirk wrote:
>> 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:
> [snip]
>> Invalid database object during database server startup
> [snip]
>> ProcessControl: Application 'akonadiserver' returned with exit code 255
>> (Unknown error)
>> "akonadiserver" crashed too often and will not be restarted!
> 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
>
> _______________________________________________ KDE PIM users mailing 
> list Subscription management: 
> https://mail.kde.org/mailman/listinfo/kdepim-users 


Hi Ingo,

in mysql.err there are errors mentioned as listet below. But the entries 
doesn't help me:

dirk@azid:~/.local/share/akonadi/db_data> less mysql.err

141118  9:06:17 InnoDB: The InnoDB memory heap is disabled
141118  9:06:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141118  9:06:17 InnoDB: Compressed tables use zlib 1.2.7
141118  9:06:17 InnoDB: Using Linux native AIO
141118  9:06:17 InnoDB: Initializing buffer pool, size = 80.0M
141118  9:06:17 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.

snip
...
snip

InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
141118  9:07:57  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
141118  9:07:57  InnoDB: Operating system error number 11 in a file 
operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: 
http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
141118  9:07:57 InnoDB: Could not open or create data files.
141118  9:07:57 InnoDB: If you tried to add new data files, and it 
failed here,
141118  9:07:57 InnoDB: you should now edit innodb_data_file_path in 
my.cnf back
141118  9:07:57 InnoDB: to what it was, and remove the new ibdata files 
InnoDB created
141118  9:07:57 InnoDB: in this failed attempt. InnoDB only wrote those 
files full of
141118  9:07:57 InnoDB: zeros, but did not yet use them in any way. But 
be careful: do not
141118  9:07:57 InnoDB: remove old data files which contain your 
precious data!
141118  9:07:57 [ERROR] Plugin 'InnoDB' init function returned error.
141118  9:07:57 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE 
failed.
141118  9:07:57 [ERROR] Unknown/unsupported storage engine: innodb
141118  9:07:57 [ERROR] Aborting

141118  9:07:57 [Note] /usr/sbin/mysqld: Shutdown complete

--
Dirk

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users