Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.4.12
-
None
Description
While updating the official Debian packaging and working on release 10.4.12 I noticed that the mtr testsuite in the s390x build on Launchpad failed on all tests, indicating that mysqld completely crashes.
This was working before, so I did many builds and managed to narrow it down to a SSL/GnuTLS issue.
Build with external libssl-dev passes and tests run OK:
https://launchpadlibrarian.net/464501349/buildlog_ubuntu-focal-s390x.mariadb-10.4_1%3A10.4.12-1~ubuntu20.04.1~1581415272.6e13abad1_BUILDING.txt.gz
However after activating the source embedded GnuTLS the mysqld starts to crash on all tests:
worker[3] mysql-test-run: WARNING: Process [mysqld.1 - pid: 27108, winpid: 27108, exit: 256] died after mysql-test-run waited 0.9 seconds for /<<PKGBUILDDIR>>/builddir/mysql-test/var/3/run/mysqld.1.pid to be created.
|
|
main.ipv4_as_ipv6 w3 [ fail ]
|
Test ended at 2020-02-11 11:20:41
|
|
CURRENT_TEST: main.ipv4_as_ipv6
|
|
|
Failed to start mysqld.1
|
mysqltest failed but provided no output
|
...
|
worker[2] mysql-test-run: WARNING: Process [mysqld.1 - pid: 27114, winpid: 27114, exit: 256] died after mysql-test-run waited 1.1 seconds for /<<PKGBUILDDIR>>/builddir/mysql-test/var/2/run/mysqld.1.pid to be created.
|
main.stat_tables_rbr 'innodb' w2 [ fail ]
|
Test ended at 2020-02-11 11:20:41
|
|
CURRENT_TEST: main.stat_tables_rbr
|
|
|
Failed to start mysqld.1
|
mysqltest failed but provided no output
|
The change between those builds was:
https://salsa.debian.org/mariadb-team/mariadb-10.4/commit/0790a802b55adcf95e41e695185e50345ac9339f
Switching to OpenSSL in official Debian is not an option due to licensing views. MariaDB has been with GnuTLS and fully working in latest 10.3.22, 10.1, 10.0 etc in Debian.
This is now a regression in 10.4 series. Please help me figure out what it is.
Attachments
Issue Links
- relates to
-
MDEV-18531 Use WolfSSL instead of YaSSL as "bundled" SSL
- Closed