[Bug 1815901] [NEW] Service: Group name with whitespace not working anymore
Dirk Heinrichs
1815901 at bugs.launchpad.net
Thu Feb 14 12:17:36 UTC 2019
Public bug reported:
On Ubuntu 16.04.x, I have a perfectly working custom systemd service
file which sets username and group for the service as
[Service]
User=user
Group=domain users
where both group and user come from an AD domain joined to with winbind.
This is not working anymore on 18.04. Even with the group name quoted,
or mangled with systemd-escape. The service doesn't start with one of
the following messages in the journal (depending on how it's spelled):
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain users
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: "domain users"
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\x20users
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\ users
The only thing that works is to use the GID instead of the group name.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.12
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Feb 14 12:58:59 2019
InstallationDate: Installed on 2019-01-28 (16 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
LC_COLLATE=C
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/he--puppet--dev04-root ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815901
Title:
Service: Group name with whitespace not working anymore
Status in systemd package in Ubuntu:
New
Bug description:
On Ubuntu 16.04.x, I have a perfectly working custom systemd service
file which sets username and group for the service as
[Service]
User=user
Group=domain users
where both group and user come from an AD domain joined to with
winbind.
This is not working anymore on 18.04. Even with the group name quoted,
or mangled with systemd-escape. The service doesn't start with one of
the following messages in the journal (depending on how it's spelled):
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain users
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: "domain users"
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\x20users
/lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\ users
The only thing that works is to use the GID instead of the group name.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.12
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Feb 14 12:58:59 2019
InstallationDate: Installed on 2019-01-28 (16 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
LC_COLLATE=C
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/he--puppet--dev04-root ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815901/+subscriptions
More information about the foundations-bugs
mailing list