[MDEV-34565] MariaDB crashes with SIGILL because the OS does not support AVX512 - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Affects Version/s: 10.5.25, 10.11.8, 10.6.18, 11.0.6, 11.1.5, 11.2.4, 11.4.2
Fix Version/s: 10.5.27, 10.6.20, 10.11.10, 11.2.6, 11.4.4, 11.6.2
Component/s: Storage Engine - InnoDB
Labels:
- crash
- regression
Environment:
AlmaLinux 9.4

Description

The mariadb service start up is failing on AlmaLinux 9.4.

Env:
AlmaLinux 9.4
libgcc-11.4.1-3.el9.alma.1.x86_64

Mariadb packages installed:
MariaDB-shared-10.11.8-1.el9.x86_64
MariaDB-common-10.11.8-1.el9.x86_64
MariaDB-client-10.11.8-1.el9.x86_64
galera-4-26.4.18-1.el9.x86_64
MariaDB-server-10.11.8-1.el9.x86_64
MariaDB-backup-10.11.8-1.el9.x86_64

my.cnf : Default (almost empty)

# This group is read both by the client and the server

# use it for options that affect everything

[client-server]

# include *.cnf from the config directory

!includedir /etc/my.cnf.d

Hardware Info:
-VM

[root@node1]# lscpu

Architecture:            x86_64

  CPU op-mode(s):        32-bit, 64-bit

  Address sizes:         45 bits physical, 57 bits virtual

  Byte Order:            Little Endian

CPU(s):                  2

  On-line CPU(s) list:   0,1

Vendor ID:               GenuineIntel

  BIOS Vendor ID:        GenuineIntel

  Model name:            Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz

    BIOS Model name:     Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz

    CPU family:          6

    Model:               106

    Thread(s) per core:  1

    Core(s) per socket:  1

    Socket(s):           2

    Stepping:            6

    BogoMIPS:            3990.62

    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology

                         tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm 3dn

                         owprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni wbnoinvd arat umip rdpid md_cle

                         ar flush_l1d arch_capabilities

Virtualization features:

  Hypervisor vendor:     VMware

  Virtualization type:   full

Caches (sum of all):

  L1d:                   96 KiB (2 instances)

  L1i:                   64 KiB (2 instances)

  L2:                    2.5 MiB (2 instances)

  L3:                    84 MiB (2 instances)

NUMA:

  NUMA node(s):          1

  NUMA node0 CPU(s):     0,1

Vulnerabilities:

  Gather data sampling:  Unknown: Dependent on hypervisor status

  Itlb multihit:         KVM: Mitigation: VMX unsupported

  L1tf:                  Not affected

  Mds:                   Not affected

  Meltdown:              Not affected

  Mmio stale data:       Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown

  Retbleed:              Not affected

  Spec rstack overflow:  Not affected

  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl

  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization

  Spectre v2:            Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence

  Srbds:                 Not affected

  Tsx async abort:       Not affected

[root@node1]#

Error message from /var/log/message:

Jul 11 01:36:45 node1 mariadbd[79583]: 2024-07-11  1:36:45 0 [Note] Starting MariaDB 10.11.8-MariaDB source revision 3a069644682e336e445039e48baae9693f9a08ee as process 79583

Jul 11 01:36:45 node1 mariadbd[79583]: 240711  1:36:45 [ERROR] mysqld got signal 4 ;

Jul 11 01:36:45 node1 mariadbd[79583]: Sorry, we probably made a mistake, and this is a bug.

Jul 11 01:36:45 node1 mariadbd[79583]: Your assistance in bug reporting will enable us to fix this for the next release.

Jul 11 01:36:45 node1 mariadbd[79583]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Jul 11 01:36:45 node1 mariadbd[79583]: We will try our best to scrape up some info that will hopefully help

Jul 11 01:36:45 node1 mariadbd[79583]: diagnose the problem, but since we have already crashed,

Jul 11 01:36:45 node1 mariadbd[79583]: something is definitely wrong and this may fail.

Jul 11 01:36:45 node1 mariadbd[79583]: Server version: 10.11.8-MariaDB source revision: 3a069644682e336e445039e48baae9693f9a08ee

Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size=134217728

Jul 11 01:36:45 node1 mariadbd[79583]: read_buffer_size=131072

Jul 11 01:36:45 node1 mariadbd[79583]: max_used_connections=0

Jul 11 01:36:45 node1 mariadbd[79583]: max_threads=153

Jul 11 01:36:45 node1 mariadbd[79583]: thread_count=0

Jul 11 01:36:45 node1 mariadbd[79583]: It is possible that mysqld could use up to

Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468061 K  bytes of memory

Jul 11 01:36:45 node1 mariadbd[79583]: Hope that's ok; if not, decrease some variables in the equation.

Jul 11 01:36:45 node1 mariadbd[79583]: Thread pointer: 0x0

Jul 11 01:36:45 node1 mariadbd[79583]: Attempting backtrace. You can use the following information to find out

Jul 11 01:36:45 node1 mariadbd[79583]: where mysqld died. If you see no messages after this, something went

Jul 11 01:36:45 node1 mariadbd[79583]: terribly wrong...

Jul 11 01:36:45 node1 mariadbd[79583]: stack_bottom = 0x0 thread_stack 0x49000

