[SOLVED] MariaDB version 10.5.4 changes

teoberi · 06-25-2020, 01:29 AM

I think we have a problem with the startup script for MariaDB.
https://mariadb.com/kb/en/mysqld_safe/
https://mariadb.com/kb/en/mysqlserver/
If I start with the rc.mysqld script I can no longer stop the service.

Code:

/etc/rc.d/rc.mysqld start

Quote:

200625 09:18:10 mysqld_safe Logging to '/var/lib/mysql/mail.err'.
200625 09:18:10 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql

Code:

/etc/rc.d/rc.mysqld stop

Quote:

mysqld: no process found
WARNING: Gave up waiting for mysqld to exit!

If I use:

Code:

/usr/share/mysql/mysql.server start

Quote:

Starting MariaDB.200625 09:24:01 mysqld_safe Logging to '/var/lib/mysql/mail.err'.
200625 09:24:01 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql
SUCCESS!

Code:

/usr/share/mysql/mysql.server stop

Quote:

Shutting down MariaDB.. SUCCESS!

Again about systemd!

And that's not all!
From the log:

Quote:

2020-06-25 9:37:39 0 [ERROR] mariadbd: Can't open shared library 'ha_s3.so' (errno: 1, Loading of alpha plugin S3 is prohibited by --plugin-maturity=gamma)
2020-06-25 9:37:39 0 [ERROR] Couldn't load plugins from 'ha_s3.so'.

3rensho · 06-25-2020, 01:55 AM

Tried it and see the same thing that you report.

Labinnah · 06-25-2020, 02:47 AM

I can confirm problem, but solution is easy.
Mariadb daemon has no longer name "mysqld" only "mariadbd". Change ~61 line in /etc/rc.d/rc.mysql from "killall mysqld" to "killall mariadbd", or apply this patch:

Code:

--- rc.mysqld<->2020-06-25 09:44:36.063446186 +0200
+++ rc.mysqld.new<----->2020-06-25 09:44:44.262445625 +0200
@@ -58,7 +58,7 @@
 mysqld_stop() {
   # If there is no PID file, ignore this request...
   if [ -r /var/run/mysql/mysql.pid ]; then
-    killall mysqld
+    killall mariadbd
     # Wait at least one minute for it to exit, as we don't know how big the DB is...
     for second in 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 \
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 60 ; do

teoberi · 06-25-2020, 03:19 AM

Quote:

Originally Posted by Labinnah

I can confirm problem, but solution is easy.
Mariadb daemon has no longer name "mysqld" only "mariadbd". Change ~61 line in /etc/rc.d/rc.mysql from "killall mysqld" to "killall mariadbd", or apply this patch:
...

I do not agree with your solution, although it works.

Code:

/etc/rc.d/rc.mysqld --help

Quote:

usage /etc/rc.d/rc.mysqld start|stop|restart

Code:

/usr/share/mysql/mysql.server --help

Quote:

Usage: mysql.server {start|stop|restart|reload|force-reload|status|configtest|bootstrap} [ MariaDB server options ]

I think we should use the mysql.server script.

There is already a patch proposal to avoid terminating other mysql instances at:
https://www.linuxquestions.org/quest...ml#post6137742

I also recommend the following when migrating to a major version for MariaDB:
1. backup to databases;
2. uninstall previous version;
3. cleaning the remaining folders/files;
4. install the new version;
5. configuration
mysql_install_db --user = mysql
/usr/bin/mysql_secure_installation
6. test
mysql -u root -p

teoberi · 06-29-2020, 05:09 AM

And that's not all!
From the log:

Quote:

2020-06-25 9:37:39 0 [ERROR] mariadbd: Can't open shared library 'ha_s3.so' (errno: 1, Loading of alpha plugin S3 is prohibited by --plugin-maturity=gamma)
2020-06-25 9:37:39 0 [ERROR] Couldn't load plugins from 'ha_s3.so'.

The problem is known by developers.
https://github.com/MariaDB/server/pull/1611

Labinnah · 06-29-2020, 05:22 AM

See https://mariadb.com/kb/en/using-the-s3-storage-engine/

Its probably good that it not load...

To get rid of it hash in "plugin-load-add=ha_s3" line /etc/my.cnf.d/s3.cnf

teoberi · 06-29-2020, 05:39 AM

So MariaDB 10.5.4, comment on that line in /etc/my.cnf.d/s3.cnf and change the daemon name from "mysqld" to "mariadbd" in rc.mysqld?
Or maybe we stick to mariadb-10.4.13-x86_64-3 for now?

Labinnah · 06-29-2020, 05:46 AM

Quote:

Originally Posted by teoberi

Or maybe we stick to mariadb-10.4.13-x86_64-3 for now?

Why?

Change daemon name is Slackware issue and error with not loading "alpha quality" plugin is IMHO harmless.

teoberi · 06-29-2020, 05:59 AM

Quote:

Originally Posted by Labinnah

Why?

Change daemon name is Slackware issue and error with not loading "alpha quality" plugin is IMHO harmless.

This time I'm just asking, it's not up to me.
I installed the new version on the test server but not yet on the production one.