| Summary: | With akonadi using an external mysql server, if mysql is restarted this lead to crash or errors | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Bruno Friedmann <bruno> |
| Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | bugz57, dvratil, mkt.lamont, rohan, Samuele.Kaplun, vo.zaeb, wheel |
| Priority: | NOR | ||
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Bruno Friedmann
2012-01-29 08:47:15 UTC
Reassign Shouldn't akonadi a bit more resistant and before crashing, just try to reconnect automatically to mysql socket ? *** Bug 303039 has been marked as a duplicate of this bug. *** *** Bug 296054 has been marked as a duplicate of this bug. *** This is still active, also on postgresql usage. If the database disappear for what ever reason. akonadi is simply not able to try to reconnect automatically. On never version, at least it doesn't crash, but as it doesn't work without stopping it, and relaunch it's a major pain in A.... If you need a use case, imagine a big terminal server having a centralized db instance. and during saturday night the db server is shutdown to make a full backup, or a update package restart the server. All users who don't have closed akonadi (shudown it) won't be able to use akonadi before a full restart :-( For MySQL at least (haven't tried with PostgreSQL), there's unfortunately a bug in Qt [0] that prevents us from fixing this in any reasonable way in Akonadi. Simply put: Qt will claim connection to database is valid even when the server is not running anymore, and we only learn about it the hard way when a query fails - but even then the MySQL client libraries will return different error code each time, so detecting what went wrong gets really hard. [0] https://bugreports.qt-project.org/browse/QTBUG-17140 *** Bug 323087 has been marked as a duplicate of this bug. *** *** Bug 319550 has been marked as a duplicate of this bug. *** *** Bug 324043 has been marked as a duplicate of this bug. *** *** Bug 316647 has been marked as a duplicate of this bug. *** This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |