2021-08-21 14:24:37 132494 [Note] WSREP: cluster conflict due to certification failure for threads: 2021-08-21 14:24:37 1 [Note] WSREP: cluster conflict due to high priority abort for threads: 2021-08-21 14:24:37 1 [Note] WSREP: Winning thread: THD: 1, mode: applier, state: executing, conflict: no conflict, seqno: 256916178 SQL: UPDATE `news` SET `views`=24984 WHERE `id`=83796▒▒ a 2021-08-21 14:24:37 132494 [Note] WSREP: Victim thread: THD: 132494, mode: local, state: executing, conflict: cert failure, seqno: 256916179 SQL: UPDATE `news` SET `views`=24984 WHERE `id`=83796 2021-08-21 14:24:37 1 [Note] WSREP: Victim thread: THD: 132494, mode: local, state: executing, conflict: cert failure, seqno: 256916179 SQL: UPDATE `news` SET `views`=24984 WHERE `id`=83796 2021-08-21 14:24:40 132506 [Note] WSREP: cluster conflict due to certification failure for threads: 2021-08-21 14:24:40 132506 [Note] WSREP: Victim thread: THD: 132506, mode: local, state: executing, conflict: cert failure, seqno: 256916206 SQL: UPDATE `news` SET `views`=24991 WHERE `id`=83796 2021-08-21 14:24:40 1 [Note] WSREP: cluster conflict due to high priority abort for threads: 2021-08-21 14:24:40 1 [Note] WSREP: Winning thread: THD: 1, mode: applier, state: executing, conflict: no conflict, seqno: 256916205 SQL: UPDATE `news` SET `views`=24991 WHERE `id`=83796▒▒ a 2021-08-21 14:24:40 1 [Note] WSREP: Victim thread: THD: 132506, mode: local, state: executing, conflict: cert failure, seqno: 256916206 SQL: UPDATE `news` SET `views`=24991 WHERE `id`=83796 2021-08-21 14:24:50 1 [Note] WSREP: cluster conflict due to high priority abort for threads: 2021-08-21 14:24:50 1 [Note] WSREP: Winning thread: THD: 1, mode: applier, state: executing, conflict: no conflict, seqno: 256916282 SQL: UPDATE `news` SET `views`=25024 WHERE `id`=83796▒▒ a 2021-08-21 14:24:50 1 [Note] WSREP: Victim thread: THD: 132539, mode: local, state: committing, conflict: no conflict, seqno: -1 SQL: UPDATE `news` SET `views`=25024 WHERE `id`=83796 2021-08-21 14:26:13 132746 [Note] WSREP: cluster conflict due to certification failure for threads: 2021-08-21 14:26:13 132746 [Note] WSREP: Victim thread: THD: 132746, mode: local, state: executing, conflict: cert failure, seqno: 256916951 SQL: UPDATE `news` SET `views`=25273 WHERE `id`=83796 2021-08-21 14:26:13 1 [Note] WSREP: cluster conflict due to high priority abort for threads: 2021-08-21 14:26:13 1 [Note] WSREP: Winning thread: THD: 1, mode: applier, state: executing, conflict: no conflict, seqno: 256916950 SQL: UPDATE `news` SET `views`=25273 WHERE `id`=83796▒▒ a 2021-08-21 14:26:13 1 [Note] WSREP: Victim thread: THD: 132746, mode: local, state: executing, conflict: cert failure, seqno: -1 SQL: UPDATE `news` SET `views`=25273 WHERE `id`=83796 2021-08-21 14:27:19 1 [Note] WSREP: cluster conflict due to high priority abort for threads: 2021-08-21 14:27:19 1 [Note] WSREP: Winning thread: THD: 1, mode: applier, state: executing, conflict: no conflict, seqno: 256917497 SQL: UPDATE `news` SET `views`=25499 WHERE `id`=83796'▒ a 2021-08-21 14:27:19 1 [Note] WSREP: Victim thread: THD: 132951, mode: local, state: committing, conflict: no conflict, seqno: -1 SQL: UPDATE `news` SET `views`=25499 WHERE `id`=83796 2021-08-21 14:27:19 0 [ERROR] WSREP: invalid state ROLLED_BACK (FATAL) at /home/buildbot/buildbot/build/galera/src/replicator_smm.cpp:abort_trx():736 2021-08-21 14:27:19 0 [ERROR] WSREP: cancel commit bad exit: 7 514275587 210821 14:27:19 [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.3.31-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=21 max_threads=153 thread_count=28 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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 = 0x0 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c61bb4ea9e] /usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55c61b5e5aef] sigaction.c:0(__restore_rt)[0x7f4736971630] :0(__GI_raise)[0x7f47365ca387] :0(__GI_abort)[0x7f47365cba78] /usr/sbin/mysqld(+0x962d9f)[0x55c61b789d9f] /usr/sbin/mysqld(handle_manager+0x1be)[0x55c61b3f4fae] pthread_create.c:0(start_thread)[0x7f4736969ea5] /lib64/libc.so.6(clone+0x6d)[0x7f47366929fd] 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. 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 31190 31190 processes Max open files 32187 32187 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 31190 31190 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 210821 14:27:20 mysqld_safe Number of processes running now: 0 210821 14:27:20 mysqld_safe WSREP: not restarting wsrep node automatically 210821 14:27:20 mysqld_safe mysqld from pid file /var/lib/mysql/ft-lb3.filmtotaal.nl.pid ended