Bug#1080087: docker-compose: broken on debian 11 (Unsupported config option)
Package: docker-compose Version: 1.25.0-1 Dear Maintainer, the docker-compose command seems to be broken on Debian old stable (Debian 11), see bellow: | $ docker run -it debian:11 bash | root@af06b2465b19:~# docker-compose --version | docker-compose version 1.25.0, build unknown | root@af06b2465b19:~# cat >docker-compose.yml <<-EOF | --- | services: | app: | image: alpine:latest | EOF | root@af06b2465b19:~# docker-compose config | ERROR: The Compose file './docker-compose.yml' is invalid because: | Unsupported config option for services: 'app' A workaround is to install docker-compose from backports: | root@af06b2465b19:~# apt -t bullseye-backports install docker-compose | root@af06b2465b19:~# docker-compose --version | docker-compose version 1.27.4, build unknown | root@af06b2465b19:~# docker-compose config | services: | app: | image: alpine:latest | version: '3.9' -- System Information: Debian Release: 11.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Versions of packages docker-compose depends on: ii python3 3.9.2-3 ii python3-cached-property 1.5.2-1 ii python3-distutils3.9.2-1 ii python3-docker 4.1.0-1.2 ii python3-dockerpty0.4.1-2 ii python3-docopt 0.6.2-3 ii python3-jsonschema 3.2.0-3 ii python3-requests 2.25.1+dfsg-2 ii python3-six 1.16.0-2 ii python3-texttable1.6.3-2 ii python3-websocket0.57.0-1 ii python3-yaml 5.3.1-5 Versions of packages docker-compose recommends: ii docker.io 20.10.5+dfsg1-1+deb11u2 docker-compose suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1039707: [debian-mysql] Bug#1039707: /usr/bin/mysqld_safe: missing from package
Hi Marc! > I think if mariadb-server-10.5 is incompatible with bookworms mariadb > server, it should be uninstalled on upgrades. Unless I am missing something, this should be the case already, see bellow (dist upgrade from debian 11): | faust@debian11:~$ sudo apt upgrade | faust@debian11:~$ dpkg -l | grep mariadb | ii libdbd-mariadb-perl 1.22-1+b1 amd64Perl5 database interface to the MariaDB/MySQL databases | ii libmariadb3:amd641:10.11.3-1 amd64MariaDB database client library | ii mariadb-client-10.5 1:10.5.19-0+deb11u2 amd64MariaDB database client binaries | ii mariadb-client-core-10.5 1:10.5.19-0+deb11u2 amd64MariaDB database core client binaries | ii mariadb-common 1:10.11.3-1 all MariaDB common configuration files | ii mariadb-server 1:10.5.19-0+deb11u2 all MariaDB database server (metapackage depending on the latest version) | ii mariadb-server-10.5 1:10.5.19-0+deb11u2 amd64MariaDB database server binaries | ii mariadb-server-core-10.5 1:10.5.19-0+deb11u2 amd64MariaDB database core server files | faust@debian11:~$ sudo apt full-upgrade | Reading package lists... Done | Building dependency tree... Done | Reading state information... Done | Calculating upgrade... Done | The following packages were automatically installed and are no longer required: | libaio1 libcbor0 libicu67 libperl5.32 liburing1 libusb-0.1-4 perl-modules-5.32 | Use 'sudo apt autoremove' to remove them. | The following packages will be REMOVED: | libsemanage1 linux-image-5.10.0-22-amd64 linux-image-5.10.0-23-amd64 mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 | The following NEW packages will be installed: | libdaxctl1 liblzo2-2 libndctl6 libpmem1 libsemanage2 libsepol2 mariadb-client mariadb-client-core mariadb-plugin-provider-bzip2 mariadb-plugin-provider-lz4 | mariadb-plugin-provider-lzma mariadb-plugin-provider-lzo mariadb-plugin-provider-snappy mariadb-server-core pv | The following packages will be upgraded: | libsemanage-common mariadb-server passwd | 3 upgraded, 15 newly installed, 7 to remove and 0 not upgraded. | Need to get 16.4 MB of archives. | After this operation, 600 MB disk space will be freed. | Do you want to continue? [Y/n] -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1039705: [debian-mysql] Bug#1039705: mariadb-server-core: fails to start via systemd due to lacking permissions on /run
Hi Marc! I am not able to reproduce this, could you please show me your steps? Here are mine: 1/ install fresh debian 11 VM; 2/ install mariadb-server (10.5.19); 3/ make sure it's started (sudo mariadb); 4/ sed bullseye/bookworm in sources.list 5/ upgrade (sudo apt upgrade); 6/ full-upgrade (sudo apt full-upgrade); 7/ make sure mariadb 10.11 is started. Also, FYI we implemented a dist-upgrade in CI (bookworm > sid) to cover this kind of scenario, it was not easy to do in Docker though, see https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/18 but it should now be ok with https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/103a3486717161a77e7b49c127b60b01fb39b267. If there is something that you think we should improve to test your case, let me know. -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1042454: [debian-mysql] Bug#1042454: mariadb-server ignores bind-address
Hi! I am not able to reproduce this. Can you make sure that there is no other "bind-address" directive in any configuration file. For instance by verifying the output of: | sudo grep -r bind-address /etc/mysql/* Regards, -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1037556: [debian-mysql] Bug#1037556: mariadb-server-10.5: mariadb should restart automatically upon crashing
Control: tags -1 wontfix Hi Martin! This is not a good practice to automatically restart a service that crashed. I understand that it can be convenient or useful as a temporary workaround if you have no time to debug it. But I really recommend you to take a moment to understand why it crashes. So, we won't certainly not change that default behavior. That said, you can very easily override the default systemd options, see "Example 2. Overriding vendor settings" in https://www.freedesktop.org/software/systemd/man/systemd.unit.html. Regards, -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1032407: [debian-mysql] Bug#1032407: Cannot start mariadb-server unless manually mkdir -p /var/lib/mysql
Hi Thomas! This seems like a normal behavior to me, at least this is what the /etc/mysql/mariadb.conf.d/50-server.cnf says: | # Note: The configured log file or its directory need to be created | # and be writable by the mysql user, e.g.: | # $ sudo mkdir -m 2750 /var/log/mysql | # $ sudo chown mysql /var/log/mysql Also, I am not able to reproduce this on a fresh container: | ❯ podman run --name 1032407 --rm -d fauust/docker-systemd:debian-12 | ❯ podman exec -it 1032407 bash -c "apt-get update && apt-get install -y mariadb-server && systemctl start mariadb && systemctl status mariadb" Can you maybe point me to the steps that makes you think that there is a problem? -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1027337: [debian-mysql] Bug#1027337: Bug#1027337: mariadb-server-10.5: Huge increase in memory consumption (leak?) since upgrade from 10.5.15 to 10.5.18
Hi Matteo! I am not in charge of doing uploads to Debian FTP so, I don't know. @Otto do you know when 10.5.19 will be uploaded? Regards, -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1031860: [debian-mysql] Bug#1031860: kmail with akonadi stops working after security-upgrade of '*mariadb*'
Hi Markus! No idea, Otto, can you give us some guidance here? Regards, -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1031860: [debian-mysql] Bug#1031860: kmail with akonadi stops working after security-upgrade of '*mariadb*'
Thank you for your report! Can you check if this looks similar to #1031770 and #1031863. -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1032047: [debian-mysql] Bug#1032047: mariadb-server: Preinst fails if user has mariadb running while system service stopped.
Hi! Not sure if that helps but there is also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031860 that seems to be also relevant to that bug report. Cheers! -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#970045: [debian-mysql] Bug#970045: Bug#970045: galera-4: Use user "_galera" instead of "nobody" to run the daemon
Hi Otto! > According to > https://www.debian.org/doc/debian-policy/ch-opersys.html#users-and-groups > it seems the proper solution would be to have a new user "_galera" for Can you point me to the exact sentence that recommend '_galera' (with underscore). WIP in: - https://salsa.debian.org/mariadb-team/galera-4/-/merge_requests/8 - https://github.com/codership/galera/pull/633 Cheers! -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1025784: [debian-mysql] Bug#1025784: Acknowledgement (mariadb-server-core-10.6: Can't connect to local server through socket '/run/mysqld/mysqld.sock' (111))
Control: close -1 #1025784 is duplicate of #1022994. Closing as I can't merge this to #1022994. signature.asc Description: PGP signature
Bug#1025784: [debian-mysql] Bug#1025784: Acknowledgement (mariadb-server-core-10.6: Can't connect to local server through socket '/run/mysqld/mysqld.sock' (111))
Control: merge -1 1022994 signature.asc Description: PGP signature
Bug#1025784: [debian-mysql] Bug#1025784: Acknowledgement (mariadb-server-core-10.6: Can't connect to local server through socket '/run/mysqld/mysqld.sock' (111))
Hi Tim! Tim McConnell , 10/01/2023 – 15:49:20 (-0600): > Hi Faustin, > Steps to recreate: > 1.Install Mariadb client/server > 2. Attempt to run mysql -u root -p > 3. fail to be able to login On a clean installation, I can't reproduce the problem with those steps and this is heavily tested in our CI pipelines. So, my best guess is that there is something else with your setup that caused the problem. I can't be sure but what you described also in the mailing list makes me think of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022994, is it possible that you had libpam-tmpdir package installed before installing MariaDB? You can verify with `dpkg -l | grep libpam-tmpdir`. If that's the case, then this will be fixed in the next release, see: https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/cde8b8613e08ecb8d5f4a5de09d34418576d3040 And #1025784 should be marked as duplicate of #1022994. Cheers! -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1027337: [debian-mysql] Bug#1027337: Bug#1027337: mariadb-server-10.5: Huge increase in memory consumption (leak?) since upgrade from 10.5.15 to 10.5.18
Hi! Xan Charbonnet , 10/01/2023 – 10:07:02 (-0600): > It looks to me like https://jira.mariadb.org/browse/MDEV-29988 is very > likely to be the issue we're seeing. Fortunately (if I'm interpreting > upstream's JIRA correctly), it looks like a fix exists and will be included > in 10.5.19. Indeed, MDEV-29988 is fixed in the next release. > From their release history, 10.5.19 can be expected in early February. Exact, maybe even by the end of January. > Probably what I will do is downgrade all machines to 10.5.15 and look > forward to the Debian package of 10.5.19, which hopefully will not be long > after the upstream release. I already sent an email to Otto about this critical issue and hopefully, 10.5.19 will hit Debian soon after it's GA upstream. Cheers! -- Faustin signature.asc Description: PGP signature
Bug#1027337: [debian-mysql] Bug#1027337: mariadb-server-10.5: Huge increase in memory consumption (leak?) since upgrade from 10.5.15 to 10.5.18
Hi, first of all, thank you all for the excellent (and detailed) report! I don't see anything that could be related with Debian packaging of MariaDB and so I suggest you check directly upstream. I have searched into https://jira.mariadb.org and the closest report that I can come with is https://jira.mariadb.org/browse/MDEV-29988. I do not forward this bug report to it because I am not sure that this is the same problem. There is also https://jira.mariadb.org/browse/MDEV-29097 that may give some ideas on how to find a workaround until the next release happen. Cheers! -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1025784: [debian-mysql] Bug#1025784: Acknowledgement (mariadb-server-core-10.6: Can't connect to local server through socket '/run/mysqld/mysqld.sock' (111))
Hi Tim! Can you explain the steps you followed so I can try to reproduce this? From your logs, it seems that your system tables are missing (mysql.db) so it may be a problem with your datadir (normally /var/lib/mysql). You may want to recreate those tables, see: https://mariadb.com/kb/en/installing-system-tables-mysql_install_db/ Before touching your datadir, please make sure that you have backups. Cheers! -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1026353: [debian-mysql] Bug#1026353: mariadb-server: mariadb does not start after bullseye point release 11.6
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-30092 signature.asc Description: PGP signature
Bug#1022994: [debian-mysql] Bug#1022994: mariadb-server: Initial DB creation fails with libpam-tmpdir installed
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-29910 signature.asc Description: PGP signature
Bug#1022994: [debian-mysql] Bug#1022994: mariadb-server: Initial DB creation fails with libpam-tmpdir installed
Control: -1 forwarded https://jira.mariadb.org/browse/MDEV-29910 signature.asc Description: PGP signature
Bug#1020301: [debian-mysql] Bug#1020301: mariadb-server-10.3: postinst called with unknown argument 'triggered'
Tuukka Pasanen , 21/09/2022 – 09:34:33 (+0300): > Upstream MariaDB tracking bug for this is: MDEV-29584 > (https://jira.mariadb.org/browse/MDEV-29584). Control: -1 forwarded https://jira.mariadb.org/browse/MDEV-29584 -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#1018063: [debian-mysql] Bug#1018063: Regression: mariadb client default charset changed breaks compatibility
Hi Georg! Georg Richter , 08/09/2022 – 17:40:21 (+0200): > default character set changed here: > https://github.com/mariadb-corporation/mariadb-connector-c/commit/d7461f7c4f6e36b4916f3dda2b64ac0cae88868c OK > Issues: CONC-547, MDEV-25485. > Github discussion: > https://github.com/MariaDB/server/pull/1722#issuecomment-821027426 @Otto, since you are involved in PR1722 you could probably explain what the plans for Debian packaging are with respect to charset? Thanks! -- Faustin Lammler MariaDB Foundation GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#993527: [debian-mysql] Bug#993527: Bug#993527: mariadb-server: At full-upgrade from buster to bullseye mariadb-server (and also client) are removed.
tags -1 moreinfo signature.asc Description: PGP signature
Bug#1010846: Fwd: Re: [debian-mysql] Bug#1010846: mariadb-common: Removes directory /etc/mysql/mariadb.conf.d during uninstall preventing mysql server from starting
tags -1 moreinfo signature.asc Description: PGP signature
Bug#1001843: [debian-mysql] Bug#1001843: libmariadb-dev: mariadb_config reports incorrect plugin directory
tags -1 moreinfo signature.asc Description: PGP signature
Bug#1018063: [debian-mysql] Bug#1018063: Regression: mariadb client default charset changed breaks compatibility
Hi Tim! Thanks for your report. I have cc. Georg since he helped a lot on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933063. @Georg, can I kindly ask you to take a look at this bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018063)? I am happy to fix it with some guidance from you (whether it's upstream or here in Debian packaging). Regards, -- Faustin signature.asc Description: PGP signature
Bug#993219: [debian-mysql] Bug#993219: Bug#993219: mariadb-server-core: Akonadi database - mysql_upgrade fails always with "FATAL ERROR: Can't execute 'mysqlcheck'"
Hi Ulrich! Since this seems not a MariaDB bug, can I kindly ask you to close it? Otto did a "batch re-opening" because we did not want to loose any bug report when 10.5 was replaced by 10.6 in Sid. Regards, -- Faustin signature.asc Description: PGP signature
Bug#1001843: [debian-mysql] Bug#1001843: libmariadb-dev: mariadb_config reports incorrect plugin directory
Without more information from reporter we will have to close this bug report. Regards, -- Faustin signature.asc Description: PGP signature
Bug#1010846: Fwd: Re: [debian-mysql] Bug#1010846: mariadb-common: Removes directory /etc/mysql/mariadb.conf.d during uninstall preventing mysql server from starting
I am still not able to reproduce this on: - debian 11, mariadb 10.5 - debian sid, mariadb 10.6 Unless the reporter gives more info on how to reproduce this we will have to close this bug report. Regards, -- Faustin signature.asc Description: PGP signature
Bug#993527: [debian-mysql] Bug#993527: Bug#993527: mariadb-server: At full-upgrade from buster to bullseye mariadb-server (and also client) are removed.
Hi! As said in my previous message, I am not able to reproduce this so unless reporter gives more information I will close this bug report since it seems to be fixed. In the mean time and to be sure that we do not hit this problem again, I have implemented a full-upgrade test step in Salsa CI: https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/19 Cheers! --- Faustin signature.asc Description: PGP signature
Bug#996706: [debian-mysql] Bug#996706: mariadb-server-10.5: run directory is not created in multi-instance mode
Hi Peter! Sorry for the delay in responding to this bug report. Peter Keresztes Schmidt , 17/10/2021 – 15:25:16 (+): > Starting mariadb as multi-instance service (mariadb@instance-name.service) > fails > since the run directory (/run/mysqld) is not created. Indeed, this is still the case with both 10.6 repos (MariaDB and Debian). > The normal unit file (mariadb.service) contains following line: > ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld Yep and also still the case in 10.6. > This is missing from mariadb@.service. In buster both unit files contain the > line. True. > Upstream I saw that tmpfiles config generation is implementend since > 7bbc6c14d1e8fcf1f4737e0a5fcf6237fe18bd23, but I don't see those files > shipped with the package. Also true, but this commit is in 10.10 branch, and I don't know if it will reach 10.6 as it could be considered as a breaking change and too dangerous. But there is something that probably needs some attention, see bellow: https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/not-installed#L26 @Otto, can you maybe explain what are the plans for this. In the mean time, I believe that multi-instance service should be configured manually by either creating the directory or by specifying another PATH for the socket. See also: https://mariadb.com/kb/en/systemd/#interacting-with-multiple-mariadb-server-processes Regards. -- Faustin signature.asc Description: PGP signature
Bug#1004262: [debian-mysql] Bug#1004262: Bug#1004262: Acknowledgement (mariadb-server: Instead of being upgraded, mariadb-server gets removed after apt update)
A new step in Salsa CI that should cover this scenario is waiting for review: https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/18 I believe that we could close this once it's merged. Cheers! -- Faustin GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#975911: [debian-mysql] Bug#975911: Seems to have been resolved
Hi! If there is a consensus that this is not a mariadb-client bug, I vote for either: - closing this bug report; - tagging "wontfix". @Otto, I'll let the final decision to you. Faustin signature.asc Description: PGP signature
Bug#1015189: [debian-mysql] Bug#1015189: mariadb-server: stopping mariadb.service never finishes
Hi Paul! Paul Gevers , 23/08/2022 – 22:03:01 (+0200): > After enabling mariadb-server again, at this moment I can indeed stop > it nicely. One addition test I did is that I hibernated once with > mariadb-server running, but also then I could stop it nicely. So, > either 10.6.9 fixed the issue, or the root cause for the symptom went > away somehow. Thanks for confirming and testing again. > I suggest we close this bug, but I'll reopen it again if the problem > resurfaces. Will do. -- Faustin signature.asc Description: PGP signature
Bug#1015189: [debian-mysql] Bug#1015189: mariadb-server: stopping mariadb.service never finishes
Hi Paul! I am not able to reproduce this with 10.6.9, at least in containers with: | podman run --name 1015189 --rm -d fauust/docker-systemd:debian-sid | podman exec -it 1015189 bash -c "apt-get update \ | && apt-get -y install mariadb-server \ | && systemctl start mariadb \ | && systemctl stop mariadb \ | && systemctl status mariadb" | ... | ○ mariadb.service - MariaDB 10.6.9 database server | Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled) | Active: inactive (dead) since Tue 2022-08-23 11:02:36 UTC; 55ms ago |Duration: 11ms |Docs: man:mariadbd(8) | https://mariadb.com/kb/en/library/systemd/ | Process: 1124 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) | Process: 1125 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) | Process: 1127 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) | Process: 1156 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS) | Process: 1169 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) | Process: 1171 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS) |Main PID: 1156 (code=exited, status=0/SUCCESS) | Status: "MariaDB server is down" | CPU: 204ms | | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: FTS optimize thread exiting. | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Starting shutdown... | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Buffer pool(s) dump completed at 220823 11:02:35 | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Shutdown completed; log sequence number 42159; transaction id 15 | Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] /usr/sbin/mariadbd: Shutdown complete | Aug 23 11:02:36 32a0256b22b9 systemd[1]: mariadb.service: Deactivated successfully. | Aug 23 11:02:36 32a0256b22b9 systemd[1]: Stopped MariaDB 10.6.9 database server. Could you verify if you have still the pb with 10.6.9? Could you also verify if you have the pb with 10.6.9 from MariaDB repo (https://mariadb.org/downloads)? Depending on the previous, could you maybe share with me the content of the DB and the configuration so I could try to reproduce it locally (and in a VM since podman is probably not the best way to debug systemd services). Also, if this is not related to Debian packaging, I suggest you report this directly upstream at https://jira.mariadb.org, I could not find any relevant issue there so far. Cheers! -- Faustin signature.asc Description: PGP signature
Bug#1004262: [debian-mysql] Bug#1004262: Bug#1004262: Bug#1004262: Acknowledgement (mariadb-server: Instead of being upgraded, mariadb-server gets removed after apt update)
Oh wait, I read to fast, the issue is now fixed it seems: Faustin Lammler , 23/08/2022 – 11:43:48 (+0200): > | The following packages were automatically installed and are no longer > required: > | libaio1 libffi7 libperl5.32 libsepol1 libssl1.1 perl-modules-5.32 > | Use 'apt autoremove' to remove them. > | The following packages will be REMOVED: > | libsemanage1 mariadb-client-10.5 mariadb-client-core-10.5 > mariadb-server-10.5 > | mariadb-server-core-10.5 > | The following NEW packages will be installed: > | gcc-12-base libdaxctl1 libffi8 libkmod2 libndctl6 libnuma1 libperl5.34 > libpmem1 > | libregexp-ipv6-perl libsemanage2 libsepol2 libssl3 liburing2 > mariadb-client-10.6 > | mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 > perl-modules-5.34 > | sensible-utils sgml-base util-linux-extra So mariadb-server-10.6 is installed. > So we should create a new step that would: > - install the produced package on Debian stable; > - full-upgrade to Debian testing; > - verify that mariadb-server was upgraded (and not removed). > > @Otto, does that look like something good to have in the CI? I will > propose a MR then... Still this is maybe good to have in the CI? -- Faustin signature.asc Description: PGP signature
Bug#1004262: [debian-mysql] Bug#1004262: Bug#1004262: Acknowledgement (mariadb-server: Instead of being upgraded, mariadb-server gets removed after apt update)
Hi! I can still reproduce this with: | ❯ podman run -it debian:11 bash -c "apt-get update && \ | apt-get upgrade -y && \ | apt-get -y install mariadb-server && \ | echo 'deb http://deb.debian.org/debian sid main' >/etc/apt/sources.list && \ | apt-get update && \ | apt-get full-upgrade" | ... | The following packages were automatically installed and are no longer required: | libaio1 libffi7 libperl5.32 libsepol1 libssl1.1 perl-modules-5.32 | Use 'apt autoremove' to remove them. | The following packages will be REMOVED: | libsemanage1 mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5 | mariadb-server-core-10.5 | The following NEW packages will be installed: | gcc-12-base libdaxctl1 libffi8 libkmod2 libndctl6 libnuma1 libperl5.34 libpmem1 | libregexp-ipv6-perl libsemanage2 libsepol2 libssl3 liburing2 mariadb-client-10.6 | mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 perl-modules-5.34 | sensible-utils sgml-base util-linux-extra | The following packages will be upgraded: | adduser apt base-files base-passwd bash bsdutils coreutils dash debconf debianutils diffutils dpkg | e2fsprogs findutils galera-4 gcc-10-base gcc-9-base gpgv grep gzip init-system-helpers iproute2 | libacl1 libaio1 libapt-pkg6.0 libatm1 libattr1 libaudit-common libaudit1 libblkid1 libbpf0 libbsd0 | libbz2-1.0 libc-bin libc6 libcap-ng0 libcgi-pm-perl libclone-perl libcom-err2 libcrypt1 libdb5.3 | libdbd-mariadb-perl libdbi-perl libdebconfclient0 libedit2 libelf1 libencode-locale-perl | libext2fs2 libfcgi-perl libgcc-s1 libgcrypt20 libgdbm-compat4 libgdbm6 libgmp10 libgnutls30 | libgpg-error0 libgpm2 libgssapi-krb5-2 libhogweed6 libhtml-parser-perl libhtml-template-perl | libhttp-message-perl libidn2-0 libio-html-perl libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 | liblzma5 libmariadb3 libmd0 libmount1 libncurses6 libncursesw6 libnettle8 libp11-kit0 | libpam-modules libpam-modules-bin libpam-runtime libpam0g libpcre2-8-0 libpcre3 libperl5.32 | libpopt0 libprocps8 libreadline8 libseccomp2 libselinux1 libsemanage-common libsigsegv2 | libsmartcols1 libsnappy1v5 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 libterm-readkey-perl | libtinfo6 libtirpc-common libtirpc3 libudev1 libunistring2 liburi-perl libuuid1 libxtables12 | libxxhash0 libzstd1 login logsave lsb-base lsof mariadb-common mariadb-server mawk mount | mysql-common ncurses-base ncurses-bin passwd perl perl-base perl-modules-5.32 procps psmisc | readline-common rsync sed socat sysvinit-utils tzdata util-linux zlib1g | 133 upgraded, 21 newly installed, 5 to remove and 0 not upgraded. | Need to get 73.6 MB of archives. | After this operation, 60.6 MB of additional disk space will be used. | Do you want to continue? [Y/n] Otto Kekäläinen , 21/02/2022 – 23:10:00 (-0800): > As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB > 10.6 upgrade on every commit. If passes correctly with: > > The following packages will be REMOVED: > mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5 > mariadb-server-core-10.5 > The following NEW packages will be installed: > libdaxctl1 libkmod2 libndctl6 libnuma1 libodbc2 libodbccr2 libpcre2-posix3 > libpmem1 liburing2 mariadb-client-10.6 mariadb-client-core-10.6 > mariadb-server-10.6 mariadb-server-core-10.6 Yes, this is also still true, but unfortunately it does not reproduce exactly the problem IMO. > To continue with solving this issue I would like to first get it > reproduced in the CI. The root cause why we have an upgrade issue is > that there is a scenario users can hit that is not covered by our CI. > Fixing that would ensure proper testing coverage and forever working > MariaDB upgrades. So we should create a new step that would: - install the produced package on Debian stable; - full-upgrade to Debian testing; - verify that mariadb-server was upgraded (and not removed). @Otto, does that look like something good to have in the CI? I will propose a MR then... Cheers! -- Faustin signature.asc Description: PGP signature
Bug#1010846: Fwd: Re: [debian-mysql] Bug#1010846: mariadb-common: Removes directory /etc/mysql/mariadb.conf.d during uninstall preventing mysql server from starting
Hi Nick! Nick DeYarman <1ni...@gmail.com>, 23/05/2022 – 10:30:37 (-0700): > Yes, those steps then `systemctl stop mysql` and `systemctl start > msyql` (or restart the machine). > > I just tried with a fresh cloud instance (google cloud compute > instance). The first time the issue did **not** reproduce. But I > tried a second time and the same issue reproduced (with the > mariadb.conf.d folder getting deleted). Second time was with > `systemctl stop mysql` and `systemctl start mysql` while the first was > just `systemctl restart mysql`. I can still not reproduce this. Could you paste here exact steps and commands (can you also provide as much info as you can about the instance you are running, maybe the output of `dpkg -l`, in order to understand what packages are installed). Here are my test in podman containers: | $ podman run --name sys-test --rm -d fauust/docker-systemd:debian-11 | $ podman exec -it sys-test bash | root@c0f7ab73450a:/# apt update && apt install -y mariadb-server && apt install -y mailutils | ... | root@c0f7ab73450a:/# dpkg -l | grep mariadb-common | ii mariadb-common 1:10.5.15-0+deb11u1 all MariaDB common configuration files | root@c0f7ab73450a:/# systemctl start mariadb | root@c0f7ab73450a:/# ps fax | grep mariadb | PID TTY STAT TIME COMMAND |4355 ?Ssl0:00 /usr/sbin/mariadbd | root@c0f7ab73450a:/# apt remove -y mailutils && apt autoremove -y | Reading package lists... Done | Building dependency tree... Done | Reading state information... Done | The following packages were automatically installed and are no longer required: | exim4-base exim4-config exim4-daemon-light gsasl-common guile-2.2-libs libevent-2.1-7 libexpat1 libfribidi0 libgc1 libgnutls-dane0 | libgsasl7 libidn11 libldap-2.4-2 libldap-common libltdl7 libmailutils7 libmpdec3 libntlm0 libpython3.9 libpython3.9-minimal | libpython3.9-stdlib libsasl2-2 libsasl2-modules libsasl2-modules-db libsqlite3-0 libunbound8 mailutils-common media-types | Use 'apt autoremove' to remove them. | The following packages will be REMOVED: | mailutils | 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. | After this operation, 1000 kB disk space will be freed. | ... | root@f77cd74ff7e0:/# dpkg -l | grep mariadb-common | ii mariadb-common 1:10.5.15-0+deb11u1 all MariaDB common configuration files | root@c0f7ab73450a:/# ps fax | grep mariadb | PID TTY STAT TIME COMMAND |4355 ?Ssl0:00 /usr/sbin/mariadbd | root@f77cd74ff7e0:/# systemctl restart mariadb && ps fax | grep mariadb |4651 pts/0S+ 0:00 \_ grep mariadb |4627 ?Ssl0:00 /usr/sbin/mariadbd Also, please remember to always include 1010...@bugs.debian.org as recipient in your response (Cc: or To:) so that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010846 gets updated. -- Faustin signature.asc Description: PGP signature
Bug#1009290: [debian-mysql] Bug#1009290: mariadb-server-10.6: Fails to start on live system
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-28751 Hi Daniel! Thank you very much for your detailed report, your tests and to have filled a jira issue! I am now also subscribed to MDEV-28751 and will talk with Daniel Black to see how we can debug this and maybe check if this is an interesting step to add in our CI system. Cheers! -- Faustin signature.asc Description: PGP signature
Bug#1010846: [debian-mysql] Bug#1010846: mariadb-common: Removes directory /etc/mysql/mariadb.conf.d during uninstall preventing mysql server from starting
Hi Nick! I can't reproduce this. Can you confirm the steps: 1/ install mailutils; 2/ install mariadb-server (or mysql-server); 3/ remove mailutils (which command did you use); 4/ autoremove Thanks! -- Faustin signature.asc Description: PGP signature
Bug#993527: [debian-mysql] Bug#993527: Bug#993527: mariadb-server: At full-upgrade from buster to bullseye mariadb-server (and also client) are removed.
Hi Tobias! Tobias Frost , 22/04/2022 – 21:41:19 (+0200): > Unfortunatly it's not fixed... > > Today I came around to upgrade one of my servers from buster to bullseye, and > after upgrade I've found mariadb-server was uninstalled and I had to manually > install it afterwards. > > Attached var/log/apt/history.log of the apt dist-upgrade step, including the > manual fixing. I can't reproduce this in a full-upgrade from buster (10.3.34-0+deb10u1) to bullseye (10.5.15-0+deb11u1). Here are my steps: | $ podman run -it debian:10 bash | root@33d890bad500:/# apt update && apt upgrade && apt install mariadb-server Edit sources.list | root@33d890bad500:/# apt full-upgrade | Reading package lists... Done | Building dependency tree | Reading state information... Done | Calculating upgrade... Done | The following packages were automatically installed and are no longer required: | libapt-pkg5.0 libffi6 libhogweed4 libidn11 libip4tc0 libjson-c3 libnettle6 libperl5.28 libreadline5 | libreadline7 perl-modules-5.28 | Use 'apt autoremove' to remove them. | The following packages will be REMOVED: | galera-3 mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server-10.3 mariadb-server-core-10.3 | The following NEW packages will be installed: | bsdextrautils dbus galera-4 gcc-10-base krb5-locales libapt-pkg6.0 libbpf0 libbsd0 libclone-perl | libcrypt1 libdbus-1-3 libedit2 libexpat1 libfcgi-bin libfcgi0ldbl libffi7 libgcc-s1 libgssapi-krb5-2 | libhogweed6 libip4tc2 libjson-c5 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmd0 | libnettle8 libnsl2 libnss-nis libnss-nisplus libpam-systemd libpcre2-8-0 libperl5.32 libprocps8 | libreadline8 libtirpc-common libtirpc3 libxxhash0 logsave mariadb-client-10.5 | mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 perl-modules-5.32 procps | systemd-timesyncd | The following packages will be upgraded: | apt base-files base-passwd bash bsdutils coreutils dash debconf debian-archive-keyring debianutils | diffutils dmsetup dpkg e2fsprogs fdisk findutils gawk gpgv grep gzip hostname init-system-helpers | iproute2 libacl1 libaio1 libapparmor1 libatm1 libattr1 libaudit-common libaudit1 libblkid1 libbz2-1.0 | libc-bin libc6 libcap-ng0 libcap2 libcap2-bin libcgi-fast-perl libcgi-pm-perl libcom-err2 | libconfig-inifiles-perl libcryptsetup12 libdb5.3 libdbd-mysql-perl libdbi-perl libdebconfclient0 | libdevmapper1.02.1 libelf1 libencode-locale-perl libext2fs2 libfcgi-perl libfdisk1 libgcrypt20 | libgdbm-compat4 libgdbm6 libgmp10 libgnutls30 libgpg-error0 libgpm2 libhtml-parser-perl | libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libidn11 libidn2-0 | libio-html-perl libkmod2 liblwp-mediatypes-perl liblz4-1 liblzma5 libmariadb3 libmnl0 libmount1 | libmpfr6 libncurses6 libncursesw6 libp11-kit0 libpam-cap libpam-modules libpam-modules-bin | libpam-runtime libpam0g libpcre3 libpopt0 libseccomp2 libselinux1 libsemanage-common libsemanage1 | libsepol1 libsigsegv2 libsmartcols1 libsnappy1v5 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 | libterm-readkey-perl libtimedate-perl libtinfo6 libudev1 libunistring2 liburi-perl libuuid1 libwrap0 | libxtables12 libzstd1 login lsb-base lsof mariadb-common mariadb-server mawk mount mysql-common | ncurses-base ncurses-bin netbase passwd perl perl-base psmisc readline-common rsync socat systemd | systemd-sysv sysvinit-utils tar tzdata util-linux vim vim-common vim-runtime xxd zlib1g | 137 upgraded, 46 newly installed, 5 to remove and 0 not upgraded. | Need to get 81.3 MB of archives. | After this operation, 62.4 MB of additional disk space will be used. | Do you want to continue? [Y/n] Can you give me a bit more information on you setup (how could I re-create your package environment to maybe spot the dependency problem?). Cheers! -- Faustin signature.asc Description: PGP signature
Bug#1006111: [debian-mysql] Bug#1006111: Bug#1006111: mariadb-server: wrong groupby result in newly filled myISAM table
Hi Cameron! On Fri, May 20, 2022 at 10:19 PM Cameron Davidson wrote: > the issue I reported has been fixed for me in the recent update. Can I kindly ask you to close this bug report if you think that it is resolved? -- Faustin signature.asc Description: PGP signature
Bug#1006388: [debian-mysql] Bug#1006388: Bug#1006388: Bug#1006388: libmariadb-dev-compat: multi-arch is not present or not working. I am unable to install multiple architectures into Docker "debian:st
Hi Dick! Can I kindly ask you to close this bug report if you believe that it is fixed? Thanks! Dick Hollenbeck , 22/05/2022 – 23:24:00 (-0500): > My docker image is building without error, and this is a new behaviour. > Something got fixed, and I have no reason to think anything I am using is > still broken. > My docker image is softplc/toolkit > at docker hub. > So thank you. -- Faustin signature.asc Description: PGP signature
Bug#1009290: [debian-mysql] Bug#1009290: mariadb-server-10.6: Fails to start on live system
Hi Denys, I am not sure that the problem is the same, in your case it seems that the datadir does not exist or need to be recreated. If you are sure that nothing can be lost (or that you have backups), you should try the following: | sudo systemctl stop mariadb | sudo rm -rf /var/lib/mysql/* | sudo -u mysql mariadb-install-db | Installing MariaDB/MySQL system tables in '/var/lib/mysql' ... | 2022-05-23 14:18:53 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 1 | 2022-05-23 14:18:53 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF | 2022-05-23 14:18:53 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. | OK | ... | sudo systemctl start mariadb Regards, Denys Nykula , 18/05/2022 – 17:16:00 (+0300): > Hello. The apt install of mariadb-server-10.6 fails for me too, > with the same line "Could not execute systemctl" but different > journal messages. I removed the existing setup in /etc and /var, > purged dependencies, but install still fails. How do I debug? > > systemd[1]: Starting MariaDB 10.6.7 database server... > [Note] /usr/sbin/mariadbd (server 10.6.7-MariaDB-3+b1) starting as process > 98614 ... > [Note] InnoDB: The first data file './ibdata1' did not exist. A new > tablespace will be created! > [Note] InnoDB: Compressed tables use zlib 1.2.11 > [Note] InnoDB: Number of pools: 1 > [Note] InnoDB: Using crc32 + pclmulqdq instructions > [Note] InnoDB: Using liburing > [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = > 134217728 > [Note] InnoDB: Completed initialization of buffer pool > [Note] InnoDB: Setting file './ibdata1' size to 12 MB. Physically writing the > file full; Please wait ... > [Note] InnoDB: File './ibdata1' size is now 12 MB. > [Note] InnoDB: Setting log file ./ib_logfile101 size to 100663296 bytes > [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 > [Note] InnoDB: New log file created, LSN=10329 > [Note] InnoDB: Doublewrite buffer not found: creating new > [Note] InnoDB: Doublewrite buffer created > [Note] InnoDB: 128 rollback segments are active. > [Note] InnoDB: Creating shared tablespace for temporary tables > [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the > file full; Please wait ... > [Note] InnoDB: File './ibtmp1' size is now 12 MB. > [Note] InnoDB: 10.6.7 started; log sequence number 0; transaction id 3 > [Note] Plugin 'FEEDBACK' is disabled. > [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't > exist". Some plugins may be not loaded > [Warning] You need to use --log-bin to make --expire-logs-days or > --binlog-expire-logs-seconds work. > [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't > exist > [Note] Server socket created on IP: '127.0.0.1'. > [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' > doesn't exist > [ERROR] Aborting > Warning: Memory not freed: 280 > systemd[1]: mariadb.service: Main process exited, code=exited, > status=1/FAILURE > systemd[1]: mariadb.service: Failed with result 'exit-code'. > systemd[1]: Failed to start MariaDB 10.6.7 database server. > > ___ > pkg-mysql-maint mailing list > pkg-mysql-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mysql-maint -- Faustin signature.asc Description: PGP signature
Bug#1009290: [debian-mysql] Bug#1009290: mariadb-server-10.6: Fails to start on live system
Hi Daniel! Thanks for your detailed report. I am not able to reproduce this with the latest mariadb-server-10.6-dbgsym version (10.6.8). Can you try with the latest version and tell me? Also, can you describe a bit better your setup? If this is a filesystem related issue, I would like to try to reproduce it myself. I have tested with a systemd container that I have created for these kind of testing, here are the commands (using podman): | podman run --name sys-test --rm -d fauust/docker-systemd:debian-sid | podman exec -it sys-test bash -c "echo \"deb http://deb.debian.org/debian-debug/ sid-debug main\" >> /etc/apt/sources.list && apt update && apt install -y mariadb-server-10.6-dbgsym" Cheers! Daniel Lewart , 11/04/2022 – 00:20:00 (-0500): > Package: mariadb-server-10.6 > Version: 1:10.6.7-3 > Severity: important > > Debian MariaDB Maintainers, > > Live Build (--distribution testing) image from April 2022. > 8 GB RAM, so should be plenty of disk space available. > > $ sudo apt install mariadb-server-10.6-dbgsym > ... > Setting up mariadb-server-10.6 (1:10.6.7-3) ... > Created symlink /etc/systemd/system/multi-user.target.wants/mariadb.service → > /lib/systemd/system/mariadb.service. > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. > ... > > $ sudo journalctl | grep -i mariadb | cut -c58- > [See below] > > Perhaps this is similar to: > #983002 - plocate: does not work with /var on overlayfs > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983002 > > Please let me know any additional information that you could use. > > Thank you! > Daniel Lewart > Urbana, Illinois > --- > 2022-04-10 22:53:02 0 [Warning] InnoDB: Retry attempts for writing partial > data failed. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at > offset 0, 1048576 bytes should have been written, only 0 were written. > Operating system error number 22. Check that your OS and file system support > files of this size. Check also that the disk is not full or a disk quota > exceeded. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Could not set the file size of > './ibdata1'. Probably out of disk space > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Database creation was aborted with > error Generic error. You may need to delete the ibdata1 file before trying to > start up again. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 22 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 222. Cannot continue operation > 220410 22:53:02 [ERROR] mysqld got signal 6 ; > 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. > > To report this bug, see https://mariadb.com/kb/en/reporting-bugs > > We will try our best to scrape up some info that will hopefully help > diagnose the problem, but since we have already crashed, > something is definitely wrong and this may fail. > > Server version: 10.6.7-MariaDB-3 > key_buffer_size=134217728 > read_buffer_size=131072 > max_used_connections=0 > max_threads=153 > thread_count=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467957 > K 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 = 0x0 thread_stack 0x49000 > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > Printing to addr2line failed > /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x555d0aa77f0e] > /usr/sbin/mariadbd(handle_fatal_signal+0x478)[0x555d0a5c5268] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /lib/x86_64-linux-gnu/libpthread.so.0(+0x12200)[0x7f606ba96200] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /lib/x86_64-linux-gnu/libc
Bug#1001843: [debian-mysql] Bug#1001843: libmariadb-dev: mariadb_config reports incorrect plugin directory
Hi Akira! With Debian 10, the path is /usr/lib/x86_64-linux-gnu/mariadb19/plugin, see bellow: | ~$ podman run -it debian:10 bash -c "apt-get update && apt-get install -y libmariadb-dev && mariadb_config --plugin" | ... | /usr/lib/x86_64-linux-gnu/mariadb19/plugin | | ~$ podman run -it debian:11 bash -c "apt-get update && apt-get install -y libmariadb-dev && mariadb_config --plugin" | ... | /usr/lib/x86_64-linux-gnu/libmariadb3/plugin You may be confusing with the mysql_config script? See also https://jira.mariadb.org/browse/MDEV-13836. The man page is quite clear about this behavior: | NAME |mysql_config - get compile options for compiling clients | | • --plugindir | | The default plugin directory path name, defined when configuring MariaDB. Also, please note that /usr/lib/mysql/plugin/ does not exist if you only install libmariadb-dev. | ~$ podman run -it debian:11 bash -c "apt-get update && apt-get install -y libmariadb-dev && ls /usr/lib/mysql/plugin/" | ... | ls: cannot access '/usr/lib/mysql/plugin/': No such file or directory If you think this is still problematic, please report it upstream (jira.mariadb.org). Thanks! -- Faustin signature.asc Description: PGP signature
Bug#1001141: [debian-mysql] Bug#1001141: odbc-mariadb: Missing dependency on odbcinst
Hi Hugh! Thank you for your report. Indeed, and it seems that this was already catched by the salsa CI: https://salsa.debian.org/mariadb-team/mariadb-connector-odbc/-/jobs/2364447#L1206 Merge request opened: https://salsa.debian.org/mariadb-team/mariadb-connector-odbc/-/merge_requests/5 And piuparts steps is now green: https://salsa.debian.org/faust/mariadb-connector-odbc/-/jobs/2382987 -- Faustin signature.asc Description: PGP signature
Bug#1001467: [debian-mysql] Bug#1001467: mariadb-10.5: Backport MariaDB 10.5.13 fixes? (Particularly MDEV-26712)
control: forwarded -1 https://jira.mariadb.org/browse/MDEV-26712 Hi Xan! Thanks for your report. 10.5.13 has already been uploaded to proposed updates, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000342 -- Faustin signature.asc Description: PGP signature
Bug#1001385: [debian-mysql] Bug#1001385: Bug#1001385: mariadb-client-10.5: authentification fails while the credentials are ok
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-27215 Hi Anthony! Anthony Bourguignon , 10/12/2021 – 10:06:18 (+0100): > There is a bug upstream : https://jira.mariadb.org/browse/MDEV-27215 . > The password input is limited to 80 characters when prompted in > interactive mode. I’m waiting for more infos. Thanks for opening the issue. > If a patch is made, do you think it could be backported into the > debian stable version ? If upstream decide to patch in 10.5, it will flow to bullseye in the next upgrades. -- Faustin signature.asc Description: PGP signature
Bug#1001385: [debian-mysql] Bug#1001385: mariadb-client-10.5: authentification fails while the credentials are ok
I am able to reproduce this and it looks indeed like a bug (but not related to Debian packaging IMO, so it should be reported upstream, see below). Here is a snippet to reproduce. | #!/bin/bash | | # clean | systemctl stop mariadb | rm -rf /var/lib/mysql | mysql_install_db | systemctl start mariadb | | # create user and db | typeset -r VAR_PWD=$(pwgen 128 1) | mariadb -e "create database testbug;" | mariadb -e "grant all privileges on testbug.* to 'testbug'@'127.0.0.1' identified by '$VAR_PWD';" | mariadb -h 127.0.0.1 -u testbug -p"$VAR_PWD" -e "show databases;" See the following: | root@a77afbebd41d:# bash -x t.sh | + systemctl stop mariadb | + rm -rf /var/lib/mysql | + mysql_install_db | Installing MariaDB/MySQL system tables in '/var/lib/mysql' ... | OK | ... | + systemctl start mariadb | ++ pwgen 128 1 | + typeset -r VAR_PWD=niovooChie7oomefoohat0fah8Foo8muDaethee4iakeithu9ahM4eeveib4goa6deixo6joo6ofedies6Taa2ua3looziek5caixohPhai8OhGeemieweesei8Veiy0 | + mariadb -e 'create database testbug;' | + mariadb -e 'grant all privileges on testbug.* to '\''testbug'\''@'\''127.0.0.1'\'' identified by '\''niovooChie7oomefoohat0fah8Foo8muDaethee4iakeithu9ahM4eeveib4goa6deixo6joo6ofedies6Taa2ua3looziek5caixohPhai8OhGeemieweesei8Veiy0'\'';' | + mariadb -h 127.0.0.1 -u testbug -pniovooChie7oomefoohat0fah8Foo8muDaethee4iakeithu9ahM4eeveib4goa6deixo6joo6ofedies6Taa2ua3looziek5caixohPhai8OhGeemieweesei8Veiy0 -e 'show databases;' | ++ | | Database | | ++ | | information_schema | | | test | | | testbug| | ++ This works as expected: | root@a77afbebd41d:# mariadb -h 127.0.0.1 -u testbug -pniovooChie7oomefoohat0fah8Foo8muDaethee4iakeithu9ahM4eeveib4goa6deixo6joo6ofedies6Taa2ua3looziek5caixohPhai8OhGeemieweesei8Veiy0 -e 'show databases;' | ++ | | Database | | ++ | | information_schema | | | test | | | testbug| | ++ This not (tty ask the password): | root@a77afbebd41d:# mysql -h 127.0.0.1 -u testbug -p | Enter password: | ERROR 1045 (28000): Access denied for user 'testbug'@'localhost' (using password: YES) I can't reproduce this with smaller password (with 'pwgen 64 1' for instance). Can I ask you to: - verify if there is a similar issue upstream (jira.mariadb.org) and report it in case you do not find something similar; - forward this bug report to the upstream issue. Thanks! -- Faustin signature.asc Description: PGP signature
Bug#1001385: [debian-mysql] Bug#1001385: mariadb-client-10.5: authentification fails while the credentials are ok
Hi! I may have read your report to quickly. Since I am not able to reproduce this locally, can you provide more informations on the steps that I could follow to reproduce this? Thanks! -- Faustin signature.asc Description: PGP signature
Bug#1001385: [debian-mysql] Bug#1001385: mariadb-client-10.5: authentification fails while the credentials are ok
Hi Anthony! I am not able to reproduce this. > - connect as root and create a database and a user : > create database testbug; > grant all privileges on testbug.* to 'testbug'@'127.0.0.1' > identified by 's3cr3t'; > - try to connect with those credentials : > mariadb -h 127.0.0.1 -u testbug -p testbug This last command does not correspond to the previous user creation command, I am wondering if this is not a password problem (you should use something like '-ps3cr3t'). Cheers! -- Faustin signature.asc Description: PGP signature
Bug#949020: linux-image-5.6.0-2-amd64: Lenovo poweroff/suspend failure
Hi! I have the exact same problem on a fresh Debian 11 installation and a T460s laptop. Changing TPM from 2.0 to 1.2 in the BIOS resolves the poweroff and the suspend issue. Also FYI (not sure if that helps), as I did not found 949020 earlier, I have used the following workaround on Buster + 5.10 bpo kernel (hibernating just after booting to then be able to suspend until next reboot): | echo reboot >/sys/power/disk | echo disk >/sys/power/state As far as I can remember, I did not had the poweroff problem on Buster, just suspend. -- Faustin signature.asc Description: PGP signature
Bug#990868: lenovo T460 Shutdown Problem
Hi Bjørn! Bjørn Mork , 25/08/2021 – 20:12:09 (+0200): > This sounds like https://bugs.debian.org/949020 Yes, exactly! I remember searching a lot when it happened to me last year, but not sufficiently apparently... > Short version: Disable TPM 2.0 (select 1.2) i BIOS, or disable IOMMU by > booting with intel_iommu=off on the command line. Switching to TPM 1.2 works perfectly, I did not tried the intel_iommu=off workaround so far... Thanks again! -- Faustin signature.asc Description: PGP signature
Bug#990868: lenovo T460 Shutdown Problem
Hi! I seem to have the same problem on my T460s and it is impossible to suspend the laptop (lid close or systemctl suspend). As far as I can remember, the problem appeared with kernel 5 branch (bpo on buster). At that time I did not wanted to open a bug report because I was not sure of my installation (dist-upgrade from buster, plus lots of bpo kernel installation and test) and I had found a workaround for the suspend problem, using those commands after reboot: | echo reboot >/sys/power/disk | echo disk >/sys/power/state Now I have a clean Debian 11 installation and both suspend and poweroff does not work anymore. I am happy to help to debug this if needed. Cheers! Faustin signature.asc Description: PGP signature
Bug#989400: [debian-mysql] Bug#989400: Bug#989400: mariadb-server-10.5: MariaDB fail to execute CONVERT TO CHARACTER
Hi Dimitry, I may be wrong but I guess that Otto was referring to using https://snapshot.debian.org/? -- Faustin signature.asc Description: PGP signature
Bug#990763: [debian-mysql] Bug#990763: mariadb-server-core-10.3: MariaDB 10.3.29 is crashing and restarting continuously
Hi! Thanks for your detailed report. I can't see anything related to Debian packaging and you seem to have hit a bug in mariadb-server and I suggest you to ask for help with upstream developers. I have searched a bit in upstream issue but I can't find an issue describing the exact same situation as yours. MDEV-25394 seems quite similar though: https://jira.mariadb.org/browse/MDEV-25394 If you can't find a similar issue, then I encourage you to create one and link this bug report to it (see "Setting Forwarded": https://www.debian.org/Bugs/Reporting) Thanks! -- Faustin signature.asc Description: PGP signature
Bug#990156: [debian-mysql] Bug#990156: mariadb-server-10.3: Service configuration fails package upgrade
Control: tags -1 moreinfo signature.asc Description: PGP signature
Bug#990156: [debian-mysql] Bug#990156: mariadb-server-10.3: Service configuration fails package upgrade
Hi Chris! I am not able to reproduce this, here are the steps I am using: - start a systemd podman debian 10 container; | $ podman run --name sys-test --rm -d fauust/docker-systemd:debian-10 | $ podman exec -it sys-test bash - activate debian snapshot repo (to install old mariadb-server version 10.3.27-0+deb10u1); | # echo "deb http://snapshot.debian.org/archive/debian/20210105 buster main">/etc/apt/sources.list - install mariadb-server 10.3.27-0+deb10u1, start it and check; | # apt update && apt install mariadb-server -y | # systemctl start mariadb && mariadb | Welcome to the MariaDB monitor. Commands end with ; or \g. | Your MariaDB connection id is 15 | Server version: 10.3.27-MariaDB-0+deb10u1 Debian 10 | | Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. | | Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. - stop mariadb and test the upgrade: | # systemctl stop mariadb | # echo "deb http://deb.debian.org/debian buster main">/etc/apt/sources.list | # apt update && apt upgrade -y - verify that mariadb is not started, start it and check the version: | # systemctl status mariadb | ● mariadb.service - MariaDB 10.3.29 database server |Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) |Active: inactive (dead) since Fri 2021-07-09 14:23:31 UTC; 1min 17s ago | Docs: man:mysqld(8) |https://mariadb.com/kb/en/library/systemd/ | Main PID: 1268 (code=exited, status=0/SUCCESS) |Status: "MariaDB server is down" | CPU: 998ms | # systemctl start mariadb && mariadb | Welcome to the MariaDB monitor. Commands end with ; or \g. | Your MariaDB connection id is 8 | Server version: 10.3.29-MariaDB-0+deb10u1 Debian 10 | | Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. | | Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. Can you please provide some information about the context and guide me so I could try to reproduce this? Also, I don't see how it could influence, but as you seem to be on arm platform, maybe we should try to reproduce it on this architecture? Regards, -- Faustin signature.asc Description: PGP signature
Bug#989898: [debian-mysql] Bug#989898: Update from upstream
Control: -1 forwarded https://jira.mariadb.org/browse/MDEV-25114 vasilis g , 25/06/2021 – 14:27:50 (+0300): > Hello, > > I would like to add that upstream has marked this bug as blocker > (highest severity) and is currently working on a fix. This affects > galera clusters. > > REF https://jira.mariadb.org/browse/MDEV-25114 > > VG > > ___ > pkg-mysql-maint mailing list > pkg-mysql-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mysql-maint -- Faustin signature.asc Description: PGP signature
Bug#976147: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11
Hi Otto! Otto Kekäläinen , 15/05/2021 – 12:56:58 (-0700): > Yes we consider doing that. Note however that it does not fix this bug > in question, we still want the dist-upgrade for Galera users to > succeed. It also needs to be debugged and a MR submitted on how to > change Galera-4 debian/control file for the upgrade to pass > flawlessly. It's not clear to me what the upgrade path for Galera would be given the fact that both galera-3 and galera-4 packages exists in Bullseye. Should a dist-upgrade upgrade galera-3 to galera-4 or does the user explicitly have to ask for galera-4? Also, removing the dependency to galera resolves the fact that mariadb-server-10.3 is removed on a dist-upgrade (galera-3 is not removed and mariadb-server-10.3 is upgraded to mariadb-server-10.5). So if the deadline to upload mariadb is short (you spoke about tomorrow), I find this solution valid until we find also a solution for Galera of course... > > The salsa CI is still green when doing so: > > https://salsa.debian.org/faust/mariadb-10.5/-/pipelines/254990 > > Good. Did you also test upstream buildbot? I have just created a WIP PR for that: https://github.com/MariaDB/server/pull/1829 > Revert: > https://github.com/MariaDB/server/commit/6bd94cf54274d54521ece1e50d534777122ff29e You mean: https://github.com/MariaDB/server/commit/b9fee60871264ea56a5582ca7a436aabdabea6fc > But as said, the bug #988089 can only be fixed by a change in galera-4 > debian/control. Changing the mariadb-10.5 debian/control to > recommends:galera-4 is a separate change. Ok but I have no idea how this should be handled then. See my previous comment and https://packages.debian.org/bullseye/galera-3 and https://packages.debian.org/bullseye/galera-4. -- Faustin signature.asc Description: PGP signature
Bug#988089: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11
Otto Kekäläinen , 15/05/2021 – 12:50:24 (-0700): > What you do in > https://salsa.debian.org/faust/galera-4/-/commit/d0119633bd42ebcedb300fb7423035de4f91f1bc > with aptly and tmux and printf 'X\n' seems overly complex. To make a > local repo for testing you can simply run: > apt install apt-utils > cd /path/to/deb/files > apt-ftparchive release . > Release > echo 'deb [trusted=yes] file:/path/to/deb/files ./' >> /etc/apt/sources.list > apt update > apt dist-upgrade Indeed! I guess that I was looking for an excuse to play with aptly (understanding how this tool works was in my todo list for too long). But yeah, completely overkill in that case, thanks! -- Faustin signature.asc Description: PGP signature
Bug#976147: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11
Hi! I am in favour of removing galera-4 from Depends and as suggested by Olaf make it only a suggestion (Suggests), I am not sure if it's even necessary (after all, MariaDB standalone server and Galera cluster are two very different setup). The salsa CI is still green when doing so: https://salsa.debian.org/faust/mariadb-10.5/-/pipelines/254990 Plus, even if I can't reproduce this dist-upgrade problem on the Salsa CI, on my personal drone CI, doing so also resolve the problem from an upstream build with https://github.com/fauust/mariadb-server/tree/fix-dist-upgrade whereas the problem exists on the 10.5 branch. Finally, galera-4 is not a dependency on RPM: | docker run fedora:latest bash -c "yum update -y && yum install mariadb-server -y && rpm -qa | egrep 'mariadb|galera'" I have asked on Zulip if there is any reason of this dependency that I could have missed. Cheers! -- Faustin signature.asc Description: PGP signature
Bug#976147: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11
Hi! I have spent a lot of time today on this and I worked on implementing a dist-upgrade in salsa CI with the aptly tool (I am not very far, and I will submit MR but only next week I guess...). I am still not sure about how to fix this dependency pb and I lost some time because of a strange behavior depending on which docker container I was using (buster/buster-slim). A dist-upgrade from debian:buster container always fails whereas a dist-upgrade from debian:buster-slim only fails when targeting sid. See: https://salsa.debian.org/faust/galera-4/-/pipelines/254828/builds I am too tired to investigate why, but maybe this can give you some pointers/ideas? -- Faustin signature.asc Description: PGP signature
Bug#988089: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11
Hi! So, I also tried the apt debug commands but I could not find the exact problem (this is also way too verbose for me ATM). Here are some questions regarding galera (because I believe the problem might come from it): - why bullseye/sid provide both galera-3 and galera-4? - why installing galera-4 removes mariadb-server-10.3, see bellow: | docker run -it debian:10 bash -c \ | "apt-get update \ | && apt-get upgrade -y \ | && apt-get install -y 'mariadb-server' \ | && dpkg -l | egrep '(mariadb|mysql|galera)' \ | && printf 'deb http://deb.debian.org/debian bullseye main' >/etc/apt/sources.list \ | && apt-get clean \ | && apt-get update \ | && apt-get install galera-4 \ | && dpkg -l | egrep '(mariadb|mysql|galera)'" @Otto, I believe that the salsa CI did not catch this problem because we are upgrading using the generated deb `apt install ./*.deb` and not using a mirror and `apt-get full-upgrade` (and maybe because we are explicitly asking apt to upgrade galera). It would be good to also test a very common scenario where we install only mariadb-server (and it's dependencies) and try to upgrade it using the recommended Debian method (https://wiki.debian.org/DebianUpgrade). I have no idea for the moment if this is easy to implement in the salsa CI but I will do some tests. Here is the snippet to reproduce the upgrade problem in docker: | docker run -it debian:10 bash -c \ | "apt-get update \ | && apt-get upgrade -y \ | && apt-get install -y 'mariadb-server' \ | && dpkg -l | egrep '(mariadb|mysql|galera)' \ | && printf 'deb http://deb.debian.org/debian bullseye main' >/etc/apt/sources.list \ | && apt-get clean \ | && apt-get update \ | && apt-get full-upgrade -y \ | && dpkg -l | egrep '(mariadb|mysql|galera)'" Cheers! -- Faustin Lammler F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#970045: [debian-mysql] Bug#970045: galera-4: Use user "_galera" instead of "nobody" to run the daemon
Hi, I'll try to implement this. Cheers! -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#987231: [debian-mysql] Bug#987231: mariadb-server-10.5: Generated /etc/logrotate.d/mariadb has wrong paths
Control: forwarded -1 https://github.com/MariaDB/server/pull/1556 Hi Matthew! Thanks for your detailed report. Indeed, the generated log rotate seems wrong (and I am able to reproduce the problem with 10.5 on sid). Could you maybe help on this directly upstream https://github.com/MariaDB/server/pull/1556? I have just created a comment based on this bug report https://github.com/MariaDB/server/pull/1556#discussion_r625630838. There is also a discussion about the project of creating an unified and optimal logrotate configuration on jira: https://jira.mariadb.org/browse/MDEV-22659 -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#985870: [debian-mysql] Bug#985870: mariadb-server-10.5: unowned files after purge (policy 6.8, 10.8): /usr/share/mysql/debian-10.5.flag
Control: forwarded -1 https://github.com/MariaDB/server/pull/1825 -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#967047: plymouth-start.service: Unit configured to use KillMode=none
Hi, FYI, I hit this bug by trying to verify a systemd unit file. | systemd-analyze verify docker.service | /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. Here is the MR: https://salsa.debian.org/debian/plymouth/-/merge_requests/3 Cheers! -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#985870: [debian-mysql] Bug#985870: mariadb-server-10.5: unowned files after purge (policy 6.8, 10.8): /usr/share/mysql/debian-10.5.flag
Hi Andreas! Thanks for your report and I can confirm this with the latest 10.5 version (debian and upstream). | podman run -it debian:sid bash -c "apt-get update &&\ | apt-get install -y mariadb-server &&\ | ls /usr/share/mysql/debian-*.flag &&\ | apt-get autopurge -y --force mariadb-server" @Otto, I have verified on 10.3 and my understanding is that there might be a confusion between datadir and statedir. For 10.3 we did not create the flag in the statedir whereas upstream did: https://salsa.debian.org/mariadb-team/mariadb-10.3/-/blob/buster/debian/mariadb-server-10.3.postinst#L96-114 https://github.com/MariaDB/server/blob/10.3/debian/mariadb-server-10.3.postinst#L135-L156 I am not sure if this statedir flag (/usr/share/mysql/debian-*.flag) is used by any maintainer script, let me know if you want me to open a jira issue and a PR upstream (I guess we should fix this upstream). Faustin signature.asc Description: PGP signature
Bug#985821: [debian-mysql] Bug#985821: Mariadb crashes on long semaphore list related to "InnoDB persistent stats analyze forces full scan forcing lock crash"
Control: -1 forwarded https://jira.mariadb.org/browse/MDEV-24275 Control: -1 tags + fixed-upstream Hi Vasilis! Thank you for your report. I have asked Otto when 10.3.28 (or later) would make it into Debian 10, see https://salsa.debian.org/mariadb-team/mariadb-10.3/-/merge_requests/30#note_234016. In the mean time, if using the MariaDB Foundation deb packages is an option for you, take a look at https://mariadb.org/download/#mariadb-repositories. Regards, -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#984784: ITP: golang-mvdan-editorconfig -- golang editorconfig module
Package: wnpp Severity: wishlist Owner: Faustin Lammler * Package name: golang-mvdan-editorconfig Version : 0.1.0-1 Upstream Author : Daniel Martí * URL : https://mvdan.cc/editorconfig * License : BSD-3-clause Programming Lang: Go Description : EditorConfig support in Go A small package to parse and use EditorConfig files. . An official library exists for Go. This alternative implementation started with a different design: * Specialised INI parser, for full compatibility with the spec * Ability to cache parsing files and compiling pattern matches * Storing and querying all properties equally * Minimising pointers and maps to store data The motivation behind packaging this golang module is to be able to package shfmt, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970393 Regards, -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#983563: [debian-mysql] Bug#983563: mariadb-server: trigger fails when systemd is not running (eg. chroot)
Hi Arnaud! Arnaud Rebillout , 26/02/2021 – 16:39:41 (+0700): > Hence I believe that the line: > > if [ -x "$(command -v systemctl)" ]; then > > Should be replaced by: > > if [ -d /run/systemd/system ]; then I am not sure that this is what we want here. Indeed, doing this would lead to the execution of `invoke-rc.d mariadb restart` in your particular case (but you are using systemd not sysv init). Or I am missing something? Could point me to the steps in your CI where this happen so I can try to reproduce it? -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#976147: [debian-mysql] Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails
Hi Calum! Thanks for providing more information. Unfortunately, I am still not able to reproduce the problem and your logs show that mariadb server 10.3 is upgraded to 10.5. So what was the problem for you? Here are the scenarios that I have tested. Upgrade 10.3 to 10.5 on the actual sid container: - start a debian:sid container; - add buster to sources.list (to be able to install mariadb-server-10.3); - install mariadb-server-10.3; - upgrade mariadb-server-10.3 to mariadb-server-10.5. Upgrade 10.3 to 10.5 on the actual buster container: - start a debian:buster container; - install mariadb-server-10.3; - add sid to sources.list; - apt upgrade && apt full-upgrade. Upgrade 10.3 to 10.5 on the debian:sid-20201209 container (using https://snapshot.debian.org/): - start a debian:sid-20201209 container; - add http://snapshot.debian.org/archive/debian/20201215 to the sources.list file: echo "deb http://snapshot.debian.org/archive/debian/20201215 sid main">/etc/apt/sources.list - install mariadb-server-10.3 (10.3.24-2 version) from snapshot.debian.org: apt-get -o Acquire::Check-Valid-Until=false update apt-get install mariadb-server-10.3 - upgrade 10.3 to 10.5. So, without more information on the exact problem and because I can't reproduce it, I guess that there is nothing more that we can do here... -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#982472: ITP: golang-github-pkg-diff -- golang diff module
Package: wnpp Severity: wishlist Owner: Faustin Lammler * Package name: golang-github-pkg-diff Version : 0.0~git20200914.5b29258-1 Upstream Author : Josh Bleecher Snyder * URL : https://github.com/pkg/diff * License : BSD-3-clause Programming Lang: Go Description : Module github.com/pkg/diff can be used to create, modify, and print diffs. The top level package, diff, contains convenience functions for the most common uses. . The subpackages provide very fine-grained control over every aspect: * myers creates diffs using the Myers diff algorithm. * edit contains the core diff data types. * ctxt provides tools to reduce the amount of context in a diff. * write provides routines to write diffs in standard formats. The motivation behind packaging this golang library is to be able to package shfmt, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970393 Regards, -- Faustin Lammler signature.asc Description: PGP signature
Bug#970393: RFP: shfmt -- Shell script formatter
Hi! I am also interested in helping in packaging shfmt for Debian. (Cc. Jules Sam. Randolph as he seems to be interested too). Regards, -- Faustin Lammler GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79 signature.asc Description: PGP signature
Bug#977383: [debian-mysql] Bug#977383: Bug#977383: closed by Debian FTP Masters (Bug#977254: Removed package(s) from unstable)
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-24194 signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Thanks Olaf, your help is very appreciated! Can I kindly ask you to open an issue directly on jira.mariadb.org then (and forward this BR when it's open). I have already searched for such issue on jira but nothing cames out. Regards, Faustin signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Hi Olaf! Olaf van der Spek , 11/12/2020 – 14:21:16 (+0100): > https://mariadb.com/docs/reference/mdb/system-variables/open_files_limit/ > > > SkySQL Analytical 10.5; Default: 32186 > > This however, is about the value we're seeing. Could the docs be out-of-date? This can of course happen, I'll verify this point with MariaDB Foundation. But I still don't understand why we would have this only on the Debian package version, not on upstream version, also the problem seems to affect 10.3, not 10.5 Faustin signature.asc Description: PGP signature
Bug#977137: [debian-mysql] Bug#977137: mariadb-server: Mariadb-server kept back on apt upgrade
Hi Olaf! Yes I can confirm this behavior on sid. My understanding from https://lists.debian.org/debian-release/2020/11/msg00305.html is that 10.3 will be fully removed from sid and replaced by 10.5. Faustin signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Olaf van der Spek , 11/12/2020 – 13:11:40 (+0100): > Package: mariadb-server-10.3 > Version: 1:10.3.27-0+deb10u1 > Followup-For: Bug #976652 > > Dear Maintainer, > > Fresh Debian 10 install, fresh mariadb-server install: > > # zgrep max_open_files syslog* > > Dec 11 13:08:46 xyz mysqld[1695]: 2020-12-11 13:08:46 0 [Warning] Could not > increase number of max_open_files to more than 16384 (request: 32184) Yes, this is confirmed, I have just tested in a fresh Debian 10 VM locally. However, I have no warning when installing MariaDB from official repositories (https://mariadb.org/download/#mariadb-repositories). @Otto, do you have any idea of what could be causing this? Faustin signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Olaf van der Spek , 11/12/2020 – 12:35:37 (+0100): > Yes, aren't you? ;) Nope :-) > I think it's just the MariaDB default. I don't remember seeing the > warning before though, was it introduced in a security update? No idea. But as you can see on a previous message, this is still the same value in the systemd unit file for 10.6. So, I would be surprised that this was not catched upstream already. > I'll do a fresh Debian 10 install in a new VM to see if the warning > occurs there too. Much appreciated, thanks! I have just verified and I was not able to reproduce this on an debian 10 and sid container. Faustin signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Hi Olaf! Olaf van der Spek , 11/12/2020 – 11:50:53 (+0100): > Package: mariadb-server-10.3 > Version: 1:10.3.27-0+deb10u1 > Followup-For: Bug #976652 > > Dear Maintainer, > > > syslog.6.gz:Dec 5 18:56:49 dev mysqld[694]: 2020-12-05 18:56:49 0 > > [Warning] Could not increase number of max_open_files to more than 16384 > > (request: 32183) Are you having this message too? > Where does the 32183 come from? I don't see it in any conf file and it's not > a value I'd set myself.. So you grep /etc for this value? I have no idea where it could come from. Can you maybe describe your setup so we can maybe find correlations with Richard's setup? Would that maybe come from a particular DB installation where this value is setup directly in the DB by the installer? > I'm not sure this isn't a 'bug'. Indeed, maybe not. Faustin signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Richard van den Berg , 07/12/2020 – 19:20:12 (+0100): > Ok, so the 16384 limit in /lib/systemd/system/mariadb.service is actually > the default from upstream? Yes, see: https://github.com/MariaDB/server/blob/10.6/support-files/mariadb.service.in#L146 > That seems odd to me as it warns it needs more in a simple small setup > like mine. I suppose that mariadb asking for more open files is the > bug here then. I'll open it upstream if it persists. Or maybe a configuration error? Check for open_files_limit in your configuration files or directly in mariadb with: | SHOW GLOBAL VARIABLES LIKE 'open_files_limit'; Can I kindly ask you to close the bug report then? Thanks! Regards, Faustin signature.asc Description: PGP signature
Bug#976652: [debian-mysql] Bug#976652: mariadb-server-10.3: Could not increase number of max_open_files to more than 16384 (request: 32191)
Hi Richard! This can not be considered as a bug and you are asking to make default an increase of the max_open_files option because your setup needs it. Why not consider instead overriding the systemd unit default option with what you think is the best value for your setup? Search for "override" keyword in: https://www.freedesktop.org/software/systemd/man/systemd.unit.html Here is example on how to override the "ProtectHome" option: https://mariadb.com/kb/en/systemd/#configuring-access-to-home-directories If you really think that this value should be increased and become the default value for every MariaDB default installation, then I suggest you open an issue directly upstream (https://jira.mariadb.org): Regards, Faustin signature.asc Description: PGP signature
Bug#976147: [debian-mysql] Bug#976147: Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails
Control: severity -1 normal Control: tags -1 + moreinfo signature.asc Description: PGP signature
Bug#976147: [debian-mysql] Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails
Hi Jörg! I am not sure that I understand what are the steps that I could follow to verify this. Are you trying to dist-upgrade from buster to sid? In that case, I was not able to reproduce the error in a container with the following steps: | # podman run -it debian:10 bash | # apt update | # apt upgrade | # apt install mariadb-server -y | # dpkg -l | grep mariadb-server | ii mariadb-server 1:10.3.25-0+deb10u1 all MariaDB database server (metapackage depending on the latest version) | ii mariadb-server-10.3 1:10.3.25-0+deb10u1 amd64 MariaDB database server binaries | ii mariadb-server-core-10.3 1:10.3.25-0+deb10u1 amd64 MariaDB database core server files | # printf 'deb http://deb.debian.org/debian/ sid main' >/etc/apt/sources.list | # apt update | # apt upgrade | # apt dist-upgrade | Reading package lists... Done | Building dependency tree | Reading state information... Done | Calculating upgrade... Done | The following packages were automatically installed and are no longer required: | fdisk libapt-pkg5.0 libfdisk1 libffi6 libhogweed4 libnettle6 libperl5.28 libreadline5 libreadline7 perl-modules-5.28 | Use 'apt autoremove' to remove them. | The following packages will be REMOVED: | galera-3 mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server-10.3 mariadb-server-core-10.3 | The following NEW packages will be installed: | galera-4 libedit2 libprocps8 mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 procps | The following packages have been kept back: | gcc-8-base | The following packages will be upgraded: | mariadb-server | 1 upgraded, 8 newly installed, 5 to remove and 1 not upgraded. | Need to get 14.5 MB of archives. | After this operation, 11.1 MB disk space will be freed. | Do you want to continue? [Y/n] | ... | # dpkg -l | grep mariadb-server | ii mariadb-server 1:10.5.8-3 all MariaDB database server (metapackage depending on the latest version) | rc mariadb-server-10.3 1:10.3.25-0+deb10u1 amd64 MariaDB database server binaries | ii mariadb-server-10.5 1:10.5.8-3 amd64 MariaDB database server binaries | ii mariadb-server-core-10.5 1:10.5.8-3 amd64 MariaDB database core server files Can you please give us more details about the steps? Regards, Faustin signature.asc Description: PGP signature
Bug#975315: mariadb-10.5: FTBFS on sh4: error: event.h: No such file or directory
Source: mariadb-10.5 Version: 1:10.5.8-2 Tags: confirmed, help, ftbfs Severity: normal User: debian-...@lists.debian.org Usertags: sh4 Build failed with: /<>/builddir/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10: fatal error: event.h: No such file or directory 1 | #include | ^ compilation terminated. gmake[3]: *** [CMakeFiles/cmTC_0e7f4.dir/build.make:85: CMakeFiles/cmTC_0e7f4.dir/CheckIncludeFile.c.o] Error 1 gmake[3]: Leaving directory '/<>/builddir/CMakeFiles/CMakeTmp' gmake[2]: *** [Makefile:140: cmTC_0e7f4/fast] Error 2 gmake[2]: Leaving directory '/<>/builddir/CMakeFiles/CMakeTmp' dh_auto_configure: error: cd builddir && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/sh4-linux-gnu -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPLUGIN_ROCKSDB=NO "-DCOMPILATION_COMMENT=Debian unstable " -DMYSQL_SERVER_SUFFIX=-2 -DSYSTEM_TYPE=debian-linux-gnu -DCMAKE_SYSTEM_PROCESSOR=sh4 -DBUILD_CONFIG=mysql_release -DCONC_DEFAULT_CHARSET=utf8mb4 -DPLUGIN_TOKUDB=NO -DPLUGIN_CASSANDRA=NO -DPLUGIN_AWS_KEY_MANAGEMENT=NO -DPLUGIN_COLUMNSTORE=NO -DWITH_INNODB_SNAPPY=ON -DDEB=Debian .. returned exit code 1 make[1]: *** [debian/rules:73: override_dh_auto_configure] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:186: binary-arch] Error 2 signature.asc Description: PGP signature
Bug#972382: [debian-mysql] Bug#972382: Bug#972382: mariadb-server-10.5: logrotate service error at system startup
Control: forcemerge -1 971399 signature.asc Description: PGP signature
Bug#972382: [debian-mysql] Bug#972382: mariadb-server-10.5: logrotate service error at system startup
Control: merge -1 971399 Hi Antonio! Thanks for your report. This is duplicate of #971399. Faustin signature.asc Description: PGP signature
Bug#971778: [debian-mysql] Bug#971778: mariadb-client-core-10.5: mariadb-embedded is missing
Hi! Indeed https://github.com/MariaDB/server/blob/10.4/debian/not-installed#L4 It seems that the move was done in 10.4 to not deploy it anymore due to it's huge size. Otto, do you know if this binary is provided by another deb or if there is any way to get it through Debian repositories. Faustin signature.asc Description: PGP signature
Bug#971399: [debian-mysql] Bug#971399: my_print_defaults: unknown option '--mariadbd'
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-22659 Hi Bob! Thanks for your help. The jira issue you are pointing on is correct (so I am forwarding this bug report to it). Feel free to do it next time, that helps us a lot in maintaining this complex package. https://www.debian.org/Bugs/server-control#forwarded Another link (that is already referenced in the jira issue) where there might be progress in the future is the PR by Otto https://github.com/MariaDB/server/pull/1556 Your workaround is correct too, but as it's an upstream issue, we have to wait for an upstream resolution first. Regards, Faustin signature.asc Description: PGP signature
Bug#917088: [debian-mysql] Bug#917088: Bug#917088: Bug#917088: mariadb-server-10.3: #1071 - Specified key was too long; max key length is 1000 bytes
Conrtol: forwarded -1 https://jira.mariadb.org/browse/MDEV-18061 Hi Olaf! I see that you opened a jira issue about this, remember to forward bug reports to upstream issue so we can track them better. What about Sergei last message, do you have any further comments? Regards, Faustin signature.asc Description: PGP signature
Bug#970681: [debian-mysql] Bug#970681: Bug#970681: /usr/bin/mytop: mytop fails to start: ‘perl -w’: No such file or directory
Hi Otto! Otto Kekäläinen , 23/09/2020 – 15:52:34 (+0300): > The error "Unknown option: default-character-set" is also fixed in > MariaDB 10.5.5 as the /etc/mysql/mariadb.conf.d/50-client.cnf no > longer defines anything about charsets or utf8mb4 (it relies on the > server to enforce utf8mb4 anyway). Great! Do you have any idea how to handle the dependency problem on libdbd-mysql-perl then? signature.asc Description: PGP signature
Bug#970681: [debian-mysql] Bug#970681: /usr/bin/mytop: mytop fails to start: ‘perl -w’: No such file or directory
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-23697 Hi Lucio! Thanks for your report. Indeed: | docker run --name test --privileged -d -v /sys/fs/cgroup:/sys/fs/cgroup:ro fauust/docker-systemd:debian-sid | docker exec -it test bash -c "apt update && apt -y install mariadb-server" | docker exec -it test bash -c "systemctl start mariadb && mytop" | /usr/bin/env: 'perl -w': No such file or directory | /usr/bin/env: use -[v]S to pass options in shebang lines Seems to be related with https://jira.mariadb.org/browse/MDEV-23697. Workaround is to edit '/usr/bin/mytop' and replace: | #!/usr/bin/env perl -w with | #!/usr/bin/env perl But then there is a dependency problem: | Unknown option: default-character-set | install_driver(mysql) failed: Can't locate DBD/mysql.pm in @INC (you may need to install the DBD::mysql module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl) at (eval 21) line 3. | Perhaps the DBD::mysql perl module hasn't been fully installed, | or perhaps the capitalisation of 'mysql' isn't right. | Available drivers: DBM, ExampleP, File, Gofer, MariaDB, Mem, Proxy, Sponge. | at /usr/bin/mytop line 291. And you have to install 'libdbd-mysql-perl' packages: | sudo apt install libdbd-mysql-perl Faustin signature.asc Description: PGP signature
Bug#956401: [debian-mysql] Bug#956401: mariadb-server: --ssl-verify-server-cert fails
Control: forward -1 https://jira.mariadb.org/browse/MDEV-12190 Hi Otto! So shouldn't we tag wontfix? signature.asc Description: PGP signature
Bug#927289: [debian-mysql] Bug#927289: Bug#927289: Bug#927289: mariadb-server-10.3: SSL error: Unable to get private key
Hi, the tip from Michael Pietsch seems to have been confirmed in the KB documentation, see comments from Jean Weisbuch https://mariadb.com/kb/en/certificate-creation-with-openssl/ So if it's a certificate format problem due to a bad generation procedure, I guess we could close this. I have raised this documentation problem in https://jira.mariadb.org/browse/MDEV-19268 Faustin signature.asc Description: PGP signature
Bug#968222: [debian-mysql] Bug#968222: mariadb-server-core-10.3: daemon won't restart after update to latest unstable
Control: forward -1 https://jira.mariadb.org/browse/MDEV-23050 Hi Russel! This may be related to: - https://jira.mariadb.org/browse/MDEV-23050 - https://jira.mariadb.org/browse/MDEV-23321 Faustin signature.asc Description: PGP signature
Bug#966196: [debian-mysql] Bug#966196: Bug#966196: mariadb-server-10.3: Mariadb 10.3.22 fails to start after Stretch update, Failed at step EXEC spawning /etc/mysql/debian-start: No such file or direc
Control: tags -1 moreinfo signature.asc Description: PGP signature
Bug#962902: [debian-mysql] Bug#962902: Bug#962902: Bug#962902: server does not start
Control: tags -1 moreinfo signature.asc Description: PGP signature
