Mageia forum

Website · by **macxi** » Jul 10th, '11, 22:42

Hi,

I can't access my emails in KMAIL (v. 1.13.7) because it says that "Akonadi not available".

Yesterday (09/july/2011) I installed updates on a Mageia:

Yesterday was OK, today KMAIL doesn't work.

When I open Kmail warning appears:

"The service management of personal information of Akonadi is not available"

I can download the emails, but not access them.

The Kadressbook depends Akonadi and gives the same error:

When I access the error details Akonadi, this window appears:

I took a look at the KDE / Akonadi, and found this page: http://userbase.kde.org/Akonadi it says in the introduction:

Introduction - In KDE Software Compilation 4.4 KAddressBook became the first application to use Akonadi. There are inevitable glitches in early stages of migration, and the Troubleshooting page will help solve them. For a brief description of the purpose of Akonadi, see this Glossary entry. You will also find useful links to further reading. Once the inevitable teething troubles are over Akonadi will provide a power-house usable by many applications.

I have no idea what's going to give these errors. It is possible that the updates of the packages have caused this error?

Does anyone have any tips?
________________________

Note 1: I tried to run kmail in "text mode" (kmail -caption "%c") and in the end, gave the following warning:

ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted!

Note 2: I created a new user and Kmail open ok.

Note 3: Today was another accident that has no connection with this (but it can have). Today, turning on the computer and access the Mageia, I saw that Firefox had lost all custom configuration.

Note 4: Mysqlsever gives error: The file of log '/home/user/.local/share/akonadi/db_data/mysql.err' of MySQL server has erros:

Code: Select all: 110710 19:30:42 InnoDB: The InnoDB memory heap is disabled 110710 19:30:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins 110710 19:30:42 InnoDB: Compressed tables use zlib 1.2.5 110710 19:30:42 InnoDB: Using Linux native AIO 110710 19:30:42 InnoDB: Initializing buffer pool, size = 80.0M 110710 19:30:42 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. 110710 19:30:42 InnoDB: Retrying to lock the first data file 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 110710 19:32:22 InnoDB: Unable to open the first data file InnoDB: Error in opening ./ibdata1 110710 19:32:22 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 110710 19:32:22 InnoDB: Could not open or create data files. 110710 19:32:22 InnoDB: If you tried to add new data files, and it failed here, 110710 19:32:22 InnoDB: you should now edit innodb_data_file_path in my.cnf back 110710 19:32:22 InnoDB: to what it was, and remove the new ibdata files InnoDB created 110710 19:32:22 InnoDB: in this failed attempt. InnoDB only wrote those files full of 110710 19:32:22 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 110710 19:32:22 InnoDB: remove old data files which contain your precious data! 110710 19:32:22 [ERROR] Plugin 'InnoDB' init function returned error. 110710 19:32:22 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 110710 19:32:22 [ERROR] Unknown/unsupported storage engine: innodb 110710 19:32:22 [ERROR] Aborting 110710 19:32:22 [Note] /usr/sbin/mysqld: Shutdown complete

Note 5:
--> I tested the Akonadi and mysql in another user of Mageia 1 and is working perfectly. I Just don't know why mysql isn't running and not allowing the run Akonodi.

--> I have another partition with a Mageia 1 installed. I updated this other Mageia 1 and didn't give the same error with the Akonadi.

Therefore, the error isn't derived from the update yesterday, because Akonodi is running on other users and another installation of Mageia 1.

So, why did the mysql stopped to run?

Website · by **macxi** » Jul 11th, '11, 14:41

I'm looking for a similar errors on the internet and trying to understand a bit:

InnoDB: Unable to lock ./ibdata1, err.: https://bugs.kde.org/225333.

akonadi and dbus.. problems: http://forum.kde.org/viewtopic.php?f=20&t=37989.