Jul 11 01:36:45 node1 mariadbd[79583]: Printing to addr2line failed

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fb1b527cee]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(handle_fatal_signal+0x468)[0x55fb1afffa28]

Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x3e6f0)[0x7fbf8803e6f0]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xfcbff5)[0x55fb1b53eff5]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc286f3)[0x55fb1b19b6f3]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc2071c)[0x55fb1b19371c]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x55fb1b002b1e]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x84b523)[0x55fb1adbe523]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x8519fc)[0x55fb1adc49fc]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x8f1)[0x55fb1adc5a21]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x7244ff)[0x55fb1ac974ff]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x415)[0x55fb1ac9ca55]

Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x29590)[0x7fbf88029590]

Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(__libc_start_main+0x80)[0x7fbf88029640]

Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_start+0x25)[0x55fb1ac91595]

Jul 11 01:36:45 node1 mariadbd[79583]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

Jul 11 01:36:45 node1 mariadbd[79583]: information that should help you find out what is causing the crash.

Jul 11 01:36:45 node1 mariadbd[79583]: Writing a core file...

Jul 11 01:36:45 node1 mariadbd[79583]: Working directory at /var/lib/mysql

Jul 11 01:36:45 node1 mariadbd[79583]: Resource Limits:

Jul 11 01:36:45 node1 mariadbd[79583]: Limit                     Soft Limit           Hard Limit           Units

Jul 11 01:36:45 node1 mariadbd[79583]: Max cpu time              unlimited            unlimited            seconds

Jul 11 01:36:45 node1 mariadbd[79583]: Max file size             unlimited            unlimited            bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max data size             unlimited            unlimited            bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max stack size            8388608              unlimited            bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max core file size        0                    unlimited            bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max resident set          unlimited            unlimited            bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max processes             30630                30630                processes

Jul 11 01:36:45 node1 mariadbd[79583]: Max open files            32768                32768                files

Jul 11 01:36:45 node1 mariadbd[79583]: Max locked memory         8388608              8388608              bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max address space         unlimited            unlimited            bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max file locks            unlimited            unlimited            locks

Jul 11 01:36:45 node1 mariadbd[79583]: Max pending signals       30630                30630                signals

Jul 11 01:36:45 node1 mariadbd[79583]: Max msgqueue size         819200               819200               bytes

Jul 11 01:36:45 node1 mariadbd[79583]: Max nice priority         0                    0

Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime priority     0                    0

Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime timeout      unlimited            unlimited            us

Jul 11 01:36:45 node1 mariadbd[79583]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h

Jul 11 01:36:45 node1 mariadbd[79583]: Kernel version: Linux version 5.14.0-427.18.1.el9_4.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), GNU ld version 2.35.2-43.el9) #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024

Jul 11 01:36:45 node1 systemd-coredump[79592]: Process 79583 (mariadbd) of user 1001 dumped core.

Jul 11 01:36:45 node1 systemd[1]: systemd-coredump@1493-79590-0.service: Deactivated successfully.

Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Main process exited, code=dumped, status=4/ILL

Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Failed with result 'core-dump'.

Jul 11 01:36:45 node1 systemd[1]: Failed to start MariaDB 10.11.8 database server.

Attachments

Issue Links

is caused by

MDEV-33817 Implement AVX512BW and VPCLMULQDQ based CRC-32 algorithms

Closed

Activity

Ascending order - Click to sort in descending order

Bijju Patel created issue - 2024-07-10 20:19

Daniel Black made changes - 2024-07-11 01:36

Field	Original Value	New Value
Link		This issue is caused by ~~MDEV-33817~~ [ ~~MDEV-33817~~ ]

Daniel Black made changes - 2024-07-11 01:36

Fix Version/s

10.5 [ 23123 ]

Daniel Black made changes - 2024-07-11 02:12

Priority

Major [ 3 ]

Critical [ 2 ]

Daniel Black made changes - 2024-07-11 02:12

Labels

regression

Daniel Black made changes - 2024-07-11 02:12

Fix Version/s

10.11 [ 27614 ]

Daniel Black made changes - 2024-07-11 02:13

Assignee

Vladislav Vaintroub [ wlad ]

Vladislav Vaintroub made changes - 2024-07-21 07:25

Assignee

Vladislav Vaintroub [ wlad ]

Marko Mäkelä [ marko ]

Sergei Golubchik made changes - 2024-07-25 11:07

Description

The mariadb service start up is failing on AlmaLinux 9.4.

Env:
AlmaLinux 9.4
libgcc-11.4.1-3.el9.alma.1.x86_64

Mariadb packages installed:
        MariaDB-shared-10.11.8-1.el9.x86_64
MariaDB-common-10.11.8-1.el9.x86_64
MariaDB-client-10.11.8-1.el9.x86_64
galera-4-26.4.18-1.el9.x86_64
MariaDB-server-10.11.8-1.el9.x86_64
MariaDB-backup-10.11.8-1.el9.x86_64

my.cnf : Default (almost empty)

#
# This group is read both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d

Hardware Info:
  -VM

[root@node1]# lscpu
Architecture: x86_64
  CPU op-mode(s): 32-bit, 64-bit
  Address sizes: 45 bits physical, 57 bits virtual
  Byte Order: Little Endian
CPU(s): 2
  On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
  BIOS Vendor ID: GenuineIntel
  Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    BIOS Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    CPU family: 6
    Model: 106
    Thread(s) per core: 1
    Core(s) per socket: 1
    Socket(s): 2
    Stepping: 6
    BogoMIPS: 3990.62
    Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology
                         tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm 3dn
                         owprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni wbnoinvd arat umip rdpid md_cle
                         ar flush_l1d arch_capabilities
