• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Plesk Error + MariaDB 10.2 installed & Error

Hajime Tanaka

Hajime Tanaka

Regular Pleskian
Code: 
Total                                                                                                                                 9.8 MB/s | 168 MB  00:00:17     
Retrieving key from https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
Importing GPG key 0x1BB943DB:
 Userid     : "MariaDB Package Signing Key <[email protected]>"
 Fingerprint: 1993 69e5 404b d5fc 7d2f e43b cbcb 082a 1bb9 43db
 From       : https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : MariaDB-common-10.2.11-1.el7.centos.x86_64                                                                                                         1/9 
warning: /etc/my.cnf created as /etc/my.cnf.rpmnew
  Installing : MariaDB-compat-10.2.11-1.el7.centos.x86_64                                                                                                         2/9 
  Installing : MariaDB-client-10.2.11-1.el7.centos.x86_64                                                                                                         3/9 
  Installing : boost-program-options-1.53.0-27.el7.x86_64                                                                                                         4/9 
  Installing : galera-25.3.22-1.rhel7.el7.centos.x86_64                                                                                                           5/9 
  Installing : MariaDB-server-10.2.11-1.el7.centos.x86_64                                                                                                         6/9 
Failed to resolve typeattributeset statement at /etc/selinux/targeted/tmp/modules/400/mariadb/cil:1
/usr/sbin/semodule:  Failed!
  Erasing    : 1:mariadb-server-5.5.56-2.el7.x86_64                                                                                                               7/9 
warning: /var/log/mariadb/mariadb.log saved as /var/log/mariadb/mariadb.log.rpmsave
  Erasing    : 1:mariadb-5.5.56-2.el7.x86_64                                                                                                                      8/9 
  Erasing    : 1:mariadb-libs-5.5.56-2.el7.x86_64                                                                                                                 9/9 
  Verifying  : MariaDB-server-10.2.11-1.el7.centos.x86_64                                                                                                         1/9 
  Verifying  : MariaDB-compat-10.2.11-1.el7.centos.x86_64                                                                                                         2/9 
  Verifying  : MariaDB-client-10.2.11-1.el7.centos.x86_64                                                                                                         3/9 
  Verifying  : MariaDB-common-10.2.11-1.el7.centos.x86_64                                                                                                         4/9 
  Verifying  : galera-25.3.22-1.rhel7.el7.centos.x86_64                                                                                                           5/9 
  Verifying  : boost-program-options-1.53.0-27.el7.x86_64                                                                                                         6/9 
  Verifying  : 1:mariadb-libs-5.5.56-2.el7.x86_64                                                                                                                 7/9 
  Verifying  : 1:mariadb-server-5.5.56-2.el7.x86_64                                                                                                               8/9 
  Verifying  : 1:mariadb-5.5.56-2.el7.x86_64                                                                                                                      9/9 

Installed:
  MariaDB-client.x86_64 0:10.2.11-1.el7.centos           MariaDB-compat.x86_64 0:10.2.11-1.el7.centos           MariaDB-server.x86_64 0:10.2.11-1.el7.centos         

Dependency Installed:
  MariaDB-common.x86_64 0:10.2.11-1.el7.centos           boost-program-options.x86_64 0:1.53.0-27.el7           galera.x86_64 0:25.3.22-1.rhel7.el7.centos         

Replaced:
  mariadb.x86_64 1:5.5.56-2.el7                      mariadb-libs.x86_64 1:5.5.56-2.el7                      mariadb-server.x86_64 1:5.5.56-2.el7                     

Complete!
[root@xxxxxx~]#

Last error,
Code: 
Failed to resolve typeattributeset statement at /etc/selinux/targeted/tmp/modules/400/mariadb/cil:1
/usr/sbin/semodule:  Failed!
  Erasing    : 1:mariadb-server-5.5.56-2.el7.x86_64                                                                                                               7/9 
warning: /var/log/mariadb/mariadb.log saved as /var/log/mariadb/mariadb.log.rpmsave
  Erasing    : 1:mariadb-5.5.56-2.el7.x86_64                                                                                                                      8/9 
  Erasing    : 1:mariadb-libs-5.5.56-2.el7.x86_64                                                                                                                 9/9