I suspicious that the problem is the "style Gtk+" that was installed (I've had trouble with the "style Gtk+" to install the Qutecom - perhaps there is some incompatibility with some new update). Now, I set the default style, which seems to be the "IaOra-Kde".

If I don't find solution, I will change my folders to a new user who is already created and where Kmail is working ok.

Note: I'm using Kmail 1.13.7, with KDE 4.6.3.

by **mikala** » Jul 12th, '11, 03:05

For some reason innodb seems to failed on your account.
Could you tell us how you did install mageia ? using the dvd or a live-cd ?

Website · by **macxi** » Jul 12th, '11, 04:55

mikala wrote:For some reason innodb seems to failed on your account.
Could you tell us how you did install mageia ? using the dvd or a live-cd ?

Mikala,

I installed "Mageia 1" with LiveCD KDE and I'm using default repository.
Now, I created a new user in same instalation "Mageia 1" and Akonadi works ok, and Kmail too.
But akonadi doesn't work in old user.

I'm trying to understand what happened. I found a page about KDE-PIM/Akonadi and in wikipedia Kde-PIM.

Website · by **macxi** » Jul 16th, '11, 21:17

Hi,

I did Akonadi to work again and I returned to have access to Kmail

I changed the folder name "akonadi" to "akonadi-old" (in "/ home/user-1/.local/share/akonadi /") and closed the session and restart again at that same user.

When restarting, Mageia/Kde created a new folder "akonadi" (in "/ home/user-1/.local/share/akonadi /"). Akonadi returned to work and had access to Kmail.

However, a new problem appeared. Akonadi is processing something (probably indexing the mail again) and is taking 99% CPU, becoming slow. And the "exception handler" KDE registers of two bugs:

Details:
Executable: akonadi_maildispatcher_agent PID: 3289 Sinal: Aborted (6)

Details:
Executable: akonadi_nepomuk_contact_feeder PID: 3290 Sinal: Aborted (6)

However, if Akonadi/mysql and Kmail are run, I think it is very good.

Note: As I created another user to access my emails, I'm using this user just for testing now.

Website · by **macxi** » Jul 23rd, '11, 15:34

Hi,
Yesterday, a the partition (ext4) of where occurred the error reported in this topic, has reported other error: "file system with error, forced checked", "Duplicad or bad block in use".
I corrected the error with fsck.
fsck -n -v /dev/sda? (n = no-repair) (to check) (vivaolinux)
sudo -r -v /dev/sda? (r = recursive, v = verbose) (to correct)
I just comment it because this may have been what caused the error in the operation Akonadi and mysql.

by **mikala** » Jul 23rd, '11, 15:52

hum maybe indeed.

Website · by **macxi** » Jul 23rd, '11, 16:29

mikala wrote:hum maybe indeed.

Mikala,

My doubt is what might have caused it.

One possibility is that the Mageia crashed a few times when I watched video on youtube (and I had restart the computer in force), this may have caused the inconsistency.

by **jtmh** » Jul 23rd, '12, 07:45

macxi wrote:Hi,

I did Akonadi to work again and I returned to have access to Kmail

I changed the folder name "akonadi" to "akonadi-old" (in "/ home/user-1/.local/share/akonadi /") and closed the session and restart again at that same user.

When restarting, Mageia/Kde created a new folder "akonadi" (in "/ home/user-1/.local/share/akonadi /"). Akonadi returned to work and had access to Kmail.

However, a new problem appeared. Akonadi is processing something (probably indexing the mail again) and is taking 99% CPU, becoming slow. And the "exception handler" KDE registers of two bugs:

Details:
Executable: akonadi_maildispatcher_agent PID: 3289 Sinal: Aborted (6)

Details:
Executable: akonadi_nepomuk_contact_feeder PID: 3290 Sinal: Aborted (6)

However, if Akonadi/mysql and Kmail are run, I think it is very good.

Note: As I created another user to access my emails, I'm using this user just for testing now.

I encountered the same problem on Mageia 2, and everytime I logged out, there was a dialog saying some unknown error from kmail. Luckily, I found this solution and my problem was solved. Thanks.

Mageia forum

[SOLVED] Kmail doesn't run - says: "Akonadi not available"?!

[SOLVED] Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run - says: "Akonadi not available"?!

Re: Kmail doesn't run-says:"Akonadi not available"! (SOLVED)

Re: Kmail doesn't run - says: "Akonadi not available"?!

Who is online