Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
We used to run systemctl set-environment to pass _WSREP_START_POSITION. This is bad because:
- it clutter systemd's environment (yes, pid 1) - upsets some Debian people dbz 984996
- it requires root privileges - hence it will fix
MDEV-14707, as such it cases all ExecStartPre scripts to be run as root. PermissionsStartOnly was deprecated by systemd in 2018. - options (like LimitNOFILE=) are not applied to ExecStartPre scripts.
The solution is:
Let's just create an environment file in ExecStartPre=, that is read before ExecStart= kicks in. We have _WSREP_START_POSITION around for the main process without any downsides.
Attachments
Issue Links
- relates to
-
MDEV-14707 systemd: remove PermissionsStartOnly=true (by removing environment _WSREP_START_POSITION)
-
- Closed
-
-
MDEV-23110 Support for Galera Multi-Instance in systemd unit file
-
- Open
-
-
MDEV-29884 Ctrl-Cing out of galera_new_cluster doesn't reset systemd environment
-
- Open
-
-
MDEV-35904 Warnings about undefined variables with systemd starting with version v254
-
- Confirmed
-
Activity
Field | Original Value | New Value |
---|---|---|
Labels | systemd |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.3 [ 22126 ] |
Assignee | Axel Schwenke [ axel ] |
Link | This issue relates to MDEV-23110 [ MDEV-23110 ] |
Assignee | Axel Schwenke [ axel ] | Daniel Black [ danblack ] |
Workflow | MariaDB v3 [ 95268 ] | MariaDB v4 [ 141249 ] |
Link |
This issue relates to |
Link | This issue relates to MDEV-29884 [ MDEV-29884 ] |
Fix Version/s | 10.4.31 [ 29010 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Stalled [ 10000 ] |
Fix Version/s | 10.4.31 [ 29010 ] |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] |
Status | Stalled [ 10000 ] | In Review [ 10002 ] |
Description |
We used to run systemctl set-environment to pass _WSREP_START_POSITION. This is bad because:
* it clutter systemd's environment (yes, pid 1) - upsets some Debian people [dbz 984996|https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984996] * it requires root privileges - hence it will fix * options (like LimitNOFILE=) are not applied to ExecStartPre scripts. The solution is: Let's just create an environment file in ExecStartPre=, that is read before ExecStart= kicks in. We have _WSREP_START_POSITION around for the main process without any downsides. |
Status | In Review [ 10002 ] | In Testing [ 10301 ] |
Fix Version/s | 11.4 [ 29301 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] |
Assignee | Daniel Black [ danblack ] |
Assignee | Daniel Black [ danblack ] |
Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
Fix Version/s | 11.6 [ 29515 ] | |
Fix Version/s | 11.4 [ 29301 ] |
Fix Version/s | 11.6.0 [ 29839 ] | |
Fix Version/s | 11.6 [ 29515 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link | This issue relates to MDEV-35904 [ MDEV-35904 ] |