Resolved Mariadb 10.1 on ubuntu 16.04

Kingsley · Oct 11, 2016

Hello;

I am trying to replace MYSQL 5.7 with MARIADB 10.1 on ubuntu 16.04. i tried with @Lloyd_mcse guide for ubuntu 14.04 which can be found here.

The installation was successfully but am unable to access plesk admin area. i got the following error

ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory

Additionally, an exception has occurred while trying to report this error: Zend_Exception
No entry is registered for key 'translate' (Abstract.php:144)

Search for related Knowledge Base articles

EugeneKazakov · Oct 12, 2016

Hello,

The error means Plesk could not connect to the database.
Please, make sure the MariaDB service is running:
# systemctl status mariadb.service

Kingsley · Oct 12, 2016

EugeneKazakov said:
Hello,

The error means Plesk could not connect to the database.
Please, make sure the MariaDB service is running:
# systemctl status mariadb.service

Code:

Oct 12 06:25:04 server4.kraftysprouts.com systemd[1]: Starting MariaDB database server...
Oct 12 06:25:05 server4.kraftysprouts.com mysqld[4280]: 2016-10-12  6:25:05 140233066928384 [Note] /usr/sbin/mysqld (mysqld 10.1.18-MariaDB-1~xenial) starting as proces
Oct 12 06:25:05 server4.kraftysprouts.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Oct 12 06:25:05 server4.kraftysprouts.com systemd[1]: Failed to start MariaDB database server.
Oct 12 06:25:05 server4.kraftysprouts.com systemd[1]: mariadb.service: Unit entered failed state.
Oct 12 06:25:05 server4.kraftysprouts.com systemd[1]: mariadb.service: Failed with result 'exit-code'.

EugeneKazakov · Oct 12, 2016

The installation seems not so successful
Check /var/log/mariadb/mariadb.log
Run /usr/sbin/mysqld to find the problem

Kingsley · Oct 12, 2016

EugeneKazakov said:
The installation seems not so successful
Check /var/log/mariadb/mariadb.log
Run /usr/sbin/mysqld to find the problem

There is no mariadb folder in log.

Code:

root@server4:~# service mysql start
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

after running systemctl status mariadb.service

Code:

root@server4:~# systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: failed (Result: exit-code) since Thu 2016-10-13 04:15:45 UTC; 4min 8s ago
  Process: 11799 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
  Process: 11701 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSR
  Process: 11694 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 11690 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 11799 (code=exited, status=1/FAILURE)

AleksOstapenko · Oct 14, 2016

Hello,

During reproducing this situation we have the same crash of mariadb service on starting. In /var/log/mysql/error.log exists next errors:

Code:

2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: The InnoDB memory heap is disabled
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Using Linux native AIO
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Using SSE crc32 instructions
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Completed initialization of buffer pool
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later,
InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
2016-10-13 10:17:23 140224936802560 [ERROR] Plugin 'InnoDB' init function returned error.
2016-10-13 10:17:23 140224936802560 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-10-13 10:17:23 140224936802560 [Note] Plugin 'FEEDBACK' is disabled.
2016-10-13 10:17:23 140224936802560 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2016-10-13 10:17:23 140224936802560 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-10-13 10:17:23 140224936802560 [ERROR] Aborting

Most likely in your logs - the same error.
At the current moment the situation is such that upgrade from mysql-5.7 to mariadb-10.1 can only be done with help of

rm -rf /var/lib/mysql

command (checked on our test environment). In other words - you need to remove all previous tables
(this should be done before

dpkg --configure -a

and

apt-get install -f

commands), and restore them after upgrade will be finished. Incompatibility issues may be arise during restoring operation - so these steps - at your own risk.
Besides, after upgrade you will likely encounter the problem of invalid mariadb users, so you have to be ready to solve them.

Kingsley · Oct 14, 2016

AleksOstapenko said:

Hello,

During reproducing this situation we have the same crash of mariadb service on starting. In /var/log/mysql/error.log exists next errors:

Code:

2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: The InnoDB memory heap is disabled
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Using Linux native AIO
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Using SSE crc32 instructions
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Completed initialization of buffer pool
2016-10-13 10:17:23 140224936802560 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later,
InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
2016-10-13 10:17:23 140224936802560 [ERROR] Plugin 'InnoDB' init function returned error.
2016-10-13 10:17:23 140224936802560 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-10-13 10:17:23 140224936802560 [Note] Plugin 'FEEDBACK' is disabled.
2016-10-13 10:17:23 140224936802560 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2016-10-13 10:17:23 140224936802560 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-10-13 10:17:23 140224936802560 [ERROR] Aborting

