Re: recurrent mysqld socket connection problem

Daniel Vrátil <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Organization Red Hat
Message-ID <15101528.5S2WUIn93Y@odin>
On Tuesday 31 of December 2013 02:35:53 E. Hakan Duran wrote:
> Hi all,

Hi,

> During the last couple of days, I have been having recurrent problems in
> launching Kontact. It doesn't open normally reporting error to connect to
> the Dbus session of Mysql, either settings being very wrong or complaining
> corruption of InnoDB files. After doing some Google search, I moved these
> files (ib_logfile0, ib_logfile1, ibdata1)) from
> $HOME/.local/share/akonadi/db_data to another folder and copied them back
> with the following command:
> cp -a ib* $HOME/.local/share/akonadi/db_data
> Most of the time it worked. A few times it didn't, and after loging out and
> in a few times, it finally worked again. However, there is no telling what
> it will do the next time I login to KDE.

If the problem with Akonadi not working appears right after you log in to your 
session and you use the proprietary nvidia drivers, your problem could be this 
[0].

if it's really a corruption in the log files, removing ib_logfile* is usually 
fine (not the ibdata one though). They will be recreated on next MySQL start. 
In the worst case you will lose uncommitted transactions, but the missing data 
will be fetched from server again, or you will lose some changes (flags 
changes, item moves, etc) - no data loss though.

Dan

[0] https://bugs.kde.org/show_bug.cgi?id=326480

> I made backups of akonadi database, kdepim settings and kwallet stuff,
> assuming that this was due to database corruption. However, I don't know if
> it is worth to erase the whole thing and restore it from the backup. I
> don't want to spend hours and at the end still lose data. Any bright
> suggestions are welcome.
> 
> I guess this is another down side of dealing with akonadi/mysql database
> structure. I have to admit I am yet to see an advantage of this decision
> after 3 years maybe? Sorry for ranting.
> 
> I am currently on Fedora 20, KDE 4.11.4.
> 
> Thanks,
> 
> Hakan

-- 
Daniel Vrátil
KDE Desktop Team
Associate Software Engineer, Red Hat, Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users
signature.asc (application/pgp-signature, 490 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAABAgAGBQJSxXjGAAoJEMWdYU9vSuNIJvEH/2rqVsIsqKvLyB5ZaQpI1qtg
dnSvPnpL26MqetXoQPoprqYur+KuJPGh59OUMLL4mCVVPUtRcaSfUHfgGJa+awQg
L7xO5+cpgg1LqGSGXBQQ2kP2R7XDXpitsXl0m/rf9bYAHHBHRQwzf5tFlKhelQdN
mTQHcf7lia5uUz7YlE+QQQ83UdPkjW5F5QfZjxFgdVJXy57e6TlGz6FHKNoOqfBZ
r9bP6lo6wD0eWf3+OZlxnxBYlmlFam+Oyvf1U2itC9lLXaO3KXXRjh+f0x5PjqHY
4COx1V6hT9V8DNkxjmut4tELuXraE042rvzJAGi1R1rHpVY7X3i2NcCfOVDpp3s=
=4Zpl
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.