1 |
Paul Stear posted on Wed, 22 Sep 2010 11:12:53 +0100 as excerpted: |
2 |
|
3 |
> Hi all, |
4 |
> I have updated kde to 4.5.1 and now have runtime errors. The following |
5 |
> is the self test report:- |
6 |
|
7 |
> Test 5: ERROR |
8 |
> -------- |
9 |
> |
10 |
> MySQL server log contains errors. |
11 |
> Details: The MySQL server error log file '<a |
12 |
> href='/home/paul/.local/share/akonadi/db_data/mysql.err'>/home/ |
13 |
paul/.local/share/akonadi/db_data/mysql.err</a>' |
14 |
> contains errors. |
15 |
> |
16 |
> File content of '/home/paul/.local/share/akonadi/db_data/mysql.err': |
17 |
> InnoDB: The InnoDB memory heap is disabled InnoDB: use atomic builtins. |
18 |
> InnoDB: Error: log file ./ib_logfile1 is of different size 0 0 bytes |
19 |
> InnoDB: than specified in the .cnf file 0 67108864 bytes! 100922 |
20 |
> 10:43:05 [ERROR] Default storage engine (InnoDB) is not available 100922 |
21 |
> 10:43:05 [ERROR] Aborting |
22 |
> |
23 |
> 100922 10:43:05 [Note] /usr/sbin/mysqld: Shutdown complete |
24 |
|
25 |
As VAH mentions, do try revdep-rebuild. You may also wish to --update |
26 |
--deep --newuse @world, if you don't routinely use --deep --newuse. |
27 |
|
28 |
Meanwhile, I see two issues here, tho only one (your choice) needs |
29 |
corrected. |
30 |
|
31 |
1) Gentoo has changed its default akonadi backend from mysql to sqlite. |
32 |
Previously, mysql was the only backend mature enough to really work |
33 |
properly. sqlite had threading related problems (now fixed), and postgres |
34 |
had issues as well. |
35 |
|
36 |
To change with it, however, requires rebuilding gt-sql and IIRC a couple |
37 |
other packages with the appropriate USE flags. (sqlite, now on by |
38 |
default, for qt-sql, others similarly on by default.) New enough versions |
39 |
are also required, thus the --deep --newuse, with revdep-rebuild to fix up |
40 |
reverse dependencies as usual. |
41 |
|
42 |
The other problem is that the config as to which backend to use is per- |
43 |
user, with emerges not touching user config. So to run the new default |
44 |
sqlite backend, you have to manually adjust your user config. I'm not |
45 |
exactly sure what the proper way to do that is. I simply backed up a |
46 |
couple dirs here (with kde and mysqld stopped) and deleted them, then |
47 |
restarted kde/akonadi and ran akonaditray to fix things. But I ended up |
48 |
having to recreate my address-book resource (the only one I really use |
49 |
ATM, no kopete or similar to worry about), pointing it at the old vcf |
50 |
files using akonaditray, then restarting kde and along with it akonadi, |
51 |
for it to work. There should be a smoother way to do that upgrade, |
52 |
probably involving manually changing the existing config, instead of |
53 |
blowing it away so it can be recreated, and I know nothing about the kopete |
54 |
side if you run it, since I don't. |
55 |
|
56 |
That bypasses the mysql error entirely, since you're switching to sqlite |
57 |
instead. |
58 |
|
59 |
2) You can instead choose to stick with the (heavier but older and better |
60 |
tested) mysql backend. In that case, the above error, that it can't find |
61 |
and start the innodb mysql engine, becomes the one of worry. That one's |
62 |
very likely due to screwed "deep" interdependencies, so again, --update |
63 |
--deep --newuse and revdep-rebuild are your friends. |
64 |
|
65 |
I know there was a recent mysql update, but I didn't bother with it here, |
66 |
as I had seen the changelog notes about switching to sqlite by default and |
67 |
decided to do that, kill the mysql USE flags, and then unmerge it, since |
68 |
akonadi was the only reason mysql was on my system anyway. That and the |
69 |
fact that I routinely use --deep --newuse on my updates, and revdep- |
70 |
rebuild and --depclean after every update as well, to keep my system as |
71 |
self-consistent as possible, is probably why I didn't run into the innodb |
72 |
error you're seeing. |
73 |
|
74 |
-- |
75 |
Duncan - List replies preferred. No HTML msgs. |
76 |
"Every nonfree program has a lord, a master -- |
77 |
and if you use the program, he is your master." Richard Stallman |