• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Plesk Exception Database after upgrade Maria DB

domox

New Pleskian
Hi I'm having an issue after i upgrade the Maria DB database, the sites i can see are still working but i can't access to plesk admin.

Screenshot:
otro error plesk.PNG
 
@UFHH01, @IgorG can you help me with this. It is urgent to me solve this. I have tray it restarting the psa but without luck. That happend after i upgrade the MariaDB to my plesk Onyx.
 
Maybe this could be part of the problem after the update:

After runing this command:#systemctl status mariadb.service

I got this:
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [Note] InnoDB: Check that you do not already have anot... files.
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [Note] InnoDB: Unable to open the first data file
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 7f58f8eae880 InnoDB: Operating system error number 11 in a file operation.
Nov 02 14:38:29 sd-102175 mysqld[28734]: InnoDB: Error number 11 means 'Resource temporarily unavailable'.
Nov 02 14:38:29 sd-102175 mysqld[28734]: InnoDB: Some operating system error numbers are described at
Nov 02 14:38:29 sd-102175 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Nov 02 14:38:29 sd-102175 systemd[1]: Failed to start MariaDB database server.
Nov 02 14:38:29 sd-102175 systemd[1]: Unit mariadb.service entered failed state.
Nov 02 14:38:29 sd-102175 systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

But i dont know how to solve it and other thing is all the sites are up.
 
this is the complete error log:

[root@xxxxxxxxxxx /]# systemctl status mariadb.service -l
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Wed 2016-11-02 14:38:29 AST; 7min ago
Process: 28734 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 28699 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 28697 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 28734 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Memory: 334.6M
CGroup: /system.slice/mariadb.service
├─ 977 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─1445 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock

Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [Note] InnoDB: Unable to open the first data file
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 7f58f8eae880 InnoDB: Operating system error number 11 in a file operation.
Nov 02 14:38:29 sd-102175 mysqld[28734]: InnoDB: Error number 11 means 'Resource temporarily unavailable'.
Nov 02 14:38:29 sd-102175 mysqld[28734]: InnoDB: Some operating system error numbers are described at
Nov 02 14:38:29 sd-102175 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Nov 02 14:38:29 sd-102175 systemd[1]: Failed to start MariaDB database server.
Nov 02 14:38:29 sd-102175 systemd[1]: Unit mariadb.service entered failed state.
Nov 02 14:38:29 sd-102175 systemd[1]: mariadb.service failed.
 
Another thing is if i run this command: mysql -V
the result is:
mysql Ver 15.1 Distrib 10.1.18-MariaDB, for Linux (x86_64) using readline 5.1
 
Hello,

This errors may be caused by several instances of mysql process running simultaneously:
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
Nov 02 14:38:29 sd-102175 mysqld[28734]: 2016-11-02 14:38:29 140020109994112 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

You need to stop mariadb service with systemctl, and then stop other instances with kill -TERM, and then start mariadb again
 
Thanks, it works:
# systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf, protecthome.conf
Active: active (running) since Thu 2016-11-03 09:14:16 AST; 1min 11s ago
Process: 22505 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 22442 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 22438 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 22477 (mysqld)
Status: "Taking your SQL requests now..."
Memory: 196.4M
CGroup: /system.slice/mariadb.service
└─22477 /usr/sbin/mysqld

Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139723792185088 [Note] InnoDB: Dumping buffer pool(s) not yet started
Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139724532459648 [Note] Plugin 'FEEDBACK' is disabled.
Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139724532459648 [Note] Server socket created on IP: '::'.
Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139724532459648 [Warning] 'proxies_priv' entry '@% root@sd-102175' ignored in -...lve mode.
Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139724532459648 [ERROR] Missing system table mysql.roles_mapping; please run my...create it
Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139724532034304 [Warning] Failed to load slave replication state from table mys...n't exist
Nov 03 09:14:16 sd-102175 mysqld[22477]: 2016-11-03 9:14:16 139724532459648 [Note] /usr/sbin/mysqld: ready for connections.
Nov 03 09:14:16 sd-102175 mysqld[22477]: Version: '10.1.18-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
Nov 03 09:14:16 sd-102175 systemd[1]: Started MariaDB database server.
Nov 03 09:14:47 sd-102175 mysqld[22477]: 2016-11-03 09:14:47 7f1427148b00 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
Hint: Some lines were ellipsized, use -l to show in full.
 
I had the same issue -- I upgraded mysql to mariadb, but at startup they BOTH want to start up, the mysqld.service and mariadb.service!
 
Back
Top