[Akonadi] [Bug 332781] Akonadi server fails to start right after upgrading to 1.12.0
https://bugs.kde.org/show_bug.cgi?id=332781 Stephan Menzel stephan.men...@gmx.eu changed: What|Removed |Added CC||stephan.men...@gmx.eu --- Comment #4 from Stephan Menzel stephan.men...@gmx.eu --- I'm having the exact same problem here with both akonadi 1.12 and 1.12.1. The only thing that helps is a downgrade to 1.11. My problem description and stacktrace are the same. Also, I can connect to the MySQL server with other tools with no problems. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332781] Akonadi server fails to start right after upgrading to 1.12.0
https://bugs.kde.org/show_bug.cgi?id=332781 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Daniel Vrátil dvra...@redhat.com --- Closing, sounds like a problem with MySQL lock or PID not being properly cleaned up after previous shutdown. We cannot cope with that well yet, but there's another report about this somewhere. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332781] Akonadi server fails to start right after upgrading to 1.12.0
https://bugs.kde.org/show_bug.cgi?id=332781 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added CC||dvra...@redhat.com --- Comment #1 from Daniel Vrátil dvra...@redhat.com --- Can you please make sure that no MySQL instances are running and that there's no *.lock file in ~/.local/share/akonadi and then try starting Akonadi from console via akonadictl start? If it fails, please provide output from self-test dialog (you will get it by running KMail for example). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332781] Akonadi server fails to start right after upgrading to 1.12.0
https://bugs.kde.org/show_bug.cgi?id=332781 --- Comment #2 from Aitor m...@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 the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
