* [gentoo-user] Re: akonadi ... don't you just love it?
@ 2014-08-11 19:05 99% ` Mick
0 siblings, 0 replies; 1+ results
From: Mick @ 2014-08-11 19:05 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 4294 bytes --]
On Saturday 09 Aug 2014 21:00:48 Mick wrote:
> First some general observations that relate to kmail2:
>
> I thought of giving the latest kmail-4.12.5 a spin. So installed it on a
> machine and set up a couple of IMAP4 servers to get messages from. An
> account with a messages in the low hundreds works fine. An account with
> messages in the 100k plus range works like a dog. While kmail fetches
> headers and then akonadi sets off to organise threads and whatever else it
> wants to do the application becomes pretty much unresponsive and the CPU
> climbs up to 98%. Half an hour later I can get back to it. :-@
>
> Anyway, this is not the current problem. I updated mysql to 5.5.39, then I
> kmail would not start with akonadi failing with "mysql log containing
> errors". So I ran:
>
> mysql_upgrade --socket=/tmp/akonadi-michael.NFvLpB/mysql.socket
>
> which completed without an error. Kmail still failed to start. Trying to
> start akonadi console states:
>
> "Failed to connect to database. Driver not loaded"
>
> Then the pop up Details window says MySQL log contains errors, just like
> when I try to start kmail. This is what I see in
> .local/share/akonadi/db_data/mysql.err:
>
> 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.
> 140809 20:58:42 InnoDB: Unable to open the first data file
> InnoDB: Error in opening ./ibdata1
> 140809 20:58:42 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
> 140809 20:58:42 InnoDB: Could not open or create data files.
> 140809 20:58:42 InnoDB: If you tried to add new data files, and it failed
> here,
> 140809 20:58:42 InnoDB: you should now edit innodb_data_file_path in my.cnf
> back
> 140809 20:58:42 InnoDB: to what it was, and remove the new ibdata files
> InnoDB created
> 140809 20:58:42 InnoDB: in this failed attempt. InnoDB only wrote those
> files full of
> 140809 20:58:42 InnoDB: zeros, but did not yet use them in any way. But be
> careful: do not
> 140809 20:58:42 InnoDB: remove old data files which contain your precious
> data!
> 140809 20:58:42 [ERROR] Plugin 'InnoDB' init function returned error.
> 140809 20:58:42 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
> failed.
> 140809 20:58:42 [ERROR] Unknown/unsupported storage engine: innodb
> 140809 20:58:42 [ERROR] Aborting
>
>
> So I moved ./ibdata* and tried again with the same error. Is there
> something else I should be doing here to get this going?
Kids, when in doubt, go back to the basics! :-p
I thought that I *had* run revdep-rebuild, but perhaps I am losing count with
the different machines I look after? Ha, ha!
Anyway, after another irrelevant update today revdep-rebuild showed this:
========================================================================
* Checking dynamic linking consistency
[ 33% ] * broken /usr/lib/qt4/plugins/sqldrivers/libqsqlmysql.so (requires
libmysqlclient_r.so.16)
[ 85% ] * broken /usr/lib64/qt4/plugins/sqldrivers/libqsqlmysql.so
(requires libmysqlclient_r.so.16)
[ 100% ]
* Generated new 3_broken.rr
* Assigning files to packages
* /usr/lib/qt4/plugins/sqldrivers/libqsqlmysql.so -> dev-qt/qtsql
* /usr/lib64/qt4/plugins/sqldrivers/libqsqlmysql.so -> dev-qt/qtsql
* Generated new 4_raw.rr and 4_owners.rr
* Cleaning list of packages to rebuild
* Generated new 4_pkgs.rr
* Assigning packages to ebuilds
* Generated new 4_ebuilds.rr
* Evaluating package order
* Generated new 5_order.rr
* All prepared. Starting rebuild
emerge --complete-graph=y --oneshot --verbose -a dev-qt/qtsql:4
========================================================================
Now all works as expected - apologies for the noise!
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-08-09 20:00 [gentoo-user] akonadi ... don't you just love it? Mick
2014-08-11 19:05 99% ` [gentoo-user] " Mick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox