Ticket 17412

Summary:	slurmdbd: Not running as root. Can't drop supplementary groups
Product:	Slurm	Reporter:	Nate Rini <nate>
Component:	slurmdbd	Assignee:	Nate Rini <nate>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	5 - Enhancement
Priority:	---
Version:	23.11.x
Hardware:	Linux
OS:	Linux
Site:	GSK	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	NoveTech Sites:	---
Nvidia HWinf-CS Sites:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Tzag Elita Sites:	---
Linux Distro:	---	Machine Name:
CLE Version:		Version Fixed:
Target Release:	---	DevPrio:	---
Emory-Cloud Sites:	---
Ticket Depends on:	16611
Ticket Blocks:

Description Nate Rini 2023-08-11 09:14:17 MDT

splitting off bug#17301

> (In reply to Nate Rini from bug#17301 comment #16)
> 
> > it is being started as root. I would suggest having both daemons be
> > configured with systemd unit file based on the file's user/group:
> > > user=slurm
> > > group=slurm
> 
> Hi Nate -- one quick question to this. I've already added a user and a group
> to the slurmctld and slurmdbd systemd config files. However I noticed that
> the following warning / info  appears after the service restart:
> 
> Aug 11 00:58:11 us1salx09012.corpnet2.com slurmdbd[3529030]: slurmdbd: Not
> running as root. Can't drop supplementary groups
> 
> Just wanted to check with you when potentially it could cause an issue (if
> any)? What groups it is about?
> 
> Thanks,
> Radek

Need to avoid creating this log message when started by systemd:

> Aug 11 00:58:11 us1salx09012.corpnet2.com slurmdbd[3529030]: slurmdbd: Not
> running as root. Can't drop supplementary groups

Comment 5 Nate Rini 2025-01-06 13:20:03 MST

Closing this ticket as it was already implemented by dbbeb36863e via ticket#20773

*** This ticket has been marked as a duplicate of ticket 20773 ***