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

Martin Steigerwald ms at teamix.de
Wed Jan 28 09:11:33 GMT 2015


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

--- Comment #4 from Martin Steigerwald <ms at teamix.de> ---
Created attachment 90734
  --> https://bugs.kde.org/attachment.cgi?id=90734&action=edit
mysql.err.old with corruption that I think may have happened due to this bug

This is related to my last comment and it clearly shows that MySQL wasn´t too
happy about running twice on the same database. I did not shutdown any mysqld
process uncleanly, so that message may just be related to that another mysqld
process was still running at the time of the message in the log. I will now
start akonadi again and watch the error log. I didn´t kill the old instance of
mysqld here on purpose to show this bug again, I hope the database is still
sound and mysql is able to recover.

141029 13:49:02 [Note] Plugin 'FEDERATED' is disabled.
141029 13:49:02 InnoDB: The InnoDB memory heap is disabled
141029 13:49:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141029 13:49:02 InnoDB: Compressed tables use zlib 1.2.8
141029 13:49:02 InnoDB: Using Linux native AIO
141029 13:49:02 InnoDB: Initializing buffer pool, size = 512.0M
141029 13:49:02 InnoDB: Completed initialization of buffer pool
141029 13:49:02 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141029 13:49:02  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
141029 13:49:03  InnoDB: Waiting for the background threads to start
141029 13:49:04 InnoDB: 5.5.39 started; log sequence number 30133605273
141029 13:49:04 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.39-1'  socket: '/tmp/akonadi-ms.L69DqH/mysql.socket'  port: 0 
(Debian)

Status information:

Current dir: /home/ms/.local/share/akonadi/db_data/
Running threads: 34  Stack size: 262144
Current locks:
lock: 0x7f9bec1c9db0:

lock: 0x7f9bec1c2bd0:

lock: 0x7f9bec1c0630:

lock: 0x7f9bec1bde60:
[…]


141029 14:38:11 [Note] Plugin 'FEDERATED' is disabled.
141029 14:38:11 InnoDB: The InnoDB memory heap is disabled
141029 14:38:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141029 14:38:11 InnoDB: Compressed tables use zlib 1.2.8
141029 14:38:11 InnoDB: Using Linux native AIO
141029 14:38:11 InnoDB: Initializing buffer pool, size = 512.0M
141029 14:38:11 InnoDB: Completed initialization of buffer pool
141029 14:38:11 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141029 14:38:11  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
141029 14:38:12  InnoDB: Waiting for the background threads to start
141029 14:38:13 InnoDB: 5.5.39 started; log sequence number 30141310511
141029 14:38:13 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.39-1'  socket: '/tmp/akonadi-ms.ixkIX5/mysql.socket'  port: 0 
(Debian)
141029 15:10:51 [Note] /usr/sbin/mysqld: Normal shutdown

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


More information about the Kdepim-bugs mailing list