Most likely in your logs - the same error.
At the current moment the situation is such that upgrade from mysql-5.7 to mariadb-10.1 can only be done with help of
command (checked on our test environment). In other words - you need to remove all previous tables
(this should be done before and commands), and restore them after upgrade will be finished. Incompatibility issues may be arise during restoring operation - so these steps - at your own risk.
Besides, after upgrade you will likely encounter the problem of invalid mariadb users, so you have to be ready to solve them.

Hello;

I dont understand. actually its a test server which i am trying out before i will try the setup on a production server.

what problems are you talking about?

urki · Oct 14, 2016

Hello,

consider installing MariaDB before Plesk to avoid such problems, and to keep the installation as clean as possible.

Kingsley · Oct 14, 2016

urki said:
Hello,

consider installing MariaDB before Plesk to avoid such problems, and to keep the installation as clean as possible.

will that work? i tried before (only added mariadb repo) to the server but plesk failed to install

urki · Oct 14, 2016

@Kingsley,

You have to install MariaDB before installing Plesk. Plesk installer will then detect MariaDB and install as usual.

Kingsley · Oct 14, 2016

urki said:
@Kingsley,

You have to install MariaDB before installing Plesk. Plesk installer will then detect MariaDB and install as usual.

Installed.

now testing.

Thanks

Oliver Marugg · Oct 14, 2016

@Kingsley:
I also plan to setup mariadb instead of mysql5.7
How did you installed Mariadb:
a. with Password
b. without password
c. with mysql_secure_installation to secure mariadb?
I amde a terst with password and with mysql_secure_installation but Onyx installed mysql as well (and all crashed becuase it was not a fresh clean ubuntu16 install).
Greets oliver

urki · Oct 14, 2016

@Oliver Marugg,

install MariaDB without a password (hit enter when it prompts you to enter it), and run Plesk installer afterwards.

The installer should then secure MariaDB with the admin password used in Plesk.

Oliver Marugg · Oct 14, 2016

urki said:
@Oliver Marugg,

install MariaDB without a password (hit enter when it prompts you to enter it), and run Plesk installer afterwards.

The installed should then secure MariaDB with the admin password used in Plesk.

Perfect that was the hint I was looking for;-)

Kingsley · Oct 14, 2016

Oliver Marugg said:
@Kingsley:
I also plan to setup mariadb instead of mysql5.7
How did you installed Mariadb:
a. with Password
b. without password
c. with mysql_secure_installation to secure mariadb?
I amde a terst with password and with mysql_secure_installation but Onyx installed mysql as well (and all crashed becuase it was not a fresh clean ubuntu16 install).
Greets oliver

@Oliver Marugg i followed @urki tip of installing it on a new server, however i set a password for it

Kingsley · Oct 14, 2016

urki said:
@Oliver Marugg,

install MariaDB without a password (hit enter when it prompts you to enter it), and run Plesk installer afterwards.

The installed should then secure MariaDB with the admin password used in Plesk.

Woooow really? let me set up my production server

Kingsley · Aug 30, 2017

urki said:
@Oliver Marugg,

install MariaDB without a password (hit enter when it prompts you to enter it), and run Plesk installer afterwards.

The installer should then secure MariaDB with the admin password used in Plesk.

I am having this error Could not find the mysqldump utility with vaultpress backup

Resolved Mariadb 10.1 on ubuntu 16.04

Kingsley

Silver Pleskian

EugeneKazakov

Regular Pleskian

Kingsley

Silver Pleskian

EugeneKazakov

Regular Pleskian

Kingsley

Silver Pleskian

AleksOstapenko

New Pleskian

Kingsley

Silver Pleskian

urki

Basic Pleskian

Kingsley

Silver Pleskian

urki

Basic Pleskian

Kingsley

Silver Pleskian

Oliver Marugg

Basic Pleskian

urki

Basic Pleskian

Oliver Marugg

Basic Pleskian

Kingsley

Silver Pleskian

Kingsley

Silver Pleskian

Kingsley

Silver Pleskian

Similar threads