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