Virtualization features:
  Hypervisor vendor: VMware
  Virtualization type: full
Caches (sum of all):
  L1d: 96 KiB (2 instances)
  L1i: 64 KiB (2 instances)
  L2: 2.5 MiB (2 instances)
  L3: 84 MiB (2 instances)
NUMA:
  NUMA node(s): 1
  NUMA node0 CPU(s): 0,1
Vulnerabilities:
  Gather data sampling: Unknown: Dependent on hypervisor status
  Itlb multihit: KVM: Mitigation: VMX unsupported
  L1tf: Not affected
  Mds: Not affected
  Meltdown: Not affected
  Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
  Retbleed: Not affected
  Spec rstack overflow: Not affected
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds: Not affected
  Tsx async abort: Not affected
[root@node1]#

Error message from /var/log/message:
Jul 11 01:36:45 node1 mariadbd[79583]: 2024-07-11 1:36:45 0 [Note] Starting MariaDB 10.11.8-MariaDB source revision 3a069644682e336e445039e48baae9693f9a08ee as process 79583
Jul 11 01:36:45 node1 mariadbd[79583]: 240711 1:36:45 [ERROR] mysqld got signal 4 ;
Jul 11 01:36:45 node1 mariadbd[79583]: Sorry, we probably made a mistake, and this is a bug.
Jul 11 01:36:45 node1 mariadbd[79583]: Your assistance in bug reporting will enable us to fix this for the next release.
Jul 11 01:36:45 node1 mariadbd[79583]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jul 11 01:36:45 node1 mariadbd[79583]: We will try our best to scrape up some info that will hopefully help
Jul 11 01:36:45 node1 mariadbd[79583]: diagnose the problem, but since we have already crashed,
Jul 11 01:36:45 node1 mariadbd[79583]: something is definitely wrong and this may fail.
Jul 11 01:36:45 node1 mariadbd[79583]: Server version: 10.11.8-MariaDB source revision: 3a069644682e336e445039e48baae9693f9a08ee
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size=134217728
Jul 11 01:36:45 node1 mariadbd[79583]: read_buffer_size=131072
Jul 11 01:36:45 node1 mariadbd[79583]: max_used_connections=0
Jul 11 01:36:45 node1 mariadbd[79583]: max_threads=153
Jul 11 01:36:45 node1 mariadbd[79583]: thread_count=0
Jul 11 01:36:45 node1 mariadbd[79583]: It is possible that mysqld could use up to
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468061 K bytes of memory
Jul 11 01:36:45 node1 mariadbd[79583]: Hope that's ok; if not, decrease some variables in the equation.
Jul 11 01:36:45 node1 mariadbd[79583]: Thread pointer: 0x0
Jul 11 01:36:45 node1 mariadbd[79583]: Attempting backtrace. You can use the following information to find out
Jul 11 01:36:45 node1 mariadbd[79583]: where mysqld died. If you see no messages after this, something went
Jul 11 01:36:45 node1 mariadbd[79583]: terribly wrong...
Jul 11 01:36:45 node1 mariadbd[79583]: stack_bottom = 0x0 thread_stack 0x49000
Jul 11 01:36:45 node1 mariadbd[79583]: Printing to addr2line failed
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fb1b527cee]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(handle_fatal_signal+0x468)[0x55fb1afffa28]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x3e6f0)[0x7fbf8803e6f0]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xfcbff5)[0x55fb1b53eff5]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc286f3)[0x55fb1b19b6f3]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc2071c)[0x55fb1b19371c]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x55fb1b002b1e]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x84b523)[0x55fb1adbe523]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x8519fc)[0x55fb1adc49fc]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x8f1)[0x55fb1adc5a21]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x7244ff)[0x55fb1ac974ff]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x415)[0x55fb1ac9ca55]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x29590)[0x7fbf88029590]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(__libc_start_main+0x80)[0x7fbf88029640]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_start+0x25)[0x55fb1ac91595]
Jul 11 01:36:45 node1 mariadbd[79583]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
Jul 11 01:36:45 node1 mariadbd[79583]: information that should help you find out what is causing the crash.
Jul 11 01:36:45 node1 mariadbd[79583]: Writing a core file...
Jul 11 01:36:45 node1 mariadbd[79583]: Working directory at /var/lib/mysql
Jul 11 01:36:45 node1 mariadbd[79583]: Resource Limits:
Jul 11 01:36:45 node1 mariadbd[79583]: Limit Soft Limit Hard Limit Units
Jul 11 01:36:45 node1 mariadbd[79583]: Max cpu time unlimited unlimited seconds
Jul 11 01:36:45 node1 mariadbd[79583]: Max file size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max data size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max stack size 8388608 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max core file size 0 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max resident set unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max processes 30630 30630 processes
Jul 11 01:36:45 node1 mariadbd[79583]: Max open files 32768 32768 files
Jul 11 01:36:45 node1 mariadbd[79583]: Max locked memory 8388608 8388608 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max address space unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max file locks unlimited unlimited locks
Jul 11 01:36:45 node1 mariadbd[79583]: Max pending signals 30630 30630 signals
Jul 11 01:36:45 node1 mariadbd[79583]: Max msgqueue size 819200 819200 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max nice priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime timeout unlimited unlimited us
Jul 11 01:36:45 node1 mariadbd[79583]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
Jul 11 01:36:45 node1 mariadbd[79583]: Kernel version: Linux version 5.14.0-427.18.1.el9_4.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), GNU ld version 2.35.2-43.el9) #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024
Jul 11 01:36:45 node1 systemd-coredump[79592]: Process 79583 (mariadbd) of user 1001 dumped core.
Jul 11 01:36:45 node1 systemd[1]: systemd-coredump@1493-79590-0.service: Deactivated successfully.
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Main process exited, code=dumped, status=4/ILL
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Failed with result 'core-dump'.
Jul 11 01:36:45 node1 systemd[1]: Failed to start MariaDB 10.11.8 database server.

