/ Register

Want more timely Centmin Mod News Updates?
Become a Member

Feedback Switching to EL8 AppStream module MariaDB 10.3 Testing

Discussion in 'AlmaLinux 8 & Rocky Linux 8 Beta Testing' started by eva2000, Sep 27, 2022.

Tags:
Previous Thread Next Thread
Loading...
  1. Sep 27, 2022 #1
    eva2000

    eva2000 Administrator Staff Member

    54,547
    12,221
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,790
    Local Time:
    5:05 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    I've updated 130.00beta01 to switch EL8 installations of Centmin Mod to native AppStream module MariaDB 10.3. So folks can test this on fresh EL8 installs of AlmaLinux 8 or Rocky Linux 8. Also worth testing is the centmin.sh menu option 11 submenu upgrades for MariaDB 10.3 to 10.4, 10.5 and 10.6 https://community.centminmod.com/threads/mariadb-10-4-upgrades-testing.23277/.

    So as of September 27, 2022:
    1. Centmin Mod EL8 installs will default to GCC 11.2 for compilation routines instead of the current Centmin Mod 130.00beta01 default for GCC 10.2 and EL8 system default GCC 8.5
    2. Centmin Mod EL8 installs will default to PHP 8.0.x installation (PHP-FPM)
    3. Centmin Mod EL8 installs as of September 27, 2022, onwards (in private beta testing), will switch from the official MariaDB YUM repo provided MariaDB 10.3 which has support ending May 2023 to the native EL8 Appstream module provided MariaDB 10.3 version which has extended support until May 2029
    Note that native EL8 Appstream MariaDB 10.3's YUM package names are different from the official MariaDB YUM repo's YUM package names.

    EL8 Appstream MariaDB 10.3's YUM package name
    Code (Text):
    rpm -qa mariadb*
mariadb-server-utils-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64
mariadb-connector-c-3.1.11-2.el8_3.x86_64
mariadb-errmsg-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64
mariadb-server-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64
mariadb-backup-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64
mariadb-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64
mariadb-gssapi-server-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64
mariadb-connector-c-config-3.1.11-2.el8_3.noarch
mariadb-common-10.3.35-1.module_el8.6.0+3265+230ed96b.x86_64

    official MariaDB YUM repo's YUM package names
    Code (Text):
    rpm -qa MariaDB*
MariaDB-devel-10.3.36-1.el8.x86_64
MariaDB-shared-10.3.36-1.el8.x86_64
MariaDB-server-10.3.36-1.el8.x86_64
MariaDB-client-10.3.36-1.el8.x86_64
MariaDB-common-10.3.36-1.el8.x86_64


    Folks can provide feedback or bug reports specifically for this in this thread :)
     
  2. Sep 27, 2022 #2
    buik

    buik “The best traveler is one without a camera.”

    2,026
    524
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,674
    Local Time:
    8:05 AM
    I briefly ran a scenario simulation (which will no doubt happen) where an end user is going to upgrade Red Hat 10.3 to Mariadb 10.4. Result regretfully failed.

    Code:
    systemctl start mariadb.service
Job for mariadb.service failed because the control process exited with error cod                                                                                                 e.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

## !! mysql failed to start properly !! ##
journalctl -xn
-- Logs begin at Tue 2022-09-27 07:51:23 UTC, end at Tue 2022-09-27 08:46:41 UTC. --
Sep 27 08:46:33 rocky-4gb-fsn1-1 postfix/pickup[497493]: 7BE2A5FC48: uid=0 from=<root>
Sep 27 08:46:33 rocky-4gb-fsn1-1 postfix/cleanup[509742]: 7BE2A5FC48: message-id=<20220927084633.7BE2A5FC48@rocky-4gb-fsn1-1.localdomain>
Sep 27 08:46:33 rocky-4gb-fsn1-1 postfix/qmgr[497494]: 7BE2A5FC48: from=<root@rocky-4gb-fsn1-1.localdomain>, size=1493, nrcpt=1 (queue active)
Sep 27 08:46:33 rocky-4gb-fsn1-1 postfix/local[509744]: 7BE2A5FC48: to=<root@rocky-4gb-fsn1-1.localdomain>, orig_to=<root>, relay=local, delay=0.05, delays=0.03/0.01/0/0, dsn=2.0.0, status=sent (delivered to mailbox)
Sep 27 08:46:33 rocky-4gb-fsn1-1 postfix/qmgr[497494]: 7BE2A5FC48: removed
Sep 27 08:46:41 rocky-4gb-fsn1-1 systemd[1]: Starting MariaDB 10.4.26 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has begun starting up.
Sep 27 08:46:41 rocky-4gb-fsn1-1 mysql-prepare-db-dir-modify[509747]: /usr/libexec/mysql-prepare-db-dir-modify: line 6: /usr/libexec/mysql-scripts-common: No such file or directory
Sep 27 08:46:41 rocky-4gb-fsn1-1 systemd[1]: mariadb.service: Control process exited, code=exited status=1
Sep 27 08:46:41 rocky-4gb-fsn1-1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Sep 27 08:46:41 rocky-4gb-fsn1-1 systemd[1]: Failed to start MariaDB 10.4.26 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has failed.
--
-- The result is failed.