If was installed and fixed isn't?

I followed this tutorial Plesk for Installation-MariaDB: How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.0/10.1/10.2 on Linux
 
I got the error on Plesk Panel again.

Code: 
ERROR: Plesk\Exception\Database: DB query failed: SQLSTATE[HY000]: General error: 1 Can't create/write to file '/var/tmp/#sql_270d_0.MAI' (Errcode: 2), query was: DESCRIBE `sessions`

Additionally, an exception has occurred while trying to report this error: Zend_Exception
No entry is registered for key &#039;translate&#039; (Mysql.php:53)
 
I also made this error myself on a new server install and had this issue. Easiest thing to do was reinstall CentOS 7.4 and upgrade MariaDB to 10.1 using the instructions on the MariaDB website. No issues and fast on Plesk 17.5

Attempting to downgrade could throw errors in the future due to major differences between 10.1 and 10.2
 
themew said:
I also made this error myself on a new server install and had this issue. Easiest thing to do was reinstall CentOS 7.4 and upgrade MariaDB to 10.1 using the instructions on the MariaDB website. No issues and fast on Plesk 17.5

Attempting to downgrade could throw errors in the future due to major differences between 10.1 and 10.2
Click to expand...
Hmmm, I restart for MariaDB was failed.
Code: 
"systemctl status mariadb.service" and "journalctl -xe" for details.

/var/log/mariadb/mariadb.log
Code: 
2017-12-16 21:42:15 139909625903232 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2017-12-16 21:42:15 139909625903232 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-16 21:42:16 139909625903232 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2017-12-16 21:42:16 139909625903232 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-16 21:42:16 139909625903232 [Note] InnoDB: Unable to open the first data file
2017-12-16 21:42:16 139909625903232 [ERROR] InnoDB: Operating system error number 11 in a file operation.
2017-12-16 21:42:16 139909625903232 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable'
2017-12-16 21:42:16 139909625903232 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-12-16 21:42:16 139909625903232 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2017-12-16 21:42:16 139909625903232 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-12-16 21:42:16 139909625903232 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2017-12-16 21:42:16 139909625903232 [Note] InnoDB: Starting shutdown...
2017-12-16 21:42:16 139909625903232 [ERROR] Plugin 'InnoDB' init function returned error.
2017-12-16 21:42:16 139909625903232 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-12-16 21:42:16 139909625903232 [Note] Plugin 'FEEDBACK' is disabled.
2017-12-16 21:42:16 139909625903232 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-12-16 21:42:16 139909625903232 [ERROR] Aborting

[root@xxxx ~]# systemctl status mariadb.service
Code: 
● 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 Sat 2017-12-16 21:39:25 UTC; 24min ago
 Main PID: 12323 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"
   CGroup: /system.slice/mariadb.service
           ├─9776 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
           └─9997 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-f...

Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [Note] InnoDB: Some operating system error numbers are desc...des.html
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] InnoDB: Cannot open datafile './ibdata1'
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] InnoDB: Could not open or create the system tablespace. If ...
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] InnoDB: Plugin initialization aborted with error Ca...n a file
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [Note] InnoDB: Starting shutdown...
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] Plugin 'InnoDB' init function returned error.
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [Note] Plugin 'FEEDBACK' is disabled.
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] Unknown/unsupported storage engine: InnoDB
Dec 16 21:39:25 unknown.com mysqld[12323]: 2017-12-16 21:39:25 140701467412608 [ERROR] Aborting
Hint: Some lines were ellipsized, use -l to show in full.
 
Samet Chan said:
That is tutorial for Ubuntu only. I'm on CentOS 7.4
Click to expand...

It's exactly the same process on Centos than on Ubuntu.
Replace MariaDB 10.2 repo by MariaDB 10.1 repository.

Code: 
nano /etc/yum.repos.d/MariaDB.repo

Should currently look like :

Code: 
# MariaDB 10.2 CentOS repository list - created 2017-12-17 13:44 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.2/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

Replace it with :
Code: 
# MariaDB 10.1 CentOS repository list - created 2017-12-17 13:45 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.1/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