The mariadb service start up is failing on AlmaLinux 9.4.

Env:
AlmaLinux 9.4
libgcc-11.4.1-3.el9.alma.1.x86_64

Mariadb packages installed:
        MariaDB-shared-10.11.8-1.el9.x86_64
MariaDB-common-10.11.8-1.el9.x86_64
MariaDB-client-10.11.8-1.el9.x86_64
galera-4-26.4.18-1.el9.x86_64
MariaDB-server-10.11.8-1.el9.x86_64
MariaDB-backup-10.11.8-1.el9.x86_64

my.cnf : Default (almost empty)
{noformat}
#
# This group is read both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d
{noformat}

Hardware Info:
  -VM

[root@node1]# lscpu
Architecture: x86_64
  CPU op-mode(s): 32-bit, 64-bit
  Address sizes: 45 bits physical, 57 bits virtual
  Byte Order: Little Endian
CPU(s): 2
  On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
  BIOS Vendor ID: GenuineIntel
  Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    BIOS Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    CPU family: 6
    Model: 106
    Thread(s) per core: 1
    Core(s) per socket: 1
    Socket(s): 2
    Stepping: 6
    BogoMIPS: 3990.62
    Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology
                         tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm 3dn
                         owprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni wbnoinvd arat umip rdpid md_cle
                         ar flush_l1d arch_capabilities
Virtualization features:
  Hypervisor vendor: VMware
  Virtualization type: full
Caches (sum of all):
  L1d: 96 KiB (2 instances)
  L1i: 64 KiB (2 instances)
  L2: 2.5 MiB (2 instances)
  L3: 84 MiB (2 instances)
NUMA:
  NUMA node(s): 1
  NUMA node0 CPU(s): 0,1
Vulnerabilities:
  Gather data sampling: Unknown: Dependent on hypervisor status
  Itlb multihit: KVM: Mitigation: VMX unsupported
  L1tf: Not affected
  Mds: Not affected
  Meltdown: Not affected
  Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
  Retbleed: Not affected
  Spec rstack overflow: Not affected
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds: Not affected
  Tsx async abort: Not affected
[root@node1]#

Error message from /var/log/message:
Jul 11 01:36:45 node1 mariadbd[79583]: 2024-07-11 1:36:45 0 [Note] Starting MariaDB 10.11.8-MariaDB source revision 3a069644682e336e445039e48baae9693f9a08ee as process 79583
Jul 11 01:36:45 node1 mariadbd[79583]: 240711 1:36:45 [ERROR] mysqld got signal 4 ;
Jul 11 01:36:45 node1 mariadbd[79583]: Sorry, we probably made a mistake, and this is a bug.
Jul 11 01:36:45 node1 mariadbd[79583]: Your assistance in bug reporting will enable us to fix this for the next release.
Jul 11 01:36:45 node1 mariadbd[79583]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jul 11 01:36:45 node1 mariadbd[79583]: We will try our best to scrape up some info that will hopefully help
Jul 11 01:36:45 node1 mariadbd[79583]: diagnose the problem, but since we have already crashed,
Jul 11 01:36:45 node1 mariadbd[79583]: something is definitely wrong and this may fail.
Jul 11 01:36:45 node1 mariadbd[79583]: Server version: 10.11.8-MariaDB source revision: 3a069644682e336e445039e48baae9693f9a08ee
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size=134217728
Jul 11 01:36:45 node1 mariadbd[79583]: read_buffer_size=131072
Jul 11 01:36:45 node1 mariadbd[79583]: max_used_connections=0
Jul 11 01:36:45 node1 mariadbd[79583]: max_threads=153
Jul 11 01:36:45 node1 mariadbd[79583]: thread_count=0
Jul 11 01:36:45 node1 mariadbd[79583]: It is possible that mysqld could use up to
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468061 K bytes of memory
Jul 11 01:36:45 node1 mariadbd[79583]: Hope that's ok; if not, decrease some variables in the equation.
Jul 11 01:36:45 node1 mariadbd[79583]: Thread pointer: 0x0
Jul 11 01:36:45 node1 mariadbd[79583]: Attempting backtrace. You can use the following information to find out
Jul 11 01:36:45 node1 mariadbd[79583]: where mysqld died. If you see no messages after this, something went
Jul 11 01:36:45 node1 mariadbd[79583]: terribly wrong...
Jul 11 01:36:45 node1 mariadbd[79583]: stack_bottom = 0x0 thread_stack 0x49000
Jul 11 01:36:45 node1 mariadbd[79583]: Printing to addr2line failed
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fb1b527cee]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(handle_fatal_signal+0x468)[0x55fb1afffa28]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x3e6f0)[0x7fbf8803e6f0]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xfcbff5)[0x55fb1b53eff5]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc286f3)[0x55fb1b19b6f3]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc2071c)[0x55fb1b19371c]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x55fb1b002b1e]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x84b523)[0x55fb1adbe523]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x8519fc)[0x55fb1adc49fc]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x8f1)[0x55fb1adc5a21]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x7244ff)[0x55fb1ac974ff]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x415)[0x55fb1ac9ca55]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x29590)[0x7fbf88029590]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(__libc_start_main+0x80)[0x7fbf88029640]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_start+0x25)[0x55fb1ac91595]
Jul 11 01:36:45 node1 mariadbd[79583]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
Jul 11 01:36:45 node1 mariadbd[79583]: information that should help you find out what is causing the crash.
Jul 11 01:36:45 node1 mariadbd[79583]: Writing a core file...
Jul 11 01:36:45 node1 mariadbd[79583]: Working directory at /var/lib/mysql
Jul 11 01:36:45 node1 mariadbd[79583]: Resource Limits:
Jul 11 01:36:45 node1 mariadbd[79583]: Limit Soft Limit Hard Limit Units
Jul 11 01:36:45 node1 mariadbd[79583]: Max cpu time unlimited unlimited seconds
Jul 11 01:36:45 node1 mariadbd[79583]: Max file size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max data size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max stack size 8388608 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max core file size 0 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max resident set unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max processes 30630 30630 processes
Jul 11 01:36:45 node1 mariadbd[79583]: Max open files 32768 32768 files
Jul 11 01:36:45 node1 mariadbd[79583]: Max locked memory 8388608 8388608 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max address space unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max file locks unlimited unlimited locks
Jul 11 01:36:45 node1 mariadbd[79583]: Max pending signals 30630 30630 signals
Jul 11 01:36:45 node1 mariadbd[79583]: Max msgqueue size 819200 819200 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max nice priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime timeout unlimited unlimited us
Jul 11 01:36:45 node1 mariadbd[79583]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
Jul 11 01:36:45 node1 mariadbd[79583]: Kernel version: Linux version 5.14.0-427.18.1.el9_4.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), GNU ld version 2.35.2-43.el9) #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024
Jul 11 01:36:45 node1 systemd-coredump[79592]: Process 79583 (mariadbd) of user 1001 dumped core.
Jul 11 01:36:45 node1 systemd[1]: systemd-coredump@1493-79590-0.service: Deactivated successfully.
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Main process exited, code=dumped, status=4/ILL
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Failed with result 'core-dump'.
Jul 11 01:36:45 node1 systemd[1]: Failed to start MariaDB 10.11.8 database server.

