Bug 447311

Summary: Akonadi server is not starting
Product: [Frameworks and Libraries] Akonadi Reporter: sourcemaker <kde-bugzilla>
Component: serverAssignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: major    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description sourcemaker 2021-12-20 21:22:41 UTC 
MariaDB is up and running, 
but the following statement is taking too much time:

SELECT count(DISTINCT PimItemTable.id), sum(PimItemTable.size), sum(CASE WHEN ( SeenFlags.Flag_id IS NOT NULL OR IgnoredFlags.Flag_id IS NOT NULL ) THEN 1 ELSE 0 END), PimItemTable.collectionId FROM PimItemTable LEFT JOIN PimItemFlagRelation AS SeenFlags ON ( PimItemTable.id = SeenFlags.PimItem_id AND SeenFlags.Flag_id = ? ) LEFT JOIN PimItemFlagRelation AS IgnoredFlags ON ( PimItemTable.id = IgnoredFlags.PimItem_id AND IgnoredFlags.Flag_id = ? ) GROUP BY PimItemTable.collectionId

Why does this problem occur suddenly?
I haven't installed any updates.
Comment 1 sourcemaker 2021-12-22 20:42:05 UTC 
I deleted the Akonadi configuration and database and made a second attempt. 
Clean fresh configuration.

Same issue again:
The Akonadi personal information management service is not operational

The SQL statement that caused the error:
=================================

 SELECT Count(DISTINCT pimitemtable.id),
       Sum(pimitemtable.size),
       Sum(CASE
             WHEN ( SeenFlags.flag_id IS NOT NULL
                     OR IgnoredFlags.flag_id IS NOT NULL ) THEN 1
             ELSE 0
           END),
       pimitemtable.collectionid
FROM   pimitemtable
       LEFT JOIN pimitemflagrelation AS SeenFlags
              ON ( pimitemtable.id = SeenFlags.pimitem_id
                   AND SeenFlags.flag_id = ? )
       LEFT JOIN pimitemflagrelation AS IgnoredFlags
              ON ( pimitemtable.id = IgnoredFlags.pimitem_id
                   AND IgnoredFlags.flag_id = ? )
GROUP  BY pimitemtable.collectionid
Comment 2 sourcemaker 2022-10-16 14:26:18 UTC 
This ticket is obsolete.
The error no longer occurred in current versions.