Then follow the steps of the guide
 
virtubox said:
It's exactly the same process on Centos than on Ubuntu.
Replace MariaDB 10.2 repo by MariaDB 10.1 repository.

Code: 
nano /etc/yum.repos.d/MariaDB.repo

Should currently look like :

Code: 
# MariaDB 10.2 CentOS repository list - created 2017-12-17 13:44 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.2/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

Replace it with :
Code: 
# MariaDB 10.1 CentOS repository list - created 2017-12-17 13:45 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.1/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

Then follow the steps of the guide
Click to expand...
I can confirm edit that file. Then re-install for yum MariaDB said it's already latest version so. I asked my friend to restored my Plesk panel and server back to the original. It's should work.

We don't know if this was known bugs.
 
Samet Chan said:
I can confirm edit that file. Then re-install for yum MariaDB said it's already latest version so. I asked my friend to restored my Plesk panel and server back to the original. It's should work.

We don't know if this was known bugs.
Click to expand...

You have to backup the folder /var/lib/mysql , then to totally remove MariaDB.
After that, update yum repo to apply the change in /etc/yum.repos.d/MariaDB.repo, and reinstall MariaDB 10.1.

The last step is to restore the previous database and to apply the MariaDB downgrade.

This is not a bug, you can 't downgrade MySQL or MariaDB without following those steps, and Plesk software support list is :
Database servers and tools:

  • MySQL 5.1–5.7
  • MySQL community edition 5.5, 5.6, 5.7
  • PostgreSQL 8.4–9.5
  • MariaDB 5.5, 10.0, 10.1
Click to expand...
 
virtubox said:
You have to backup the folder /var/lib/mysql , then to totally remove MariaDB.
After that, update yum repo to apply the change in /etc/yum.repos.d/MariaDB.repo, and reinstall MariaDB 10.1.

The last step is to restore the previous database and to apply the MariaDB downgrade.

This is not a bug, you can 't downgrade MySQL or MariaDB without following those steps, and Plesk software support list is :
Click to expand...
Ah, I'm afraid. Can you give me as a guide to installation MariaDB safe for the plesk panel?

Something if safe was this How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.0/10.1/10.2 on Linux ?

As I can see Plesk support said supported upgrade to 10.2 huh?

"MariaDB 5.5 to 10.0/10.1/10.2 on Linux"
 
Samet Chan said:
Ah, I'm afraid. Can you give me as a guide to installation MariaDB safe for the plesk panel?

Something if safe was this How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.0/10.1/10.2 on Linux ?

As I can see Plesk support said supported upgrade to 10.2 huh?

"MariaDB 5.5 to 10.0/10.1/10.2 on Linux"
Click to expand...

You are right, there is maybe an error in the kb title.
The easiest to use the MariaDB release of your choice is to install it before installing Plesk :

Code: 
 #add MariaDB 10.1 repository
curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup |    sudo bash -s -- --mariadb-server-version=10.1 --skip-maxscale

#  install MariaDB (do not set any root password during MariaDB installation)
yum update
yum install mariadb-server

# install Plesk
wget https://installer.plesk.com/plesk-installer
chmod +x
./plesk-installer ./plesk-installer --all-versions[code]
 
virtubox said:
The easiest to use the MariaDB release of your choice is to install it before installing Plesk
Click to expand...

Exactly, plesk detects during the installation whether a database server has already been installed and does not try to install mysql.
 
You must log in or register to reply here.

Similar threads

J
Issue Update MariaDB 5.5 to 10.5 failed, system crash
Replies
1
Views
697
JuanCar
J
Dork
Issue Database Mangement problem
Replies
6
Views
1K
JuanCar
J
P
Issue Upgrade Mariadb 10.3 to 10.6 completes but trying to start MariaDB fails with error "systemctl status mariadb.service" and "journalctl -xe"
Replies
12
Views
513
PeterK900
P
Daerik
Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)
Replies
6
Views
693
Daerik
Daerik
davidds64
Question How to upgrade MariaDB to latest version with Plesk Obsidian on Alma Linux 9
Replies
5
Views
1K
davidds64
davidds64
Back
Top