Sergei Golubchik made changes - 2024-07-25 11:07

Description

The mariadb service start up is failing on AlmaLinux 9.4.

Env:
AlmaLinux 9.4
libgcc-11.4.1-3.el9.alma.1.x86_64

Mariadb packages installed:
        MariaDB-shared-10.11.8-1.el9.x86_64
MariaDB-common-10.11.8-1.el9.x86_64
MariaDB-client-10.11.8-1.el9.x86_64
galera-4-26.4.18-1.el9.x86_64
MariaDB-server-10.11.8-1.el9.x86_64
MariaDB-backup-10.11.8-1.el9.x86_64

my.cnf : Default (almost empty)
{noformat}
#
# This group is read both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d
{noformat}

Hardware Info:
  -VM

[root@node1]# lscpu
Architecture: x86_64
  CPU op-mode(s): 32-bit, 64-bit
  Address sizes: 45 bits physical, 57 bits virtual
  Byte Order: Little Endian
CPU(s): 2
  On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
  BIOS Vendor ID: GenuineIntel
  Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    BIOS Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    CPU family: 6
    Model: 106
    Thread(s) per core: 1
    Core(s) per socket: 1
    Socket(s): 2
    Stepping: 6
    BogoMIPS: 3990.62
    Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology
                         tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm 3dn
                         owprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni wbnoinvd arat umip rdpid md_cle
                         ar flush_l1d arch_capabilities
Virtualization features:
  Hypervisor vendor: VMware
  Virtualization type: full
Caches (sum of all):
  L1d: 96 KiB (2 instances)
  L1i: 64 KiB (2 instances)
  L2: 2.5 MiB (2 instances)
  L3: 84 MiB (2 instances)
NUMA:
  NUMA node(s): 1
  NUMA node0 CPU(s): 0,1
Vulnerabilities:
  Gather data sampling: Unknown: Dependent on hypervisor status
  Itlb multihit: KVM: Mitigation: VMX unsupported
  L1tf: Not affected
  Mds: Not affected
  Meltdown: Not affected
  Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
  Retbleed: Not affected
  Spec rstack overflow: Not affected
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds: Not affected
  Tsx async abort: Not affected
[root@node1]#