tail -50 /var/log/mysqld.log
2022-09-27  8:04:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-09-27  8:04:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-09-27  8:04:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-09-27  8:04:47 0 [Note] InnoDB: Waiting for purge to start
2022-09-27  8:04:47 0 [Note] InnoDB: 10.3.35 started; log sequence number 1625612; transaction id 20
2022-09-27  8:04:47 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-09-27  8:04:47 0 [Note] InnoDB: Buffer pool(s) load completed at 220927  8:04:47
2022-09-27  8:04:47 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-09-27  8:04:47 0 [Note] Server socket created on IP: '::'.
2022-09-27  8:04:47 0 [Note] /usr/libexec/mysqld: ready for connections.
Version: '10.3.35-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2022-09-27  8:17:25 0 [Note] /usr/libexec/mysqld (initiated by: unknown): Normal shutdown
2022-09-27  8:17:25 0 [Note] Event Scheduler: Purging the queue. 0 events
2022-09-27  8:17:25 0 [Note] InnoDB: FTS optimize thread exiting.
2022-09-27  8:17:25 0 [Note] InnoDB: Starting shutdown...
2022-09-27  8:17:25 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2022-09-27  8:17:25 0 [Note] InnoDB: Buffer pool(s) dump completed at 220927  8:17:25
2022-09-27  8:17:27 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-09-27  8:17:27 0 [Note] InnoDB: Shutdown completed; log sequence number 1625621; transaction id 21
2022-09-27  8:17:27 0 [Note] /usr/libexec/mysqld: Shutdown complete

2022-09-27  8:17:27 0 [Note] InnoDB: Using Linux native AIO
2022-09-27  8:17:27 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-09-27  8:17:27 0 [Note] InnoDB: Uses event mutexes
2022-09-27  8:17:27 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-09-27  8:17:27 0 [Note] InnoDB: Number of pools: 1
2022-09-27  8:17:27 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-09-27  8:17:27 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2022-09-27  8:17:27 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-27  8:17:27 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-09-27  8:17:27 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-09-27  8:17:27 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-09-27  8:17:27 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-09-27  8:17:27 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-09-27  8:17:27 0 [Note] InnoDB: Waiting for purge to start
2022-09-27  8:17:27 0 [Note] InnoDB: 10.3.35 started; log sequence number 1625621; transaction id 20
2022-09-27  8:17:27 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-09-27  8:17:27 0 [Note] InnoDB: Buffer pool(s) load completed at 220927  8:17:27
2022-09-27  8:17:27 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-09-27  8:17:27 0 [Note] Server socket created on IP: '::'.
2022-09-27  8:17:27 0 [Note] /usr/libexec/mysqld: ready for connections.
Version: '10.3.35-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2022-09-27  8:45:23 0 [Note] /usr/libexec/mysqld (initiated by: unknown): Normal shutdown
2022-09-27  8:45:23 0 [Note] Event Scheduler: Purging the queue. 0 events
2022-09-27  8:45:23 0 [Note] InnoDB: FTS optimize thread exiting.
2022-09-27  8:45:23 0 [Note] InnoDB: Starting shutdown...
2022-09-27  8:45:25 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-09-27  8:45:25 0 [Note] InnoDB: Shutdown completed; log sequence number 1625630; transaction id 21
2022-09-27  8:45:25 0 [Note] /usr/libexec/mysqld: Shutdown complete


possible errors / warnings

possible unknown or incompatible /etc/my.cnf set options below
maybe need to comment out or remove these in /etc/my.cnf

attempting auto commenting out of invalid options
systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

