Re: recurrent mysqld socket connection problem

Thank you Dan for another very helpful answer. Since I reported this problem, 
I backed up and restored the mysql database and it seemed to correct the first 
part of the problem, i.e. the one related to the InnoDB stuff. However, your 
diagnosis was correct, the DBus issue continued to occur and I use NVidia 
propriety drivers. For that part of the problem, the following seems to 
correct the issue:

pkill akonadi_control &
pkill akonadiserver &
mysqladmin shutdown --socket 
~/.local/share/akonadi/socket-$(hostname)/mysql.socket &
akonadictl start

Thanks!

Hakan

On Thursday, January 02, 2014 03:33:42 PM Daniel Vrátil wrote:
> 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

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlLJsHQACgkQu5WqKQPUC0uXrgCfeQMBoXoLTqgK00N33zbjdqQw
HGcAoJKI/K4FVTlhmN/NIOzASWnrbjmi
=x4Xz
-----END PGP SIGNATURE-----