are there any known issues running MariaDB on RockyLinux 8.4?
hello -
i have recently installed MariaDB 10:5.11 on RL 8.4 and seem to run into some pretty mysterious 'occasional' errors.
for instance, the last couple of days I see messages like this:
ERROR 1053 (08S01) at line 110: Server shutdown in progress
ERROR 2006 (HY000) at line 281: MySQL server has gone away ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
here are the results of "systemctl status mariadb.service;:
● mariadb.service - MariaDB 10.5.11 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/mariadb.service.d └─migrated-from-my.cnf-settings.conf Active: active (running) since Sun 2021-08-01 12:48:03 EDT; 24s ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 2760850 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 2760811 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR > Process: 2760809 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Main PID: 2760827 (mariadbd) Status: "Taking your SQL requests now..." Tasks: 16 (limit: 36590) Memory: 100.1M CGroup: /system.slice/mariadb.service └─2760827 /usr/sbin/mariadbd
Aug 01 12:48:02 edwardsmark.info systemd[1]: Starting MariaDB 10.5.11 database server... Aug 01 12:48:02 edwardsmark.info mariadbd[2760827]: 2021-08-01 12:48:02 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.11-MariaDB) starting as process 2760827 ... Aug 01 12:48:03 edwardsmark.info systemd[1]: Started MariaDB 10.5.11 database server.
so then i added this to my:cnf and restarted:
[mariadb] log_error=/var/log/mariadb/mariadb.err
and here is the results from "/var/log/mariadb/mariadb.err"
2021-08-01 12:57:03 0 [Note] InnoDB: Uses event mutexes 2021-08-01 12:57:03 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-08-01 12:57:03 0 [Note] InnoDB: Number of pools: 1 2021-08-01 12:57:03 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2021-08-01 12:57:03 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) 2021-08-01 12:57:03 0 [Note] InnoDB: Using Linux native AIO 2021-08-01 12:57:03 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2021-08-01 12:57:03 0 [Note] InnoDB: Completed initialization of buffer pool 2021-08-01 12:57:03 0 [Note] InnoDB: 128 rollback segments are active. 2021-08-01 12:57:03 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-08-01 12:57:03 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-08-01 12:57:03 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2021-08-01 12:57:03 0 [Note] InnoDB: 10.5.11 started; log sequence number 1055479998; transaction id 41897 2021-08-01 12:57:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2021-08-01 12:57:03 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-08-01 12:57:03 0 [Note] Server socket created on IP: '0.0.0.0'. 2021-08-01 12:57:03 0 [Note] Reading of all Master_info entries succeeded 2021-08-01 12:57:03 0 [Note] Added new Master_info '' to hash table 2021-08-01 12:57:03 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.5.11-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2021-08-01 12:57:03 0 [Note] InnoDB: Buffer pool(s) load completed at 210801 12:57:03 2021-08-01 12:57:03 4 [Warning] Access denied for user 'root'@'localhost' (using password: YES) 2021-08-01 12:57:03 5 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
any suggestions why these mysterious errors are happening? i am starting to wonder if MariadDB fully supports RL or not.
or is there something else i should be monitoring for?
thank you all very much.
Answer
You haven't included the error log after the startup. If there is no logs related to the shutdown of mariadb, this could be: a) lack of filesystem space where the error log is stored b) the server where mariadb was running ran out of memory c) a user or system process hard killed mariadb (SIGKILL)
The dmesg or system journal should provide an indicator of this.
If there are logs beyond that point they'll indicate the shutdown cause. "Shutdown by unknown" is a indication that a signal caused the shutdown (SIGTERM or equivalent)
