Bug 32378

Summary:	rpc.idmapd failing due to missing group nobody
Product:	Mageia	Reporter:	Mike Wood <michael.wood>
Component:	RPM Packages	Assignee:	Guillaume Rousse <guillomovitch>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	Normal	CC:	lewyssmith
Version:	9	Keywords:	FOR_ERRATA9
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	nfs-utils-2.6.3-1.mga9.src.rpm	CVE:
Status comment:

Description Mike Wood 2023-10-12 12:09:51 CEST

Description of problem:
rpc.idmapd fails as group nobody does not exist in Mageia 9.
Fixed by either creating the nobody group or adding the line:
Nobody-Group = nogroup
to /etc/idmapd.conf

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Lewis Smith 2023-10-12 20:17:21 CEST

Thank you for this report.
Can you say how you installed your Mageia 9? Upgrade from 8, or from an installation ISO?

My own M9 system does have group 'nobody', but it started life as an upgrade from M8; I do not know where that group came from. I can look at an M8 installation, but the group is probably present with the same unknown.

/etc/idmapd.conf is in pkg lib64nfsidmap0, SRPM as noted nfs-utils-2.6.3-1.mga9.src.rpm

Assigning to Guillaume for nfs-utils, but the problem may lie elsewhere: should any Mageia installation have group 'nobody'? If so, please change Component to Installer, and re-assign this to mageiatools CC isobuild.

Assignee: bugsquad => guillomovitch
CC: (none) => lewyssmith
Keywords: (none) => FOR_ERRATA9

Comment 2 Mike Wood 2023-10-13 09:23:29 CEST

The issue cropped up on 2 systems, one that was a recent install fron the Mageia 9 release ISO and one that had been updated from the beta release.
I have checked a VBOX image that was upgraded from Nageia 8 and it still has the nobody group.