Atomicorp

I just updated my server. This are the packages that were updated:
Feb 11 16:09:41 Updated: 1:asl-3.2.18-37.el6.art.x86_64
Feb 11 16:09:43 Updated: 1:asl-waf-module-3.2.18-37.el6.art.x86_64
Feb 11 16:09:44 Updated: 1:asl-web-3.2.18-37.el6.art.x86_64
Feb 11 16:10:18 Updated: php-common-5.4.25-31.el6.art.x86_64
Feb 11 16:10:22 Updated: php-cli-5.4.25-31.el6.art.x86_64
Feb 11 16:10:23 Installed: ilmbase-1.0.1-6.1.el6.x86_64
Feb 11 16:10:24 Updated: mysql-libs-5.5.36-21.el6.art.x86_64
Feb 11 16:10:28 Updated: mysql-5.5.36-21.el6.art.x86_64
Feb 11 16:10:28 Installed: OpenEXR-libs-1.6.1-8.1.el6.x86_64
Feb 11 16:10:29 Updated: php-pdo-5.4.25-31.el6.art.x86_64
Feb 11 16:10:30 Updated: php-mysql-5.4.25-31.el6.art.x86_64
Feb 11 16:10:32 Updated: ImageMagick-6.5.4.7-7.el6_5.x86_64
Feb 11 16:10:49 Updated: mysql-server-5.5.36-21.el6.art.x86_64
Feb 11 16:10:51 Updated: php-5.4.25-31.el6.art.x86_64
Feb 11 16:10:53 Updated: php-devel-5.4.25-31.el6.art.x86_64
Feb 11 16:10:54 Updated: php-xml-5.4.25-31.el6.art.x86_64
Feb 11 16:10:54 Updated: php-gd-5.4.25-31.el6.art.x86_64
Feb 11 16:10:56 Updated: php-fpm-5.4.25-31.el6.art.x86_64
Feb 11 16:10:57 Updated: php-soap-5.4.25-31.el6.art.x86_64
Feb 11 16:10:57 Updated: php-mcrypt-5.4.25-31.el6.art.x86_64
Feb 11 16:10:58 Updated: php-mbstring-5.4.25-31.el6.art.x86_64
Feb 11 16:10:58 Updated: php-tidy-5.4.25-31.el6.art.x86_64
Feb 11 16:10:59 Updated: php-imap-5.4.25-31.el6.art.x86_64
Feb 11 16:10:59 Updated: atomic-release-1.0-18.el6.art.noarch


And now I have the problem that mysql and libc are "fighting".

*** glibc detected *** /usr/libexec/mysqld: double free or corruption (fasttop): 0x00007f6fc8004a60 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3edb076166]
/usr/libexec/mysqld(_ZN16Security_context7destroyEv+0xb4)[0x561a24]
/usr/libexec/mysqld(_ZN3THDD1Ev+0x13d)[0x5654ad]
/usr/libexec/mysqld(_ZN3THDD0Ev+0x9)[0x565889]
/usr/libexec/mysqld(_Z10unlink_thdP3THD+0x8d)[0x5186bd]
/usr/libexec/mysqld(_Z29one_thread_per_connection_endP3THDb+0x2d)[0x51872d]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0x139)[0x61f6b9]
/usr/libexec/mysqld(handle_one_connection+0x5b)[0x61f79b]
/lib64/libpthread.so.0[0x3edb4079d1]
/lib64/libc.so.6(clone+0x6d)[0x3edb0e8b6d]
======= Memory map: ========
00400000-00c6f000 r-xp 00000000 08:02 28532 /usr/libexec/mysqld
00e6e000-00f86000 rw-p 0086e000 08:02 28532 /usr/libexec/mysqld
00f86000-00faf000 rw-p 00000000 00:00 0
...
(lots more)

Is there any known problem?

What is the faster easier fix?

Thanks in advance,

I saw the same with this MySQL update from the Atomic channel, but only on machines with ASL, and only just after the update was installed. I couldn't reproduce the issue after restarting MySQL again.

That was it.

Thanks,

Ran into the same issue on a Plesk server. Restarting MySQL alone did not fix it, had to bounce the box.

Solved, had to restart the whole server, the mysql was out of service badly, couldn't be restarted by itself

I just downgraded back to .33 - seems to be fine after that.


MySQL Error log shows

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.


Which would support that the mysql service needs to be killed manually and restarted.

Just updated mysql to:
[root@alien ~]# mysql --version
mysql Ver 14.14 Distrib 5.5.37, for Linux (x86_64) using readline 5.1

and ran into the same problems

140422 10:38:22 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.
140422 10:38:22 InnoDB: Retrying to lock the first data file

so I had to kill mysqld processes and restart it, it works fine now, apparently.

See https://www.atomicorp.com/forum/viewtop ... =24&t=7589