Error message from /var/log/message:
Jul 11 01:36:45 node1 mariadbd[79583]: 2024-07-11 1:36:45 0 [Note] Starting MariaDB 10.11.8-MariaDB source revision 3a069644682e336e445039e48baae9693f9a08ee as process 79583
Jul 11 01:36:45 node1 mariadbd[79583]: 240711 1:36:45 [ERROR] mysqld got signal 4 ;
Jul 11 01:36:45 node1 mariadbd[79583]: Sorry, we probably made a mistake, and this is a bug.
Jul 11 01:36:45 node1 mariadbd[79583]: Your assistance in bug reporting will enable us to fix this for the next release.
Jul 11 01:36:45 node1 mariadbd[79583]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jul 11 01:36:45 node1 mariadbd[79583]: We will try our best to scrape up some info that will hopefully help
Jul 11 01:36:45 node1 mariadbd[79583]: diagnose the problem, but since we have already crashed,
Jul 11 01:36:45 node1 mariadbd[79583]: something is definitely wrong and this may fail.
Jul 11 01:36:45 node1 mariadbd[79583]: Server version: 10.11.8-MariaDB source revision: 3a069644682e336e445039e48baae9693f9a08ee
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size=134217728
Jul 11 01:36:45 node1 mariadbd[79583]: read_buffer_size=131072
Jul 11 01:36:45 node1 mariadbd[79583]: max_used_connections=0
Jul 11 01:36:45 node1 mariadbd[79583]: max_threads=153
Jul 11 01:36:45 node1 mariadbd[79583]: thread_count=0
Jul 11 01:36:45 node1 mariadbd[79583]: It is possible that mysqld could use up to
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468061 K bytes of memory
Jul 11 01:36:45 node1 mariadbd[79583]: Hope that's ok; if not, decrease some variables in the equation.
Jul 11 01:36:45 node1 mariadbd[79583]: Thread pointer: 0x0
Jul 11 01:36:45 node1 mariadbd[79583]: Attempting backtrace. You can use the following information to find out
Jul 11 01:36:45 node1 mariadbd[79583]: where mysqld died. If you see no messages after this, something went
Jul 11 01:36:45 node1 mariadbd[79583]: terribly wrong...
Jul 11 01:36:45 node1 mariadbd[79583]: stack_bottom = 0x0 thread_stack 0x49000
Jul 11 01:36:45 node1 mariadbd[79583]: Printing to addr2line failed
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fb1b527cee]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(handle_fatal_signal+0x468)[0x55fb1afffa28]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x3e6f0)[0x7fbf8803e6f0]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xfcbff5)[0x55fb1b53eff5]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc286f3)[0x55fb1b19b6f3]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc2071c)[0x55fb1b19371c]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x55fb1b002b1e]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x84b523)[0x55fb1adbe523]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x8519fc)[0x55fb1adc49fc]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x8f1)[0x55fb1adc5a21]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x7244ff)[0x55fb1ac974ff]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x415)[0x55fb1ac9ca55]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x29590)[0x7fbf88029590]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(__libc_start_main+0x80)[0x7fbf88029640]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_start+0x25)[0x55fb1ac91595]
Jul 11 01:36:45 node1 mariadbd[79583]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
Jul 11 01:36:45 node1 mariadbd[79583]: information that should help you find out what is causing the crash.
Jul 11 01:36:45 node1 mariadbd[79583]: Writing a core file...
Jul 11 01:36:45 node1 mariadbd[79583]: Working directory at /var/lib/mysql
Jul 11 01:36:45 node1 mariadbd[79583]: Resource Limits:
Jul 11 01:36:45 node1 mariadbd[79583]: Limit Soft Limit Hard Limit Units
Jul 11 01:36:45 node1 mariadbd[79583]: Max cpu time unlimited unlimited seconds
Jul 11 01:36:45 node1 mariadbd[79583]: Max file size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max data size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max stack size 8388608 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max core file size 0 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max resident set unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max processes 30630 30630 processes
Jul 11 01:36:45 node1 mariadbd[79583]: Max open files 32768 32768 files
Jul 11 01:36:45 node1 mariadbd[79583]: Max locked memory 8388608 8388608 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max address space unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max file locks unlimited unlimited locks
Jul 11 01:36:45 node1 mariadbd[79583]: Max pending signals 30630 30630 signals
Jul 11 01:36:45 node1 mariadbd[79583]: Max msgqueue size 819200 819200 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max nice priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime timeout unlimited unlimited us
Jul 11 01:36:45 node1 mariadbd[79583]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
Jul 11 01:36:45 node1 mariadbd[79583]: Kernel version: Linux version 5.14.0-427.18.1.el9_4.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), GNU ld version 2.35.2-43.el9) #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024
Jul 11 01:36:45 node1 systemd-coredump[79592]: Process 79583 (mariadbd) of user 1001 dumped core.
Jul 11 01:36:45 node1 systemd[1]: systemd-coredump@1493-79590-0.service: Deactivated successfully.
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Main process exited, code=dumped, status=4/ILL
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Failed with result 'core-dump'.
Jul 11 01:36:45 node1 systemd[1]: Failed to start MariaDB 10.11.8 database server.

The mariadb service start up is failing on AlmaLinux 9.4.

Env:
AlmaLinux 9.4
libgcc-11.4.1-3.el9.alma.1.x86_64

Mariadb packages installed:
        MariaDB-shared-10.11.8-1.el9.x86_64
MariaDB-common-10.11.8-1.el9.x86_64
MariaDB-client-10.11.8-1.el9.x86_64
galera-4-26.4.18-1.el9.x86_64
MariaDB-server-10.11.8-1.el9.x86_64
MariaDB-backup-10.11.8-1.el9.x86_64

my.cnf : Default (almost empty)
{noformat}
#
# This group is read both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d
{noformat}

Hardware Info:
  -VM
{noformat}
[root@node1]# lscpu
Architecture: x86_64
  CPU op-mode(s): 32-bit, 64-bit
  Address sizes: 45 bits physical, 57 bits virtual
  Byte Order: Little Endian
