Review Request 129264: handle mysql process crashes gracefully

[Martin Koller]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129264/
-----------------------------------------------------------

(Updated Oct. 30, 2016, 5:53 p.m.)


Review request for Akonadi and Daniel Vrátil.


Changes
-------

looking into the "system crash" sceanrio, what about the simple following idea:

if we find a socket file, then normally the server is already running - except your above scenario.

When we now just do the "cleanup" (removal of the socket file) in the case when the "initConnection"
can not open a connection to the db, that should be enough, right ?


Repository: akonadi


Description
-------

It happened to me that I started kmail but could not see any mail folder.
Searching I found that although all akonadi processes were running, the mysqld process was not,
so it seems for whatever reason mysqld crashed (using a privately started mysqld from akonadiserver).

This patch checks if the mysqld stops unexpectedly when it was started from akonadiserver and tells the latter to quit when a stopped mysqld was discovered.
Also in this case the local socket file is removed so that a restart can work without problem.


Diffs (updated)
-----

  src/server/storage/dbconfigmysql.h 27841e8 
  src/server/storage/dbconfigmysql.cpp 0962ccb 

Diff: https://git.reviewboard.kde.org/r/129264/diff/


Testing
-------

Started akonadi via akonadictl and also implicitely via kmail, then killed (-4, -15) mysqld.
Restarted via akonadictl or kmail


Thanks,

Martin Koller

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20161030/9807acd6/attachment.html>