[gentoo-user] mysql-5.6.22 update borked akonadi

[Mick]

Hi All,

I just updated a laptop after a week's abstinence and with mysql-5.6.22 
akonadi won't start.  This error renders this laptop useless for email (it 
uses kmail) and therefore I am hesitant to update other boxen to avoid a luser 
riot.  Have you experienced such a problem?  How can I fix it?


This is the error log:
======================

2015-01-25 09:18:08 3192 [Warning] Buffered warning: Changed limits: 
max_open_files: 1024 (requested 5000)

2015-01-25 09:18:08 3192 [Warning] Buffered warning: Changed limits: 
max_connections: 214 (requested 256)

2015-01-25 09:18:08 7f3605d7c740 InnoDB: Warning: Using 
innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in 
future releases, together with the option innodb_use_sys_malloc and with the 
InnoDB's internal memory allocator.
2015-01-25 09:18:08 3192 [Note] InnoDB: Using atomics to ref count buffer pool 
pages
2015-01-25 09:18:08 3192 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-25 09:18:08 3192 [Note] InnoDB: Mutexes and rw_locks use GCC atomic 
builtins
2015-01-25 09:18:08 3192 [Note] InnoDB: Memory barrier is not used
2015-01-25 09:18:08 3192 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-01-25 09:18:08 3192 [Note] InnoDB: Using Linux native AIO
2015-01-25 09:18:08 3192 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-25 09:18:08 3192 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2015-01-25 09:18:08 3192 [Note] InnoDB: Completed initialization of buffer 
pool
2015-01-25 09:18:08 3192 [Note] InnoDB: Highest supported file format is 
Barracuda.
2015-01-25 09:18:08 3192 [Note] InnoDB: The log sequence numbers 20549320007 
and 20549320007 in ibdata files do not match the log sequence number 
20692769575 in the ib_logfiles!
2015-01-25 09:18:08 3192 [Note] InnoDB: Database was not shutdown normally!
2015-01-25 09:18:08 3192 [Note] InnoDB: Starting crash recovery.
2015-01-25 09:18:08 3192 [Note] InnoDB: Reading tablespace information from 
the .ibd files...
2015-01-25 09:18:08 3192 [Note] InnoDB: Restoring possible half-written data 
pages
2015-01-25 09:18:08 3192 [Note] InnoDB: from the doublewrite buffer...
09:18:08 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=214
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 85119 K  
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x83f5c0]
/usr/sbin/mysqld(handle_fatal_signal+0x34d)[0x61fcbd]
/lib64/libpthread.so.0(+0x11250)[0x7f3604aed250]
/usr/sbin/mysqld[0x9e3d28]
/usr/sbin/mysqld[0x9e4df1]
/usr/sbin/mysqld[0x96d245]
/usr/sbin/mysqld[0x8cc8e4]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x57d401]
/usr/sbin/mysqld[0x6975d0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x91c)[0x69b5dc]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x83f)[0x57722f]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f360414edb5]
/usr/sbin/mysqld[0x56c9e5]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
======================

-- 
Regards,
Mick