Your message dated Mon, 8 Dec 2025 11:13:28 -0800 with message-id <CAOU6tACMhExxnwFC97vFE2R3GfA_GXu4P5r7J=tp2u6t2mp...@mail.gmail.com> and subject line Re: Bug#984996: [debian-mysql] Bug#984996: mariadb-server-core-10.5: modifies globalö environment, causing race conditions has caused the Debian Bug report #984996, regarding mariadb-server-core-10.5: modifies globalö environment, causing race conditions to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 984996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984996 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mariadb-server-core-10.5 Version: 1:10.5.9-1 Severity: normal Dear Maintainer, * What led up to the situation? various scripts (e.g. galera_new_cluster) and the systemd.unit modify the global/systemwide environment, e.g. with variables _WSREP_START_POSITION. This has the effect of polluting the environment of other sservices with these variables, which is usually pretty harmless. However, if there are multiple server instances then this creates a race condition where starting/stopping one server or bootstrapping one cluster will interfere with the other instance,s which could easily lead to database corruption. * What exactly did you do (or not do) that was effective (or ineffective)? I didn't try to solve the problem, it seems to be too fundamental to easily work around. The mechanism (systemd environment block) is wholly unsuitable to solve this problem. * What was the outcome of this action? Environment polluted, critical environment variables of other services erased/modified. * What outcome did you expect instead? A systemd service should _never_ _ever_ modify the global environment. -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 5.8.18-050818-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---The upstream issue https://jira.mariadb.org/browse/MDEV-14707 was fixed in 11.6.0 and https://github.com/mariadb-corporation/galera/pull/109 says it was fixed via another solution. As there was no additional follow-up here by the original submitter and nobody else reported this issue, and it is not easy for me to verify, I will assume now the issue is fixed and marking this closed. Feel free to re-open and provide additional information if needed.
--- End Message ---
