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
Transition | Time In Source Status | Execution Times |
---|
|
1578d 7m | 1 |
|
5d 20h 50m | 1 |
|
41d 13h 2m | 1 |
|
92d 5h 44m | 1 |
|
124d 13m | 1 |
|
37d 54m | 1 |