Issue MariaDB Upgrade - two startups

[Tobias Stein]

Hi,

I upgraded mariadb 5.5 to 10.0 in a Plesk Onyx Centos7 installation. In general a pretty straight forward approach (as described in https://kb.plesk.com/en/127962). Nontheless, I observed a strange behaviour after rebooting the machine. It seems that two MariaDB instances are starting all of the sudden.

Did anyone encounter something similar? yum says that only one database version is installed.
When I stop mariadb and restart only a single instance the database works fine.

Of course I adjusted the autostart settings of both instances and disabled MariaDB and mysql via the chkconfig tool but it doesn't apply.
# ll /etc/rc3.d/
lrwxrwxrwx 1 root root 15 Dec 4 15:23 K36mysql -> ../init.d/mysql*
lrwxrwxrwx 1 root root 17 Dec 4 15:24 S64mariadb -> ../init.d/mariadb*

Attached is the logfile.
Thanks for your support.

161204 14:42:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161204 14:42:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161204 14:42:53 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB) starting as process 2120 ...
161204 14:42:53 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB) starting as process 2134 ...
161204 14:42:53 [Note] InnoDB: Using mutexes to ref count buffer pool pages
161204 14:42:53 [Note] InnoDB: The InnoDB memory heap is disabled
161204 14:42:53 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
161204 14:42:53 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
161204 14:42:53 [Note] InnoDB: Compressed tables use zlib 1.2.7
161204 14:42:53 [Note] InnoDB: Using Linux native AIO
161204 14:42:53 [Note] InnoDB: Using CPU crc32 instructions
161204 14:42:53 [Note] InnoDB: Initializing buffer pool, size = 128.0M
161204 14:42:53 [Note] InnoDB: Using mutexes to ref count buffer pool pages
161204 14:42:53 [Note] InnoDB: The InnoDB memory heap is disabled
161204 14:42:53 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
161204 14:42:53 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
161204 14:42:53 [Note] InnoDB: Compressed tables use zlib 1.2.7
161204 14:42:53 [Note] InnoDB: Using Linux native AIO
161204 14:42:53 [Note] InnoDB: Using CPU crc32 instructions
161204 14:42:53 [Note] InnoDB: Initializing buffer pool, size = 128.0M
161204 14:42:53 [Note] InnoDB: Completed initialization of buffer pool
161204 14:42:53 [Note] InnoDB: Completed initialization of buffer pool
161204 14:42:53 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
161204 14:42:53 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
161204 14:42:53 [Note] InnoDB: Retrying to lock the first data file
161204 14:42:53 [Note] InnoDB: Highest supported file format is Barracuda.
161204 14:42:53 [Note] InnoDB: 128 rollback segment(s) are active.
161204 14:42:53 [Note] InnoDB: Waiting for purge to start
161204 14:42:54 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 2323536441
161204 14:42:54 [Note] Plugin 'FEEDBACK' is disabled.
161204 14:42:54 [Note] Server socket created on IP: '::'.
161204 14:42:54 [Warning] 'proxies_priv' entry '@% root@centos-71-64-minimal' ignored in --skip-name-resolve mode.
161204 14:42:54 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.28-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
161204 14:42:54 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
161204 14:42:54 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
161204 14:42:55 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
161204 14:42:55 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
161204 14:42:56 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

 

[fogelf]

Try to execute command (then reboot)
chkconfig --del mysql