-- Logs begin at Tue 2018-09-18 18:58:14 UTC, end at Wed 2018-10-03 19:30:22 UTC. --
Oct 02 16:49:41 cst4-db4.c.sharpspring-us.internal docker[25403]: 2018-10-02 16:49:41 38 [Note] Error reading relay log event: slave SQL thread was killed
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: mysqld: /mariadb/mysys/thr_mutex.c:388: safe_mutex_lock: Assertion `deadlock->count > 0' failed.
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: 181003  8:21:26 [ERROR] mysqld got signal 6 ;
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: This could be because you hit a bug. It is also possible that this binary
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: or one of the libraries it was linked against is corrupt, improperly built,
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: We will try our best to scrape up some info that will hopefully help
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: diagnose the problem, but since we have already crashed,
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: something is definitely wrong and this may fail.
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: Server version: 10.3.8-MariaDB-valgrind-max-debug-log
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: key_buffer_size=134217728
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: read_buffer_size=131072
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: max_used_connections=4
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: max_threads=3002
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: thread_count=26
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: It is possible that mysqld could use up to
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6733197 K  bytes of memory
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: Hope that's ok; if not, decrease some variables in the equation.
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: Thread pointer: 0x13b0d1ee28
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: Attempting backtrace. You can use the following information to find out
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: where mysqld died. If you see no messages after this, something went
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: terribly wrong...
Oct 03 08:21:26 cst4-db4.c.sharpspring-us.internal docker[25403]: stack_bottom = 0x58371d40 thread_stack 0x49000
Oct 03 08:21:27 cst4-db4.c.sharpspring-us.internal docker[25403]: /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x3d)[0x130b34d]
Oct 03 08:21:27 cst4-db4.c.sharpspring-us.internal docker[25403]: /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3b8)[0xa510d7]
Oct 03 08:21:28 cst4-db4.c.sharpspring-us.internal docker[25403]: /lib64/libpthread.so.0(+0xf6d0)[0x4e3c6d0]
Oct 03 08:21:28 cst4-db4.c.sharpspring-us.internal docker[25403]: /lib64/libc.so.6(gsignal+0x37)[0x6d54277]
Oct 03 08:21:28 cst4-db4.c.sharpspring-us.internal docker[25403]: /lib64/libc.so.6(abort+0x148)[0x6d55968]
Oct 03 08:21:28 cst4-db4.c.sharpspring-us.internal docker[25403]: linux/raise.c:56(__GI_raise)[0x6d4d096]
Oct 03 08:21:28 cst4-db4.c.sharpspring-us.internal docker[25403]: stdlib/abort.c:92(__GI_abort)[0x6d4d142]
Oct 03 08:21:29 cst4-db4.c.sharpspring-us.internal docker[25403]: /usr/local/mysql/bin/mysqld(safe_mutex_lock+0x4f4)[0x1312423]
Oct 03 08:21:29 cst4-db4.c.sharpspring-us.internal docker[25403]: /usr/local/mysql/bin/mysqld[0x6fbcb4]
Oct 03 08:21:29 cst4-db4.c.sharpspring-us.internal docker[25403]: log/log0recv.cc:3326(recv_recovery_from_checkpoint_start(unsigned long))[0x70f8f9]
Oct 03 08:21:29 cst4-db4.c.sharpspring-us.internal docker[25403]: /usr/local/mysql/bin/mysqld[0x939dcf]
Oct 03 08:21:29 cst4-db4.c.sharpspring-us.internal docker[25403]: /usr/local/mysql/bin/mysqld(handle_rpl_parallel_thread+0x75f)[0x93bfa7]
Oct 03 08:21:29 cst4-db4.c.sharpspring-us.internal docker[25403]: /lib64/libpthread.so.0(+0x7e25)[0x4e34e25]
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: /lib64/libc.so.6(clone+0x6d)[0x6e1cbad]
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: Trying to get some variables.
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: Some pointers may be invalid and cause the dump to abort.
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: Query (0x0):
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: Connection ID (thread ID): 44
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: Status: NOT_KILLED
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: 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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: information that should help you find out what is causing the crash.
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1== Process terminating with default action of signal 6 (SIGABRT): dumping core
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    at 0x6D54547: kill (syscall-template.S:81)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0xA514C1: handle_fatal_signal (signal_handler.cc:317)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x4E3C6CF: ??? (in /usr/lib64/libpthread-2.17.so)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D54276: raise (raise.c:56)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D55967: abort (abort.c:90)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D4D095: __assert_fail_base (assert.c:92)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D4D141: __assert_fail (assert.c:101)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x1312422: safe_mutex_lock (thr_mutex.c:388)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6FBCB3: inline_mysql_mutex_lock (mysql_thread.h:710)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x70F8F8: wait_for_commit::register_wait_for_prior_commit(wait_for_commit*) (sql_class.cc:7396)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x939DCE: register_wait_for_prior_event_group_commit(rpl_group_info*, rpl_parallel_entry*) (rpl_parallel.cc:299)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x93BFA6: handle_rpl_parallel_thread (rpl_parallel.cc:1189)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x4E34E24: start_thread (pthread_create.c:308)
Oct 03 08:21:30 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6E1CBAC: clone (clone.S:113)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: valgrind: m_mallocfree.c:307 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: valgrind: Heap block lo/hi size mismatch: lo = 1, hi = 4294967295.
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: This is probably caused by your program erroneously writing past the
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: end of a heap block and corrupting heap metadata.  If you fix any
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: invalid writes reported by Memcheck, this assertion failure will
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: probably go away.  Please try that before reporting this as a bug.
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: host stacktrace:
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    at 0x5800F3DD: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x5800F4F4: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x5800F681: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x5801C66D: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x580627C7: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x58013FB7: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x580140EC: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x580711C1: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x5807130A: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x5809A50D: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0xDEADBEEFDEADBEEE: ???
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: sched status:
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]:   running_tid=49
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: Thread 49: status = VgTs_Runnable (lwpid 9150)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    at 0x4C290CD: free (vg_replace_malloc.c:530)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6E8E26B: __libc_freeres (in /usr/lib64/libc-2.17.so)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x4A24749: _vgnU_freeres (vg_preloaded.c:77)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0xA514C1: handle_fatal_signal (signal_handler.cc:317)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x4E3C6CF: ??? (in /usr/lib64/libpthread-2.17.so)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D54276: raise (raise.c:56)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D55967: abort (abort.c:90)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D4D095: __assert_fail_base (assert.c:92)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6D4D141: __assert_fail (assert.c:101)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x1312422: safe_mutex_lock (thr_mutex.c:388)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6FBCB3: inline_mysql_mutex_lock (mysql_thread.h:710)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x70F8F8: wait_for_commit::register_wait_for_prior_commit(wait_for_commit*) (sql_class.cc:7396)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x939DCE: register_wait_for_prior_event_group_commit(rpl_group_info*, rpl_parallel_entry*) (rpl_parallel.cc:299)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x93BFA6: handle_rpl_parallel_thread (rpl_parallel.cc:1189)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x4E34E24: start_thread (pthread_create.c:308)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: ==1==    by 0x6E1CBAC: clone (clone.S:113)
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: Note: see also the FAQ in the source distribution.
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: It contains workarounds to several common problems.
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: In particular, if Valgrind aborted or crashed after
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: identifying problems in your program, there's a good chance
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: that fixing those problems will prevent Valgrind aborting or
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: crashing, especially if it happened in m_mallocfree.c.
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: If that doesn't help, please report this bug to: www.valgrind.org
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: In the bug report, send all the above text, the valgrind
Oct 03 08:24:43 cst4-db4.c.sharpspring-us.internal docker[25403]: version, and what OS and version you are using.  Thanks.
Oct 03 08:24:46 cst4-db4.c.sharpspring-us.internal systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 08:24:46 cst4-db4.c.sharpspring-us.internal systemd[1]: mariadb.service: Failed with result 'exit-code'.
Oct 03 08:25:16 cst4-db4.c.sharpspring-us.internal systemd[1]: mariadb.service: Service hold-off time over, scheduling restart.
Oct 03 08:25:16 cst4-db4.c.sharpspring-us.internal systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 1.
Oct 03 08:25:16 cst4-db4.c.sharpspring-us.internal systemd[1]: Stopped mariadb.