[MDEV-632] LP:908914 - akonadi & mariadb 5.5; xtradb seems to crash Created: 2011-12-27  Updated: 2014-03-03  Resolved: 2014-03-03

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Maarten Vanraes (Inactive) Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug908914.xml     File LPexportBug908914_mysql.err.old     Text File LPexportBug908914_mysql.err.old.txt     Text File LPexportBug908914_mysql.err.old.txt    

 Description   

not all details yet, but see error log



 Comments   
Comment by Maarten Vanraes (Inactive) [ 2011-12-27 ]

Re: akonadi & mariadb 5.5; xtradb seems to crash

Comment by Maarten Vanraes (Inactive) [ 2011-12-27 ]

mysql.err.old
LPexportBug908914_mysql.err.old

Comment by Maarten Vanraes (Inactive) [ 2011-12-27 ]

Re: akonadi & mariadb 5.5; xtradb seems to crash
this one is from another user, it doesn't have the error itself, i'm waiting for that atm, but if you look through it you see that several times the'res no shutdown between starts, which means it just shut down hard, or something.

but; with innodb there is no recovery procedure started, while with xtradb there is.

i'll post the error when i get it

Comment by Maarten Vanraes (Inactive) [ 2011-12-27 ]

this one is from another user, it doesn't have the error itself, i'm waiting for that atm, but if you look through it you see that several times the'res no shutdown between starts, which means it just shut down hard, or something.

but; with innodb there is no recovery procedure started, while with xtradb there is.

i'll post the error when i get it
mysql.err.old.txt
LPexportBug908914_mysql.err.old.txt

Comment by Elena Stepanova [ 2011-12-27 ]

Re: akonadi & mariadb 5.5; xtradb seems to crash
From what I see, there is recovery each time after the server didn't shutdown normally, be it innodb or xtradb. Example:

111106 12:44:07 InnoDB: 1.1.8 started; log sequence number 835797051
111106 12:44:08 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.15' socket: '/home/pnunn/.local/share/akonadi/socket-localhost.localdomain/mysql.socket' port: 0 Mageia - MySQL Community Edition (GPL)

-> here the previous instance didn't end properly <-

111106 21:52:14 InnoDB: The InnoDB memory heap is disabled
111106 21:52:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111106 21:52:14 InnoDB: Compressed tables use zlib 1.2.5
111106 21:52:14 InnoDB: Using Linux native AIO
111106 21:52:16 InnoDB: Initializing buffer pool, size = 80.0M
111106 21:52:16 InnoDB: Completed initialization of buffer pool
111106 21:52:17 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!

-> recovery <-

111106 21:52:17 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...
111106 21:52:23 InnoDB: Waiting for the background threads to start

Comment by Maarten Vanraes (Inactive) [ 2011-12-29 ]

Re: akonadi & mariadb 5.5; xtradb seems to crash
this is finally the real log from the 2nd person (this time with the error)

i see it stopping and sometimes not completing the shutdown, but likely killed off and then started up again

then there's a weird thing, innodb log files gone??? ibdata looks like it being opened by something else?

Comment by Maarten Vanraes (Inactive) [ 2011-12-29 ]

this is finally the real log from the 2nd person (this time with the error)

i see it stopping and sometimes not completing the shutdown, but likely killed off and then started up again

then there's a weird thing, innodb log files gone??? ibdata looks like it being opened by something else?

mysql.err.old.txt
LPexportBug908914_mysql.err.old.txt

Comment by Rasmus Johansson (Inactive) [ 2012-03-29 ]

Launchpad bug id: 908914

Generated at Thu Feb 08 06:30:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.