- Package:
- src:mariadb
- Source:
- src:mariadb
- Submitter:
- Lucas Nussbaum
- Date:
- 2025-12-08 19:19:01 UTC
- Severity:
- normal
- Tags:
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): The full build log is available from: http://qa-logs.debian.net/2023/09/25/mariadb_10.11.4-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Hi! The relevant lines from log seems to be: ... What might have been holding port 16020 during the test run?
I saw this now after 1:10.11.5-2 upload on multiple builders. Snippets from logs https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=powerpc&ver=1%3A10.11.5-2&stamp=1696735216&raw=0 main.failed_auth_unixsocket w13 [ fail ] Test ended at 2023-10-08 03:17:49 CURRENT_TEST: main.failed_auth_unixsocket Failed to start mysqld.1 mysqltest failed but provided no output - saving '/<<PKGBUILDDIR>>/builddir/mysql-test/var/13/log/main.failed_auth_unixsocket/' to '/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/main.failed_auth_unixsocket/' Retrying test main.failed_auth_unixsocket, attempt(2/3)... worker[13] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: main.failed_auth_unixsocket 2023-10-08 3:17:49 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:49 0 [ERROR] Do you already have another server running on port: 16120 ? 2023-10-08 3:17:49 0 [ERROR] Aborting main.password_expiration_unix_socket w13 [ fail ] Test ended at 2023-10-08 03:18:16 CURRENT_TEST: main.password_expiration_unix_socket Failed to start mysqld.1 mysqltest failed but provided no output - skipping '/<<PKGBUILDDIR>>/builddir/mysql-test/var/13/log/main.password_expiration_unix_socket/' Retrying test main.password_expiration_unix_socket, attempt(2/3)... main.order_by w14 [ pass ] 3306 worker[13] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: main.password_expiration_unix_socket 2023-10-08 3:18:16 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:16 0 [ERROR] Do you already have another server running on port: 16120 ? 2023-10-08 3:18:16 0 [ERROR] Aborting main.ssl_cipher w15 [ fail ]main.ssl_cipher w15 [ fail ] ... 2023-10-08 3:18:22 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:22 0 [ERROR] Do you already have another server running on port: 16140 ? main.func_int w13 [ fail ]main.func_int w13 [ fail ] ... 2023-10-08 3:18:42 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:42 0 [ERROR] Do you already have another server running on port: 16120 ? main.plugin_loaderr w6 [ fail ] ... 2023-10-08 3:18:59 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:59 0 [ERROR] Do you already have another server running on port: 16100 ? etc Failing test(s): main.failed_auth_unixsocket main.password_expiration_unix_socket main.ssl_cipher main.func_int main.grant_4332 main.plugin_loaderr main.func_isnull main.grant_binlog_replay main.func_json main.grant_cache_no_prot https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64&ver=1%3A10.11.5-2&stamp=1696735349&raw=0 main.connect w3 [ fail ] Test ended at 2023-10-08 03:17:18 CURRENT_TEST: main.connect Failed to start mysqld.1 mysqltest failed but provided no output - saving '/<<PKGBUILDDIR>>/builddir/mysql-test/var/3/log/main.connect/' to '/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/main.connect/' Retrying test main.connect, attempt(2/3)... worker[3] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: main.connect 2023-10-08 3:17:18 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:18 0 [ERROR] Do you already have another server running on port: 16140 ? 2023-10-08 3:17:18 0 [ERROR] Aborting main.innodb_load_xa w5 [ fail ] .. 2023-10-08 3:17:33 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:33 0 [ERROR] Do you already have another server running on port: 16120 ? main.flush_block_commit_notembedded 'innodb' w3 [ fail ] ... 2023-10-08 3:17:45 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:45 0 [ERROR] Do you already have another server running on port: 16140 ? main.long_unique_innodb 'innodb' w9 [ fail ] ... 2023-10-08 3:19:29 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:19:29 0 [ERROR] Do you already have another server running on port: 16260 ? Both builds above ran on builder 'blaauw' with kernel Linux 6.5.0-1-powerpc64 #1 SMP Debian 6.5.3-1 (2023-09-13) ppc64 (ppc64) I have not been able to reproduce this on any Salsa-CI builders or on Launchpad.
I restarted the build for powerpc yesterday, and it did not run into reserved ports issue and build passed. I suspect that this is because the ppc64 build (which runs on the same builder 'blaauw' was not running in parallel and thus the two build jobs were not competing for the same ports on that host. A later restart of ppc64 when the powerpc build had completed likewise did not run into reserved ports issues. Thus I'd say this is a Debian builder problem. The builds should be running inside a container or something so that they can't affect each other.
Hi, I could reproduce the issue again, and I was not running anything else on the node. Lucas
Hi, The ci.debian.net results for mariadb seem to be very flaky lately (on amd64 they fail roughly 9/10) since version 1:10.11.6-1. Might be related (although the failure is different). i386 and arm64 seem to be exceptions. https://ci.debian.net/packages/m/mariadb/testing/amd64/ Paul
Hi! No - the current CI failures for MariaDB are unrelated and not due to this local port issue. (Current MariaDB failures are partly due to OpenSSL API text change in https://github.com/openssl/openssl/commit/81b741f68984 and partfly due to upstream bug https://jira.mariadb.org/browse/MDEV-32843 - both issues has known fixes, just a matter of dev time to commit and push)
at https://tracker.debian.org/pkg/mariadb: autopkgtest for mariadb/1:10.11.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass The 'reserved port' issue has not been fixed, or at least I am not aware of any fix. However the issue was sporadic and I have not seen it in late 2023 or 2024 on any buildd or ci.debian.org log.
In https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=amd64&ver=1%3A11.4.5-2%7Eexp1&stamp=1740281411&raw=0 these were passing: main.bind_address_resolution w3 [ pass ] 25 main.bind_multiple_addresses_resolution w3 [ pass ] 34 Could be sporadic. I am re-enabling the tests permanently to see if this resurfaces randomly in the future again. For reference, this is tracked in Debian as * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052838 * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077524 * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091557 (they are all the same issue but every time it occurs a new is filed) Upstream issue: https://jira.mariadb.org/browse/MDEV-34788