[Bug 2019203] Re: mysql 8.0.33 binary crashes on startup on armhf

Tue Jun 13 05:29:49 UTC 2023

Just checked past build logs
https://launchpadlibrarian.net/665338538/buildlog_ubuntu-mantic-
armhf.mysql-8.0_8.0.33-0ubuntu2_BUILDING.txt.gz which show.

```
RULES.override_dh_auto_test
touch builddir/mysql-test/skiplist
# Tests that are known to be unstable on all platforms are skipped
# http://bugs.mysql.com/bug.php?id=83340
echo "main.xa_prepared_binlog_off	: BUG#00000 - unstable test" >> builddir/mysql-test/skiplist
echo "main.mysql_client_test		: BUG#100274 - unstable test" >> builddir/mysql-test/skiplist
echo "main.type_float			: BUG#92375 - fails on ppc64el. Ref https://bugs.mysql.com/bug.php?id=92375" >> builddir/mysql-test/skiplist
echo "main.type_newdecimal		: BUG#92375 - Same as above" >> builddir/mysql-test/skiplist
echo "main.type_ranges			: BUG#92375 - Same as above" >> builddir/mysql-test/skiplist
# https://bugs.mysql.com/bug.php?id=86608
echo "main.mysqlpump_basic		: BUG#00000 - needs openssl with zlib" >> builddir/mysql-test/skiplist
# Test is broken for 32bit. Fixed upstream, so remove in 8.0.12+
echo "main.window_functions_explain	: BUG#00000 -  broken on i386" >> builddir/mysql-test/skiplist
# New test in 8.0.26, needs investigation
echo "main.slow_log			: BUG#00000 -  broken" >> builddir/mysql-test/skiplist
# Test is broken for 32bit.
echo "main.index_merge_myisam		: BUG#00000 -  broken on i386" >> builddir/mysql-test/skiplist
# Test is broken on Mantic
echo "main.derived_condition_pushdown	: BUG#00000 -  broken on mantic" >> builddir/mysql-test/skiplist
# Skip replication tests since they are timing sensitive and may
# result in false positives.
cd builddir/mysql-test && ./mtr --suite-timeout=600 --testcase-timeout=60 --report-unstable-tests --parallel=4 --skip-rpl --suite=main --force --skip-test-list=./skiplist || true ;
Logging: /<<PKGBUILDDIR>>/mysql-test/mysql-test-run.pl  --suite-timeout=600 --testcase-timeout=60 --report-unstable-tests --parallel=4 --skip-rpl --suite=main --force --skip-test-list=./skiplist
2023-05-09T14:58:46Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=195a631af53dd4598a337c119fb58728b7bc1c74
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 0x100000
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2b) [0x1bec0bc]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(print_fatal_signal(int)+0x29d) [0x10c1ba2]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(handle_fatal_signal+0x71) [0x10c1c9e]
/lib/arm-linux-gnueabihf/libc.so.6(+0x2d750) [0xf6d49750]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(memory::Aligned_atomic<long>::Aligned_atomic()+0x51) [0x199b49a]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(Delegate::Delegate(unsigned int)+0x3b) [0x199b6c4]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(delegates_init()+0x37) [0x199b804]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(+0x8ec92c) [0xf2392c]
/<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(mysqld_main(int, char**)+0x1959) [0xf2822a]
/lib/arm-linux-gnueabihf/libc.so.6(+0x1d7da) [0xf6d397da]
/lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x5d) [0xf6d3987e]
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.
mysql-test-run: *** ERROR: Could not find version of MySQL
```

However the MySQL packaging in Ubuntu is configured to disregard the
results of the MTR run.

** Bug watch added: MySQL Bug System #83340
   http://bugs.mysql.com/bug.php?id=83340

** Bug watch added: MySQL Bug System #92375
   http://bugs.mysql.com/bug.php?id=92375

** Bug watch added: MySQL Bug System #86608
   http://bugs.mysql.com/bug.php?id=86608

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2019203

Title:
  mysql 8.0.33 binary crashes on startup on armhf

Status in MySQL Server:
  Unknown
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in glibc source package in Focal:
  Invalid
Status in linux source package in Focal:
  Incomplete
Status in mysql-8.0 source package in Focal:
  Fix Released
Status in glibc source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in mysql-8.0 source package in Jammy:
  Fix Released
Status in glibc source package in Kinetic:
  Invalid
Status in linux source package in Kinetic:
  Incomplete
Status in mysql-8.0 source package in Kinetic:
  Fix Released
Status in glibc source package in Lunar:
  Invalid
Status in linux source package in Lunar:
  Incomplete
Status in mysql-8.0 source package in Lunar:
  Fix Released
Status in glibc source package in Mantic:
  Invalid
Status in linux source package in Mantic:
  Incomplete
Status in mysql-8.0 source package in Mantic:
  Fix Released

Bug description:
  From mantic autopkgtests:

  Setting up mysql-server-8.0 (8.0.33-0ubuntu2) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  ERROR: Unable to start MySQL server:
  2023-05-09T17:23:22Z UTC - mysqld got signal 11 ;
  Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
  BuildID[sha1]=facf2109b23102b169b11737a1fc4bd99de4be1b
  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 0x100000
  /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2b) [0x205e0bc]
  /usr/sbin/mysqld(print_fatal_signal(int)+0x29d) [0x1533ba2]
  /usr/sbin/mysqld(handle_fatal_signal+0x71) [0x1533c9e]
  /lib/arm-linux-gnueabihf/libc.so.6(+0x2d750) [0xf6e7b750]
  /usr/sbin/mysqld(memory::Aligned_atomic<long>::Aligned_atomic()+0x51) [0x1e0d49a]
  /usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x3b) [0x1e0d6c4]
  /usr/sbin/mysqld(delegates_init()+0x37) [0x1e0d804]
  /usr/sbin/mysqld(+0x8ec92c) [0x139592c]
  /usr/sbin/mysqld(mysqld_main(int, char**)+0x1959) [0x139a22a]
  /lib/arm-linux-gnueabihf/libc.so.6(+0x1d7da) [0xf6e6b7da]
  /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x5d) [0xf6e6b87e]
  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.
  Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues.
  Once the problem is resolved, run apt-get --fix-broken install to retry.
  dpkg: error processing package mysql-server-8.0 (--configure):
   installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/2019203/+subscriptions