Date: Wed, 13 Jan 2021 10:13:23 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 252636] databases/mysql57-server Message-ID: <bug-252636-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252636 Bug ID: 252636 Summary: databases/mysql57-server Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: joneum@FreeBSD.org Reporter: jorritdeklerk@gmail.com Flags: maintainer-feedback?(joneum@FreeBSD.org) Assignee: joneum@FreeBSD.org I don't know if this problem is with mysql57-server OR with google-perftool= s. Because of swap-problems I'm using libtcmalloc (as described in https://forums.freebsd.org/threads/freebsd-12-x-and-mysql-5-7-and-importing= -file-with-lots-of-small-lines-exhaust-ram-and-swap.72733/) with mysql57-server-5.7.32 on 12.2-RELEASE-p2. However, since upgrading to google-perftools-2.8.1 mysql-server refuses to start. Happened on production server. Could repeat it on development server after upgrading to same versions mysql-server/google-perftools. MySQL error log: 2021-01-13T09:55:39.254557Z 0 [Note] InnoDB: Last MySQL binlog file positio= n 0 432222, file name mysql-bin.000510 09:55:39 UTC - mysqld got signal 10 ; 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=3D67108864 read_buffer_size=3D131072 max_used_connections=3D0 max_threads=3D151 thread_count=3D0 connection_count=3D0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =3D 125= 490 K=20 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 =3D 0 thread_stack 0x40000 0x1452188 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld 0x13ad15e <handle_fatal_signal+0x2be> at /usr/local/libexec/mysqld 0x801f28b70 <_pthread_sigmask+0x530> at /lib/libthr.so.3 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. 2021-01-13T09:55:39.6NZ mysqld_safe mysqld from pid file /var/db/mysql/bsdvm03.pid ended --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252636-7788>