CloudLinuix 7.3 MySQL restart issue

[fen7azy]

Ive installed CloudLinux 7.3 with cPanel. Ive tested few things and I notice that when I restart MySQL with (but not limited to):

/scripts/restartsrv_mysql

Its restart successfully, however I am getting the following error in the MySQL error log:

2016-11-28 23:37:44 42874 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2016-11-28 23:37:44 42874 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

Ive checked which process is using ibdata1 file, and its governor and MySQL itself. Ive killed MySQL and stopped governor, after which Ive restarted once again MySQL, but the error continues. The only solution to run MySQL correctly is to restart the entire server.

Any suggestions?

[bogdan.sh]

What cPanel version do you use? I remember there was something fixed in cPanel v60.0.17 :

> Fixed case CPANEL-9529: Have restartsrvs systemd logic factor in pidfile.

Also, try using lates governor from beta.

[fen7azy]

I am using WHM 60.0 (build 25) . Clean CentOS7 with cPanel doesn have such issue as I am testing 2 servers on the same time one with CentOs7 + cPanel second with CloudLinux 7.3 + cPanel .

[bogdan.sh]

I am not sure what is going on there. Better to create support ticket with https://helpdesk.cloudlinux.com .

[bogdan.sh]

Same problem here, Ive created a support ticket.
Restarting with "service mysql restart" works just fine.

Error when restarting using /script/restartsrv_mysql (the same that chksrvd uses):

2018-12-21 13:01:42 139663034878144 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded

2018-12-21 13:01:42 139663034878144 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables

2018-12-21 13:01:42 139663034878144 [ERROR] Aborting

2018-12-21 13:01:42 140088337995968 [ERROR] mysqld: Cant lock aria control file /var/lib/mysql/aria_log_control for exclusive use, error: 11. Will retry for 30 seconds

2018-12-21 13:02:13 140088337995968 [ERROR] mysqld: Got error Could not get an exclusive lock; file is probably in use by another process when trying to use aria control file /var/lib/mysql/aria_log_control

2018-12-21 13:02:13 140088337995968 [ERROR] Plugin Aria init function returned error.

2018-12-21 13:02:13 140088337995968 [ERROR] Plugin Aria registration as a STORAGE ENGINE failed.

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Uses event mutexes

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Compressed tables use zlib 1.2.7

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Using Linux native AIO

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Number of pools: 1

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Using SSE2 crc32 instructions

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Completed initialization of buffer pool

2018-12-21 13:02:13 140087745267456 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2018-12-21 13:02:13 140088337995968 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

2018-12-21 13:02:13 140088337995968 [Note] InnoDB: Retrying to lock the first data file

[bogdan.sh]

Doing this seems to solve the problem:

mv /usr/lib/systemd/system/mysqld.service /usr/lib/systemd/system/mysqld.service.bak

mv /usr/lib/systemd/system/mariadb.service /usr/lib/systemd/system/mariadb.service.bak

systemctl daemon-reload

/scripts/restartsrv_mysql

Found here: https://forums.cpanel.net/threads/mu...cesses.572331/

Ignacio