CPU(s): 2
  On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
  BIOS Vendor ID: GenuineIntel
  Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    BIOS Model name: Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
    CPU family: 6
    Model: 106
    Thread(s) per core: 1
    Core(s) per socket: 1
    Socket(s): 2
    Stepping: 6
    BogoMIPS: 3990.62
    Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology
                         tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm 3dn
                         owprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni wbnoinvd arat umip rdpid md_cle
                         ar flush_l1d arch_capabilities
Virtualization features:
  Hypervisor vendor: VMware
  Virtualization type: full
Caches (sum of all):
  L1d: 96 KiB (2 instances)
  L1i: 64 KiB (2 instances)
  L2: 2.5 MiB (2 instances)
  L3: 84 MiB (2 instances)
NUMA:
  NUMA node(s): 1
  NUMA node0 CPU(s): 0,1
Vulnerabilities:
  Gather data sampling: Unknown: Dependent on hypervisor status
  Itlb multihit: KVM: Mitigation: VMX unsupported
  L1tf: Not affected
  Mds: Not affected
  Meltdown: Not affected
  Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
  Retbleed: Not affected
  Spec rstack overflow: Not affected
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds: Not affected
  Tsx async abort: Not affected
[root@node1]#
{noformat}

Error message from /var/log/message:
{noformat}Jul 11 01:36:45 node1 mariadbd[79583]: 2024-07-11 1:36:45 0 [Note] Starting MariaDB 10.11.8-MariaDB source revision 3a069644682e336e445039e48baae9693f9a08ee as process 79583
Jul 11 01:36:45 node1 mariadbd[79583]: 240711 1:36:45 [ERROR] mysqld got signal 4 ;
Jul 11 01:36:45 node1 mariadbd[79583]: Sorry, we probably made a mistake, and this is a bug.
Jul 11 01:36:45 node1 mariadbd[79583]: Your assistance in bug reporting will enable us to fix this for the next release.
Jul 11 01:36:45 node1 mariadbd[79583]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jul 11 01:36:45 node1 mariadbd[79583]: We will try our best to scrape up some info that will hopefully help
Jul 11 01:36:45 node1 mariadbd[79583]: diagnose the problem, but since we have already crashed,
Jul 11 01:36:45 node1 mariadbd[79583]: something is definitely wrong and this may fail.
Jul 11 01:36:45 node1 mariadbd[79583]: Server version: 10.11.8-MariaDB source revision: 3a069644682e336e445039e48baae9693f9a08ee
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size=134217728
Jul 11 01:36:45 node1 mariadbd[79583]: read_buffer_size=131072
Jul 11 01:36:45 node1 mariadbd[79583]: max_used_connections=0
Jul 11 01:36:45 node1 mariadbd[79583]: max_threads=153
Jul 11 01:36:45 node1 mariadbd[79583]: thread_count=0
Jul 11 01:36:45 node1 mariadbd[79583]: It is possible that mysqld could use up to
Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468061 K bytes of memory
Jul 11 01:36:45 node1 mariadbd[79583]: Hope that's ok; if not, decrease some variables in the equation.
Jul 11 01:36:45 node1 mariadbd[79583]: Thread pointer: 0x0
Jul 11 01:36:45 node1 mariadbd[79583]: Attempting backtrace. You can use the following information to find out
Jul 11 01:36:45 node1 mariadbd[79583]: where mysqld died. If you see no messages after this, something went
Jul 11 01:36:45 node1 mariadbd[79583]: terribly wrong...
Jul 11 01:36:45 node1 mariadbd[79583]: stack_bottom = 0x0 thread_stack 0x49000
Jul 11 01:36:45 node1 mariadbd[79583]: Printing to addr2line failed
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fb1b527cee]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(handle_fatal_signal+0x468)[0x55fb1afffa28]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x3e6f0)[0x7fbf8803e6f0]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xfcbff5)[0x55fb1b53eff5]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc286f3)[0x55fb1b19b6f3]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc2071c)[0x55fb1b19371c]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x55fb1b002b1e]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x84b523)[0x55fb1adbe523]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x8519fc)[0x55fb1adc49fc]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x8f1)[0x55fb1adc5a21]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x7244ff)[0x55fb1ac974ff]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x415)[0x55fb1ac9ca55]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x29590)[0x7fbf88029590]
Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(__libc_start_main+0x80)[0x7fbf88029640]
Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_start+0x25)[0x55fb1ac91595]
Jul 11 01:36:45 node1 mariadbd[79583]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
Jul 11 01:36:45 node1 mariadbd[79583]: information that should help you find out what is causing the crash.
Jul 11 01:36:45 node1 mariadbd[79583]: Writing a core file...
Jul 11 01:36:45 node1 mariadbd[79583]: Working directory at /var/lib/mysql
Jul 11 01:36:45 node1 mariadbd[79583]: Resource Limits:
Jul 11 01:36:45 node1 mariadbd[79583]: Limit Soft Limit Hard Limit Units
Jul 11 01:36:45 node1 mariadbd[79583]: Max cpu time unlimited unlimited seconds
Jul 11 01:36:45 node1 mariadbd[79583]: Max file size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max data size unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max stack size 8388608 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max core file size 0 unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max resident set unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max processes 30630 30630 processes
Jul 11 01:36:45 node1 mariadbd[79583]: Max open files 32768 32768 files
Jul 11 01:36:45 node1 mariadbd[79583]: Max locked memory 8388608 8388608 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max address space unlimited unlimited bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max file locks unlimited unlimited locks
Jul 11 01:36:45 node1 mariadbd[79583]: Max pending signals 30630 30630 signals
Jul 11 01:36:45 node1 mariadbd[79583]: Max msgqueue size 819200 819200 bytes
Jul 11 01:36:45 node1 mariadbd[79583]: Max nice priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime priority 0 0
Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime timeout unlimited unlimited us
Jul 11 01:36:45 node1 mariadbd[79583]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
Jul 11 01:36:45 node1 mariadbd[79583]: Kernel version: Linux version 5.14.0-427.18.1.el9_4.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), GNU ld version 2.35.2-43.el9) #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024
Jul 11 01:36:45 node1 systemd-coredump[79592]: Process 79583 (mariadbd) of user 1001 dumped core.
Jul 11 01:36:45 node1 systemd[1]: systemd-coredump@1493-79590-0.service: Deactivated successfully.
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Main process exited, code=dumped, status=4/ILL
Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Failed with result 'core-dump'.
Jul 11 01:36:45 node1 systemd[1]: Failed to start MariaDB 10.11.8 database server.
{noformat}

