| Bug #93719 | `opt_event_scheduler == Events::EVENTS_ON || opt_event_scheduler == Events::EVEN | ||
|---|---|---|---|
| Submitted: | 21 Dec 2018 12:24 | Modified: | 2 Feb 2019 16:14 |
| Reporter: | Roel Van de Paar | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Options | Severity: | S6 (Debug Builds) |
| Version: | 8.0.13 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | debug | ||
[21 Dec 2018 21:15]
MySQL Verification Team
Thank you for the bug report. Verified on debug built only: miguel@tikal:~/bug $ /home/miguel/bug/8.0/bin/mysqld --no-defaults --basedir=/home/miguel/bug/8.0 --datadir=/home/miguel/bug/8.0/data --event-scheduler=2 2018-12-21T21:07:53.816300Z 0 [System] [MY-010116] [Server] /home/miguel/bug/8.0/bin/mysqld (mysqld 8.0.15) starting as process 7340 2018-12-21T21:07:55.645165Z 0 [System] [MY-010229] [Server] Starting crash recovery... 2018-12-21T21:07:55.656698Z 0 [System] [MY-010232] [Server] Crash recovery finished. 2018-12-21T21:07:55.880517Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 2018-12-21T21:07:55.940106Z 0 [System] [MY-010931] [Server] /home/miguel/bug/8.0/bin/mysqld: ready for connections. Version: '8.0.15' socket: '/tmp/mysql.sock' port: 3306 Source distribution. 2018-12-21T21:07:56.080285Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/tmp/mysqlx.sock' bind-address: '::' port: 33060 ============================================================================================================================== miguel@tikal:~/bug $ /home/miguel/bug/8.0/bin/mysqld --no-defaults --basedir=/home/miguel/bug/8.0 --datadir=/home/miguel/bug/8.0/data --event-scheduler=2 mysqld: /home/miguel/bug/2018DEC11/mysql-8.0/sql/events.cc:940: static bool Events::init(bool): Assertion `opt_event_scheduler == Events::EVENTS_ON || opt_event_scheduler == Events::EVENTS_OFF' failed. 21:10:25 UTC - 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67884 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x5590a5c7ca70 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 = 7ffe954ae658 thread_stack 0x46000 /home/miguel/bug/8.0/bin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x55) [0x5590a25fa3d1] /home/miguel/bug/8.0/bin/mysqld(handle_fatal_signal+0x3f2) [0x5590a12b1487] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12dd0) [0x7fe8fa33cdd0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7fe8f98e1077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7fe8f98c2535] /lib/x86_64-linux-gnu/libc.so.6(+0x2240f) [0x7fe8f98c240f] /lib/x86_64-linux-gnu/libc.so.6(+0x32142) [0x7fe8f98d2142] /home/miguel/bug/8.0/bin/mysqld(Events::init(bool)+0xe9) [0x5590a12ae3d5] /home/miguel/bug/8.0/bin/mysqld(mysqld_main(int, char**)+0x255a) [0x5590a0f6c94c] /home/miguel/bug/8.0/bin/mysqld(main+0x20) [0x5590a0f5a8c5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fe8f98c409b] /home/miguel/bug/8.0/bin/mysqld(_start+0x2a) [0x5590a0f5a7ea] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): Connection ID (thread ID): 0 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. miguel@tikal:~/bug $
[2 Feb 2019 16:14]
Paul DuBois
Posted by developer: Fixed in 8.0.16. For debug builds, starting the server with --event-scheduler=DISABLED could result in an assertion being raised for certain events.
Description: mysqld: /git/MS-8.0-trunk_dbg/sql/events.cc:926: static bool Events::init(bool): Assertion `opt_event_scheduler == Events::EVENTS_ON || opt_event_scheduler == Events::EVENTS_OFF' failed. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill (threadid=<optimized out>, signo=6) at ../sysdeps/unix/sysv/linux/pthread_kill.c:57 57 ../sysdeps/unix/sysv/linux/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f252caa9200 (LWP 2477))] (gdb) bt #0 __pthread_kill (threadid=<optimized out>, signo=6) at ../sysdeps/unix/sysv/linux/pthread_kill.c:57 #1 0x0000561d36a246b7 in my_write_core (sig=6) at /git/MS-8.0-trunk_dbg/mysys/stacktrace.cc:278 #2 0x0000561d356d5880 in handle_fatal_signal (sig=6) at /git/MS-8.0-trunk_dbg/sql/signal_handler.cc:249 #3 <signal handler called> #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x00007f252a63d801 in __GI_abort () at abort.c:79 #6 0x00007f252a62d39a in __assert_fail_base (fmt=0x7f252a7b47d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x561d37adb370 "opt_event_scheduler == Events::EVENTS_ON || opt_event_scheduler == Events::EVENTS_OFF", file=file@entry=0x561d37adb170 "/git/MS-8.0-trunk_dbg/sql/events.cc", line=line@entry=926, function=function@entry=0x561d37adbb00 <Events::init(bool)::__PRETTY_FUNCTION__> "static bool Events::init(bool)") at assert.c:92 #7 0x00007f252a62d412 in __GI___assert_fail ( assertion=0x561d37adb370 "opt_event_scheduler == Events::EVENTS_ON || opt_event_scheduler == Events::EVENTS_OFF", file=0x561d37adb170 "/git/MS-8.0-trunk_dbg/sql/events.cc", line=926, function=0x561d37adbb00 <Events::init(bool)::__PRETTY_FUNCTION__> "static bool Events::init(bool)") at assert.c:101 #8 0x0000561d356d25b7 in Events::init (opt_noacl_or_bootstrap=false) at /git/MS-8.0-trunk_dbg/sql/events.cc:925 #9 0x0000561d3539909b in mysqld_main (argc=11, argv=0x7f2529c20120) at /git/MS-8.0-trunk_dbg/sql/mysqld.cc:6498 #10 0x0000561d35386cfa in main (argc=11, argv=0x7ffe9ab97ee8) at /git/MS-8.0-trunk_dbg/sql/main.cc:30 How to repeat: --event-scheduler=2 option to mysqld