Solved Update MariaDB 10.4.26 to 10.4.27

TomR

TomR

Verified User
Joined
Jan 7, 2008
Messages
51
This is only one 1 of our servers ( unformunally a productie server )

Bash: 
[root@cursadweb-04 custombuild]# ./build mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Error: Nothing to do
######################################################################## 100.0%
Found /usr/local/directadmin/custombuild/mysql/MariaDB-client-10.4.27-1.el7.centos.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-devel-10.4.27-1.el7.centos.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-server-10.4.27-1.el7.centos.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-shared-10.4.27-1.el7.centos.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-common-10.4.27-1.el7.centos.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-compat-10.4.27-1.el7.centos.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-backup-10.4.27-1.el7.centos.x86_64.rpm
Installing dependencies...
Installing libjemalloc...
Found /usr/local/directadmin/custombuild/mysql/jemalloc-3.6.0-1.el7.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/jemalloc-devel-3.6.0-1.el7.x86_64.rpm
warning: /usr/local/directadmin/custombuild/mysql/jemalloc-3.6.0-1.el7.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                          ########################################
Updating / installing...
jemalloc-3.6.0-1.el7                  ########################################
jemalloc-devel-3.6.0-1.el7            ########################################
Installing galera...
Found /usr/local/directadmin/custombuild/mysql/galera-4-26.4.8-1.el7.centos.x86_64.rpm
warning: /usr/local/directadmin/custombuild/mysql/galera-4-26.4.8-1.el7.centos.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                          ########################################
Updating / installing...
galera-4-26.4.8-1.el7.centos          ########################################
Stopping mysqld ...
Updating MariaDB 10.4.27 to 10.4.27
warning: MariaDB-client-10.4.27-1.el7.centos.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                          ########################################
Updating / installing...
MariaDB-compat-10.4.27-1.el7.centos   ########################################
MariaDB-common-10.4.27-1.el7.centos   ########################################
MariaDB-client-10.4.27-1.el7.centos   ########################################
MariaDB-shared-10.4.27-1.el7.centos   ########################################
MariaDB-devel-10.4.27-1.el7.centos    ########################################
MariaDB-server-10.4.27-1.el7.centos   ########################################
MariaDB-backup-10.4.27-1.el7.centos   ########################################
Created symlink from /etc/systemd/system/mysql.service to /etc/systemd/system/mariadb.service.
Created symlink from /etc/systemd/system/mysqld.service to /etc/systemd/system/mariadb.service.
Ensuring local-infile is disabled for security reasons in MySQL configuration file...
Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.
Giving mysqld a few seconds to start up...
Giving mysqld a another few seconds to start up...
Giving mysqld last 20 seconds to start up...
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
/usr/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect
cp: '/usr/lib/libmysqlclient.so' and '/usr/lib/mysql/libmysqlclient.so' are the same file
Restarting MySQL.
Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.
Installation completed.

​

 
From /var/log/mysqld.log
Bash: 
2022-12-05 16:23:48 0 [Note] InnoDB: Using Linux native AIO
2022-12-05 16:23:48 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-12-05 16:23:48 0 [Note] InnoDB: Uses event mutexes
2022-12-05 16:23:48 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2022-12-05 16:23:48 0 [Note] InnoDB: Number of pools: 1
2022-12-05 16:23:48 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-12-05 16:23:48 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-12-05 16:23:48 0 [Note] InnoDB: Completed initialization of buffer pool
2022-12-05 16:23:48 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-12-05 16:23:48 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=588522722350
2022-12-05 16:23:48 0 [Note] InnoDB: Starting final batch to recover 104 pages from redo log.
2022-12-05 16:23:49 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-12-05 16:23:49 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-12-05 16:23:49 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-12-05 16:23:49 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-12-05 16:23:49 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-12-05 16:23:49 0 [Note] InnoDB: Waiting for purge to start
2022-12-05 16:23:49 0x7fe7977fe700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.27/storage/innobase/include/fut0lst.inl line 67
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
221205 16:23:49 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.27-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467777 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fe7880009a8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7fe7977fdbf0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x564551ab9b6e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x56455150577f]
sigaction.c:0(__restore_rt)[0x7fe7d3d11630]
:0(__GI_raise)[0x7fe7d315c387]
:0(__GI_abort)[0x7fe7d315da78]
/usr/sbin/mysqld(+0x5cdc5c)[0x56455120fc5c]
/usr/sbin/mysqld(+0x5cd854)[0x56455120f854]
/usr/sbin/mysqld(+0xcb76ce)[0x5645518f96ce]
/usr/sbin/mysqld(+0xcb8517)[0x5645518fa517]
/usr/sbin/mysqld(+0xcbb8c3)[0x5645518fd8c3]
/usr/sbin/mysqld(+0xca0873)[0x5645518e2873]
pthread_create.c:0(start_thread)[0x7fe7d3d09ea5]
/lib64/libc.so.6(clone+0x6d)[0x7fe7d3224b0d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): (null)
Connection ID (thread ID): 1
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.

We think the query pointer is invalid, but we will try to print it anyway.
Query:

Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             31118                31118                processes
Max open files            655350               655350               files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       31118                31118                signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us
Core pattern: core

Kernel version: Linux version 3.10.0-1160.80.1.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Nov 8 15:48:59 UTC 2022
 
Hello,

You are advised to re-install a MySQL server and re-import MySQL databases from a backup. That might be the simplest way to go.
 
Thanks, I did that already. I was just wondering what the problem was and why there was no clue in logging.
 
You must log in or register to reply here.
Back
Top