Marko Mäkelä made changes - 2024-07-29 07:38

Status

Open [ 1 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2024-07-29 08:12

Fix Version/s		10.6 [ 24028 ]
Fix Version/s		11.4 [ 29301 ]
Affects Version/s		11.4.2 [ 29633 ]
Affects Version/s		11.2.4 [ 29631 ]
Affects Version/s		11.1.5 [ 29629 ]
Affects Version/s		11.0.6 [ 29628 ]
Affects Version/s		10.6.18 [ 29627 ]
Affects Version/s		10.5.25 [ 29626 ]
Labels	regression	crash regression
Priority	Critical [ 2 ]	Blocker [ 1 ]
Summary	Mariadb service startup fails with signal 4	MariaDB crashes with SIGILL because the OS does not support AVX512

Marko Mäkelä made changes - 2024-07-29 08:12

Assignee	Marko Mäkelä [ marko ]	Vladislav Vaintroub [ wlad ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Vladislav Vaintroub made changes - 2024-07-29 09:13

Assignee	Vladislav Vaintroub [ wlad ]	Marko Mäkelä [ marko ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Marko Mäkelä made changes - 2024-07-29 09:57

issue.field.resolutiondate

2024-07-29 09:57:46.0

2024-07-29 09:57:46.076

Marko Mäkelä made changes - 2024-07-29 09:57

Fix Version/s		10.5.26 [ 29832 ]
Fix Version/s		10.6.19 [ 29833 ]
Fix Version/s		10.11.9 [ 29834 ]
Fix Version/s		11.1.6 [ 29835 ]
Fix Version/s		11.2.5 [ 29836 ]
Fix Version/s		11.4.3 [ 29837 ]
Fix Version/s		11.5.2 [ 29838 ]
Fix Version/s		11.6.1 [ 29847 ]
Fix Version/s	10.5 [ 23123 ]
Fix Version/s	10.6 [ 24028 ]
Fix Version/s	10.11 [ 27614 ]
Fix Version/s	11.4 [ 29301 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Marko Mäkelä made changes - 2024-08-20 14:40

Resolution	Fixed [ 1 ]
Status	Closed [ 6 ]	Stalled [ 10000 ]

Marko Mäkelä made changes - 2024-08-20 14:40

Fix Version/s		10.5 [ 23123 ]
Fix Version/s		10.6 [ 24028 ]
Fix Version/s		10.11 [ 27614 ]
Fix Version/s		11.2 [ 28603 ]
Fix Version/s		11.4 [ 29301 ]
Fix Version/s	10.5.26 [ 29832 ]
Fix Version/s	10.6.19 [ 29833 ]
Fix Version/s	10.11.9 [ 29834 ]
Fix Version/s	11.1.6 [ 29835 ]
Fix Version/s	11.2.5 [ 29836 ]
Fix Version/s	11.4.3 [ 29837 ]
Fix Version/s	11.5.2 [ 29838 ]
Fix Version/s	11.6.1 [ 29847 ]

Marko Mäkelä made changes - 2024-08-20 14:40

Status

Stalled [ 10000 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2024-08-20 15:09

Assignee	Marko Mäkelä [ marko ]	Vladislav Vaintroub [ wlad ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Marko Mäkelä made changes - 2024-08-21 06:11

Fix Version/s		10.5.27 [ 29902 ]
Fix Version/s		10.6.20 [ 29903 ]
Fix Version/s		10.11.10 [ 29904 ]
Fix Version/s		11.2.6 [ 29906 ]
Fix Version/s		11.4.4 [ 29907 ]
Fix Version/s		11.6.2 [ 29908 ]
Fix Version/s	10.5 [ 23123 ]
Fix Version/s	10.6 [ 24028 ]
Fix Version/s	10.11 [ 27614 ]
Fix Version/s	11.2 [ 28603 ]
Fix Version/s	11.4 [ 29301 ]
Assignee	Vladislav Vaintroub [ wlad ]	Marko Mäkelä [ marko ]
Resolution		Fixed [ 1 ]
Status	In Review [ 10002 ]	Closed [ 6 ]

People

Assignee:: Marko Mäkelä

Reporter:: Bijju Patel

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2024-07-10 20:19

Updated:: 2024-08-21 06:16

Resolved:: 2024-08-21 06:11

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration