http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c10 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de --- Comment #10 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Nick Dordea from comment #9)
(In reply to Fabian Vogt from comment #8)
mysql.err clearly shows that the database got corrupted, there's unfortunately not much you can do at that point. Turning on recovery mode and trying to pull as much data is the best option, but might not result in a usable clone.
I agree that the error messages during akonadi initiated/controlled start point to corrupted data.
However, the akonadi database was available via mysql -h localhost -u root -p I can not explain how comes that after mysql -h localhost -u root -p , sql queries worked .... not only sql queries but also mysql-check did not point to any issues with table belonging to akonadi database .
Is akonadi ceating/using a proprietary database different from the akonadi database accessed via mysql -h localhost -u root -p ?
By default, akonadi's database can be connected to with mysql -S /run/user/1000/akonadi/mysql.socket It's also possible that errors only appear with write accesses.
It is very strange complains that the connection fails while other user/utility has problems.
Could you please tell me if we can customize kmail to access akonadi database directly without database services provided via "akonadi" packages ?
There's a way, but the UI for that got removed so you'd have to edit ~/.config/akonadi/akonadiserverrc manually.
Thanks,
ND
-- You are receiving this mail because: You are on the CC list for the bug.