Created attachment 395052 [details] emerge --info dev-db/mysql-5.6.22: crashed - mysqld got signal 11
Created attachment 395054 [details] mysql.err crash log
downgraded to version: 5.5.40, no crash
Did this happen after upgrading or during normal operation?
I would like to see the mysqld.err log starting from the first startup of 5.6.22. Was mysql_upgrade run?
Also post my.cnf as well.
Did you happen to skip running mysql_upgrade on 5.5.40? http://bugs.mysql.com/bug.php?id=67319 seems relevant.
(In reply to Tomas Mozes from comment #3) > Did this happen after upgrading or during normal operation? This happened after upgrading from 5.5.40.
(In reply to Brian Evans from comment #5) > Also post my.cnf as well. my.cnf is default, updated with etc-update
From #gentoo: 11:20:12 AM - grknight: cilly: mysql_upgrade works similar to the mysql cli client.. needs user and password 11:20:51 AM - cilly: grknight: never used it 11:21:05 AM - cilly: grknight: just created my tables once and thats it 11:21:11 AM - grknight: cilly: it is critical to use for each major/minor update 11:21:48 AM - grknight: cilly: 5.1 -> 5.5 is critical to use as well 11:23:04 AM - cilly: grknight: I had no issues until 5.6 11:23:11 AM - cilly: grknight: everything worked flawlessly 11:24:00 AM - grknight: cilly: really depends on what is used, but 5.6 looks for an index and crashes when mysql_upgrade is not run on a 5.5 install The mysql_upgrade script must be run on each major.minor update or problems may occur. Upstream does not support jumping versions without it as noted in ${URL}
After running `mysql_upgrade -u root -p` on version 5.5.40, then reinstalled 5.6.22. It works now. Thx to Brian Evans.
