Date: Thu, 14 Apr 2016 17:45:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 208805] databases/mysql57-server: SIGSEGV when doing binary upgrade from databases/mysql56-server Message-ID: <bug-208805-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208805 Bug ID: 208805 Summary: databases/mysql57-server: SIGSEGV when doing binary upgrade from databases/mysql56-server Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: fredrik.eriksson@loopia.se CC: ale@FreeBSD.org, mokhi64@gmail.com CC: ale@FreeBSD.org, mokhi64@gmail.com Created attachment 169316 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D169316&action= =3Dedit backtrace of crash I've encountered this bug on two servers when testing binary upgrades from 5.6.27 to 5.7.10. Each server has 9500+ databases with 200GB+ worth of data. mysqld crashes with a segfault after a while when running mysql_upgrade or mysqlcheck --check-upgrade. I can reproduce it every time, and it seems lik= e it happens after X number of databases/tables/GB since it usually crashes arou= nd the same database. I've attached a backtrace (that I got using gdb and mysql with debugging symbols). I think this is an upstream bug, but I start here since I've only tested it on FreeBSD (and 5.7.10 is not the latest upstream version). Let me know if there is something more I should test. --=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-208805-13>