1 |
First some general observations that relate to kmail2: |
2 |
|
3 |
I thought of giving the latest kmail-4.12.5 a spin. So installed it on a |
4 |
machine and set up a couple of IMAP4 servers to get messages from. An account |
5 |
with a messages in the low hundreds works fine. An account with messages in |
6 |
the 100k plus range works like a dog. While kmail fetches headers and then |
7 |
akonadi sets off to organise threads and whatever else it wants to do the |
8 |
application becomes pretty much unresponsive and the CPU climbs up to 98%. |
9 |
Half an hour later I can get back to it. :-@ |
10 |
|
11 |
Anyway, this is not the current problem. I updated mysql to 5.5.39, then I |
12 |
kmail would not start with akonadi failing with "mysql log containing errors". |
13 |
So I ran: |
14 |
|
15 |
mysql_upgrade --socket=/tmp/akonadi-michael.NFvLpB/mysql.socket |
16 |
|
17 |
which completed without an error. Kmail still failed to start. Trying to |
18 |
start akonadi console states: |
19 |
|
20 |
"Failed to connect to database. Driver not loaded" |
21 |
|
22 |
Then the pop up Details window says MySQL log contains errors, just like when |
23 |
I try to start kmail. This is what I see in |
24 |
.local/share/akonadi/db_data/mysql.err: |
25 |
|
26 |
InnoDB: Unable to lock ./ibdata1, error: 11 |
27 |
InnoDB: Check that you do not already have another mysqld process |
28 |
InnoDB: using the same InnoDB data or log files. |
29 |
InnoDB: Unable to lock ./ibdata1, error: 11 |
30 |
InnoDB: Check that you do not already have another mysqld process |
31 |
InnoDB: using the same InnoDB data or log files. |
32 |
140809 20:58:42 InnoDB: Unable to open the first data file |
33 |
InnoDB: Error in opening ./ibdata1 |
34 |
140809 20:58:42 InnoDB: Operating system error number 11 in a file operation. |
35 |
InnoDB: Error number 11 means 'Resource temporarily unavailable'. |
36 |
InnoDB: Some operating system error numbers are described at |
37 |
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html |
38 |
140809 20:58:42 InnoDB: Could not open or create data files. |
39 |
140809 20:58:42 InnoDB: If you tried to add new data files, and it failed |
40 |
here, |
41 |
140809 20:58:42 InnoDB: you should now edit innodb_data_file_path in my.cnf |
42 |
back |
43 |
140809 20:58:42 InnoDB: to what it was, and remove the new ibdata files InnoDB |
44 |
created |
45 |
140809 20:58:42 InnoDB: in this failed attempt. InnoDB only wrote those files |
46 |
full of |
47 |
140809 20:58:42 InnoDB: zeros, but did not yet use them in any way. But be |
48 |
careful: do not |
49 |
140809 20:58:42 InnoDB: remove old data files which contain your precious |
50 |
data! |
51 |
140809 20:58:42 [ERROR] Plugin 'InnoDB' init function returned error. |
52 |
140809 20:58:42 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE |
53 |
failed. |
54 |
140809 20:58:42 [ERROR] Unknown/unsupported storage engine: innodb |
55 |
140809 20:58:42 [ERROR] Aborting |
56 |
|
57 |
|
58 |
So I moved ./ibdata* and tried again with the same error. Is there something |
59 |
else I should be doing here to get this going? |
60 |
|
61 |
-- |
62 |
Regards, |
63 |
Mick |