[Akonadi] [Bug 340813] New: sometimes two copies of mysqld are running with Akonadi

[Martin Steigerwald]

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

            Bug ID: 340813
           Summary: sometimes two copies of mysqld are running with
                    Akonadi
           Product: Akonadi
           Version: 1.13.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: server
          Assignee: kdepim-bugs at kde.org
          Reporter: ms at teamix.de

Sorry for not being anymore specific, but I have it that sometimes I have two
copies of mysqld running.

Reproducible: Sometimes

Steps to Reproduce:
I am not sure. I seem to have this when I do akonadictl stop and then start it
again. Often I check whether it really quits old mysqld process. But sometimes
I forget this step. Maybe it did not shutdown yet.

It seems to happen more easily when there is a lot of load on the MySQL server,
for example when some search folders are updated.

Actual Results:  
ms at mango:~> ps aux | grep mysql
ms        2391 97.2  5.2 3640268 638488 ?      Sl   09:50  15:05
/usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf
--datadir=/home/ms/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-ms.1pzYYX/mysql.socket
ms        4435  0.2  3.0 1598552 372952 ?      Sl   10:04   0:00
/usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf
--datadir=/home/ms/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-ms.1pzYYX/mysql.socket
ms        4678  0.0  0.0  12676  1708 pts/11   S+   10:05   0:00 grep mysql

Expected Results:  
Never ever there will be two mysqld processes with Akonadi.

Actually I wonder why I didn't see any visible database corruption yet.

In akonadiserver.error.old log I got:

DATABASE ERROR: 
  Error code: 1452 
  DB error:  "Cannot add or update a child row: a foreign key constraint fails
(`akonadi`.`collectionpimitemrelation`, CONSTRAINT
`collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES
`pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)" 
  Error text: "Cannot add or update a child row: a foreign key constraint fails
(`akonadi`.`collectionpimitemrelation`, CONSTRAINT
`collectionpimitemrelation_ibfk_2` FOREIGN KEY (`PimItem_id`) REFERENCES
`pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL3: Unable to
execute statement" 
  Query: "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id)
VALUES (:0, :1)"

In old mysql.err log I have:

InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11

I will attach the complete logs.

I am tempted to raise this to critical due to the potential of having data
loss, but seems mysqld locks the files just fine. So far I didn't see any
inconsistencies which doesn't mean that there are none.

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