[Akonadi] [Bug 415956] Akonadi 19.12.x crash when socket file for connection to postgresql database disappear

Bruno Friedmann bugzilla_noreply at kde.org
Thu Jan 9 13:31:07 GMT 2020


https://bugs.kde.org/show_bug.cgi?id=415956

Bruno Friedmann <bruno at ioda-net.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Akonadi crash when reading  |Akonadi 19.12.x crash when
                   |and moving mail             |socket file for connection
                   |                            |to postgresql database
                   |                            |disappear

--- Comment #2 from Bruno Friedmann <bruno at ioda-net.ch> ---
Application: akonadiserver (5.13.0 (19.12.0))

Qt Version: 5.13.1
Frameworks Version: 5.65.0
Operating System: Linux 5.3.12-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Reading mail after having let kmail2 open and idle during 2,3 hours.

One interesting log in console
ProtocolException thrown:Timeout while waiting for data
ProtocolException thrown:ProtocolException thrown:Timeout while waiting for
dataProtocolException thrown:Timeout while waiting for data

Timeout while waiting for data
ProtocolException thrown:ProtocolException thrown:Timeout while waiting for
dataTimeout while waiting for data

ProtocolException thrown:Timeout while waiting for data
org.kde.pim.akonadiserver: NotificationSubscriber for
"MailFilterCollectionMonitor - 94151401733072" : timeout writing into stream
org.kde.pim.akonadiserver: Subscriber "SpecialCollectionsMonitor -
94000591742048" disconnected
org.kde.pim.akonadiserver: Subscriber "KMail Kernel ETM - 94000592474800"
disconnected
ProtocolException thrown:Failed to write data to stream
terminate called after throwing an instance of 'Akonadi::ProtocolException'
  what():  Failed to write data to stream
KCrash: Application 'akonadiserver' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1502/kdeinit5__0
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: ""
org.kde.pim.akonadiserver:   DB error:  "could not receive data from server:
Bad file descriptor\n()"
org.kde.pim.akonadiserver:   Error text: "could not receive data from server:
Bad file descriptor\n() QPSQL: Unable to create query"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(qlonglong, 555)))
org.kde.pim.akonadiserver:   Query: "SELECT
CollectionMimeTypeRelation.Collection_id,
CollectionMimeTypeRelation.MimeType_id, MimeTypeTable.name FROM
CollectionMimeTypeRelation LEFT JOIN MimeTypeTable ON ( MimeTypeTable.id =
CollectionMimeTypeRelation.MimeType_id ) WHERE (
CollectionMimeTypeRelation.Collection_id IN ( :0 ) ) ORDER BY
CollectionMimeTypeRelation.Collection_id ASC"
org.kde.pim.akonadiserver: Handler exception when handling command
FetchCollections on connection akonadi_mailfilter_agent (0x55ba851efb50) :
Unable to retrieve mimetypes for listing
org.kde.pim.akonadiserver: Shutting down "akonadi_mailfilter_agent" ...
ProtocolException thrown:Timeout while waiting for data
ProtocolException thrown:Timeout while waiting for data

Database inside log
Jan 09 14:12:05 qt-kt postgres[21454]: [7-1] 2020-01-09 14:12:05.264 CET 1
21454 bf_akonadi  bf_akonadi LOG:  could not receive data from client:
Connection reset by peer

The socket file has been recreated at crash time
ll /run/postgresql/
total 8
srwxrwxrwx 1 postgres postgres  0 Jan  9 14:09 .s.PGSQL.5432
-rw------- 1 postgres postgres 60 Jan  9 14:09 .s.PGSQL.5432.lock
-rw-r--r-- 1 postgres postgres  5 Jan  7 20:23 postmaster.pid

while the server is up since Jan 5th.

So while it is certainly not ideal to have the socket file that disappear,
akonadi should be resilient to this error, and not crash as it do.

The crash can be reproduced every time.


Possible duplicates by query: bug 415991, bug 415962, bug 415956, bug 415930,
bug 415815.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kdepim-bugs mailing list