[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Akonadi] [Bug 332781] Akonadi server fails to start right after upgrading to 1.12.0
From:       Aitor <mail () aitorpazos ! es>
Date:       2014-03-31 22:00:22
Message-ID: bug-332781-17878-aDzwuyV5jU () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=332781

--- Comment #2 from Aitor <mail@aitorpazos.es> ---
I might not expressed myself very clearly, sorry. I'll try to clarify what I
did try.
Once I detected Akonadi was not able to start, I tried to find out what was
going on. I was using the default internal MySQL based configuration. With this
setup, when I tried to start Akonadi with "akonadictl start", Akonadi failed to
boot and at the same time it automatically launched multiple mysqld instances
(which might be another bug). At that moment I decided to check the MySQL's
data integrity and I started MySQL manually, which did so without any problem.
With MySQL booted manually, I decided to change Akonadi's configuration to
point it to this manually started instance of MySQL. Akonadi's error message
was the same as when it tried to use the default configuration. Mean while I
tried with a new clean profile (different user) and I saw that Akonadi booted
correctly. At this point, I decided to backup MySQL DB (ask me if you want me
to check some data in this DB) and I've wiped the whole .local/share/akonadi
folder. Since my data is backed by other servers I have no big problems doing
so, but it might be an issue for other people.
My Akonadi DB was quite old, so I don't know if that might have been an issue.
Unfortunatly, I forgot to backup old akonadiserver.error and
akonadi_control.error files, sorry. The only portion of that files available is
the one posted in the bug description.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]