total 331M
drwx------. 2 mysql mysql 4.0K Sep 27 08:04 mysql
drwx------. 2 mysql mysql 4.0K Sep 27 08:04 performance_schema
-rw-rw----. 1 mysql mysql   16 Sep 27 08:04 mysql_upgrade_info
-rw-rw----. 1 mysql mysql    0 Sep 27 08:04 multi-master.info
-rw-rw----. 1 mysql mysql 128M Sep 27 08:04 ib_logfile1.bak
drwxr-xr-x. 2 mysql mysql 4.0K Sep 27 08:04 cmsetiofiotest
-rw-rw----. 1 mysql mysql  976 Sep 27 08:17 ib_buffer_pool
-rw-rw----. 1 mysql mysql   52 Sep 27 08:45 aria_log_control
-rw-rw----. 1 mysql mysql  16K Sep 27 08:45 aria_log.00000001
-rw-rw----. 1 mysql mysql 128M Sep 27 08:45 ib_logfile0.bak
-rw-rw----. 1 mysql mysql  74M Sep 27 08:45 ibdata1
mysql_upgrade --verbose
Looking for 'mysql' as: mysql
Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
FATAL ERROR: Upgrade failed
------------------------------------------------
Installing MariaDB 10 plugins
------------------------------------------------
mysql -e "INSTALL SONAME 'metadata_lock_info';"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
mysql -e "INSTALL SONAME 'query_cache_info';"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
mysql -e "INSTALL SONAME 'query_response_time';"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
mysql -t -e "SELECT * FROM mysql.plugin;"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
mysql -t -e "SHOW PLUGINS;"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
mysql -t -e "SHOW ENGINES;"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
systemctl enable mariadb.service
Created symlink /etc/systemd/system/mysql.service → /usr/lib/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/mysqld.service → /usr/lib/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/multi-user.target.wants/mariadb.service → /usr/lib/systemd/system/mariadb.service.


mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
     
    Last edited: Sep 27, 2022
  3. Sep 27, 2022 #3
    eva2000

    eva2000 Administrator Staff Member

    54,547
    12,221
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,790
    Local Time:
    5:05 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Via centmin.sh menu option 11 submenu option 8 to update from EL8 Appstream MariaDB 10.3 to official MariaDB 10.3 YUM repo? or you mean you manually made the switch outside of centmin.sh menu option 11 submenu option 8?

    Make sure you're doing this on a fresh Centmin Mod 130.00beta01 install as of a few hours ago released and using centmin.sh menu option 11 submenu option 8
     
  4. Sep 27, 2022 #4
    buik

    buik “The best traveler is one without a camera.”

    2,026
    524
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,674
    Local Time:
    8:05 AM
    Fresh fish installation and upgrade Red Hat Appstream MariaDB 10.3 to Mariadb 10.4 YUM via centmin.
     
  5. Sep 27, 2022 #5
    eva2000

    eva2000 Administrator Staff Member

    54,547
    12,221
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,790
    Local Time:
    5:05 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    What output do you get for
    Code (Text):
    systemctl status mariadb --no-pager

    and for
    Code (Text):
    journalctl -u mariadb --no-pager

    I will have to test on Rocky Linux 8.6 as AlmaLinux 8.6 worked fine for centmin.sh menu option 11 submenu options 8, 9 and 10 to update to MariaDB 10.4, 10.5 and 10.6
     
  6. Sep 27, 2022 #6
    buik

    buik “The best traveler is one without a camera.”

    2,026
    524
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,674
    Local Time:
    8:05 AM
    Hmm logs are written about:

    "possible unknown or incompatible /etc/my.cnf set options below
    maybe need to comment out or remove these in /etc/my.cnf"

    Code:
    [09:36][root@rocky-4gb-fsn1-1 ~]# systemctl status mariadb --no-pager
