Sometimes the MySQL 5.7.13 builds on Ubuntu 16.04 are failing with "Lost connection to MySQL server during query" because the MySQL server restarts during the tests. I wonder if anyone has an idea about how to solve this. Looking through the MySQL error log, I think this is the root cause:
2016-08-01T23:02:56.636617Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung. 2016-08-01 23:02:56 0x7f5fb75d8700 InnoDB: Assertion failure in thread 140049074980608 in file ut0ut.cc line 920 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 23:02:56 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=536870912 read_buffer_size=131072 max_used_connections=4 max_threads=151 thread_count=4 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 584285 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 = 0 thread_stack 0x200000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe7bdab] /usr/sbin/mysqld(handle_fatal_signal+0x489)[0x783759] /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0)[0x7f60131dc3d0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f6012596418] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f601259801a] /usr/sbin/mysqld[0x759764] /usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x145)[0x110c905] /usr/sbin/mysqld(srv_error_monitor_thread+0xe2d)[0x10aa34d] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f60131d26fa] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6012667b5d] 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. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3f787f25-2e3f-49b1-b6a3-7a3411e70a9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
