[Akonadi] [Bug 340813] sometimes two copies of mysqld are running with Akonadi
Martin Steigerwald
ms at teamix.de
Wed Jan 28 09:04:17 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=340813
Martin Steigerwald <ms at teamix.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
--- Comment #3 from Martin Steigerwald <ms at teamix.de> ---
This does still happen (this is with Akonadi 1.13 master git branch with
database optimizations and KDEPIM + Runtime 4.14.2 as packages in Debian
unstable):
ms at merkaba:~> akonadictl stop
Akonadi is not running.
ms at merkaba:~#4> akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
search paths: ("/usr/local/lib/kde4", "/home/ms/.kde/lib/kde4/plugins/",
"/usr/lib/kde4/plugins/", "/usr/local/lib/plugins/",
"/usr/lib/x86_64-linux-gnu/qt4/plugins", "/usr/local/bin",
"/usr/lib/kde4/plugins", "/usr/local/lib/plugins", "/home/ms/.kde/lib/kde4/",
"/usr/lib/kde4/")
Akonadi Server Search Support: available (Remote Search, Akonadi Baloo Search
Plugin)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent,
akonadi_baloo_indexer, akonadi_birthdays_resource, akonadi_contacts_resource,
akonadi_davgroupware_resource, akonadi_folderarchive_agent,
akonadi_followupreminder_agent, akonadi_googlecalendar_resource,
akonadi_googlecontacts_resource, akonadi_ical_resource,
akonadi_icaldir_resource, akonadi_imap_resource, akonadi_invitations_agent,
akonadi_kabc_resource, akonadi_kalarm_dir_resource, akonadi_kalarm_resource,
akonadi_kcal_resource, akonadi_kdeaccounts_resource, akonadi_knut_resource,
akonadi_kolab_resource, akonadi_kolabproxy_resource,
akonadi_localbookmarks_resource, akonadi_maildir_resource,
akonadi_maildispatcher_agent, akonadi_mailfilter_agent,
akonadi_mailtransport_dummy_resource, akonadi_mbox_resource,
akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_nepomuk_feeder,
akonadi_newmailnotifier_agent, akonadi_nntp_resource, akonadi_notes_agent,
akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource,
akonadi_sendlater_agent, akonadi_vcard_resource, akonadi_vcarddir_resource
ms at merkaba:~> ps aux | grep "[m]ysql" | grep ms
ms 4006 0.4 3.8 2809592 631456 ? Sl Jan27 6:26
/usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf
--datadir=/home/ms/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-ms.QEKpW0/mysql.socket
After minutes after issuing akonadictl stop:
ms at merkaba:~> ps aux | grep "[m]ysql" | grep ms
ms 4006 0.4 3.8 2809592 631456 ? Sl Jan27 6:27
/usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf
--datadir=/home/ms/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-ms.QEKpW0/mysql.socket
And look when I start it again:
ms at merkaba:~> ps aux | grep "[m]ysql" | grep ms
ms 4006 0.4 3.8 2809592 632112 ? Sl Jan27 6:40
/usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf
--datadir=/home/ms/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-ms.QEKpW0/mysql.socket
ms 29368 1.0 0.5 787196 85964 ? Sl 09:54 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.QEKpW0/mysql.socket
This is a *huge*, *big* *no-go*. At no point of time Akonadi should there
*ever* be *two* instances of MySQL running for the same user and the *same*
database.
As this bug is about the stopping of Akonadi I will file a new bug about having
two instances of MySQL running. From all I know this just is a very, very bad
idea.
And I think I lost my private Akonadi MySQL database due to this in combination
with some impatience of mine as I saw mysqld replaying from log file and
bursting writes of about 150-300 MiB/s sustained for *minutes*, totalling to
several times the size of the complete MySQL database. I stopped it with
SIGKILL to end the excessive writing.
As I think that this causes *real* data loss, loss of the complete Akonadi
MySQL database I am raising bug severity. I think I still have the MySQL error
log available.
Now even after writing all of this, the initial left over mysqld still did not
end:
ms at merkaba:~> ps aux | grep "[m]ysql" | grep ms
ms 4006 0.4 3.9 2809592 632260 ? Sl Jan27 6:45
/usr/sbin/mysqld --defaults-file=/home/ms/.local/share/akonadi/mysql.conf
--datadir=/home/ms/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-ms.QEKpW0/mysql.socket
Yet a friendly SIGTERM finishes it:
ms at merkaba:~> kill 4006
ms at merkaba:~> ps aux | grep "[m]ysql" | grep ms
ms at merkaba:~#1>
And I have this:
ms at merkaba:~/.local/share/akonadi/db_data> cat mysql.err
150128 9:54:11 [Note] Plugin 'FEDERATED' is disabled.
150128 9:54:11 InnoDB: The InnoDB memory heap is disabled
150128 9:54:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150128 9:54:11 InnoDB: Compressed tables use zlib 1.2.8
150128 9:54:11 InnoDB: Using Linux native AIO
150128 9:54:11 InnoDB: Initializing buffer pool, size = 512.0M
150128 9:54:11 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
150128 9:54:11 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
And a mysql.err.old that is 875 KiB. I will attach it in a moment.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list