● mariadb.service - MariaDB 10.4.26 database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor pres                                                                                                 et: disabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf, mysql-prepare-db-dir-modify.con                                                                                                 f, notifyaccess.conf, openfileslimit.conf, protecthome.conf
   Active: failed (Result: exit-code) since Tue 2022-09-27 09:20:14 UTC; 16min a                                                                                                 go
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 901 ExecStartPre=/usr/libexec/mysql-prepare-db-dir-modify mariadb.ser                                                                                                 vice (code=exited, status=1/FAILURE)

Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: Starting MariaDB 10.4.26 databa…...
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: mariadb.service: Control proces…s=1
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: mariadb.service: Failed with re…e'.
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: Failed to start MariaDB 10.4.26…er.
Hint: Some lines were ellipsized, use -l to show in full.
    Code:
    -- Logs begin at Tue 2022-09-27 09:20:11 UTC, end at Tue 2022-09-27 09:36:36 UTC. --
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: Starting MariaDB 10.4.26 database server...
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: mariadb.service: Control process exited, code=exited status=1
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Sep 27 09:20:14 rocky-4gb-fsn1-1 systemd[1]: Failed to start MariaDB 10.4.26 database server.
     
  7. Sep 27, 2022 #7
    eva2000

    eva2000 Administrator Staff Member

    54,547
    12,221
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,790
    Local Time:
    5:05 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Oh I see this in your previous journalctl -xe output. The /usr/libexec/mysql-prepare-db-dir-modify is the modified version of EL8 Appstream's version to remove the confusing message I mentioned at https://community.centminmod.com/th...iadb-10-3-x-for-el8-install.23274/#post-94582

    But I don't create that file there, only at /etc/systemd/system/mariadb.service.d/mysql-prepare-db-dir-modify.conf
    Code (Text):
    ls -lah /etc/systemd/system/mariadb.service.d
total 20K
drwxr-xr-x.  2 root root  122 Sep 27 08:06 .
drwxr-xr-x. 17 root root 4.0K Sep 27 08:15 ..
-rw-r--r--.  1 root root   81 Sep 27 08:06 mysql-prepare-db-dir-modify.conf
-rw-r--r--.  1 root root   27 Sep 27 08:06 notifyaccess.conf
-rw-r--r--.  1 root root   29 Sep 27 08:06 openfileslimit.conf
-rw-r--r--.  1 root root   48 Sep 27 08:06 protecthome.conf


     
  8. Sep 27, 2022 #8
    eva2000

    eva2000 Administrator Staff Member

    54,547
    12,221
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,790
    Local Time:
    5:05 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Oh interesting
    Code (Text):
    cat /etc/systemd/system/mariadb.service.d/mysql-prepare-db-dir-modify.conf
[Service]
ExecStartPre=
ExecStartPre=/usr/libexec/mysql-prepare-db-dir-modify %n

    I did create a modified file at /usr/libexec/mysql-prepare-db-dir-modify using copy of /usr/libexec/mysql-prepare-db-dir
    line 6
    Code (Text):
    cat -n /usr/libexec/mysql-prepare-db-dir-modify
     1  #!/bin/sh
     2
     3  # This script creates the mysql data directory during first service start.
     4  # In subsequent starts, it does nothing much.
     5
     6  source "`dirname ${BASH_SOURCE[0]}`/mysql-scripts-common"
     7

    direct debug run of the modified script for line 6 reveals
    Code (Text):
    bash -x /usr/libexec/mysql-prepare-db-dir-modify
++ dirname /usr/libexec/mysql-prepare-db-dir-modify
+ source /usr/libexec/mysql-scripts-common

    sourcing /usr/libexec/mysql-scripts-common
    Code (Text):
    ls -lah /usr/libexec/mysql-scripts-common
-rw-r--r--. 1 root root 2.6K Sep 13 17:17 /usr/libexec/mysql-scripts-common


    edit: oh i think I see now, updating to MariaDB 10.4+ I should remove /etc/systemd/system/mariadb.service.d/mysql-prepare-db-dir-modify.conf

    if you remove it and restart MariaDB does it start
    Code (Text):
    rm -f /etc/systemd/system/mariadb.service.d/mysql-prepare-db-dir-modify.conf
systemctl daemon-reload 
systemctl restart mariadb
     
  9. Sep 27, 2022 #9
    buik

    buik “The best traveler is one without a camera.”

    2,026
    524
    113
    Apr 29, 2016
    Flanders
    Ratings:
    +1,674
    Local Time:
    8:05 AM
    Yup. You see that more often that certain programs have left overs after uninstallation and switching the same product from vendor to another one. Good thing you found the problem.
     
  10. Sep 27, 2022 #10
    eva2000

    eva2000 Administrator Staff Member

    54,547
    12,221
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,790
    Local Time:
    5:05 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Yup thanks for the bug report - fixed in latest 130.00beta01 update - so run cmupdate :)
     
Previous Thread Next Thread
Loading...

.