Page 1 of 1

nfs-idmapd.service fails after Mageia upgrade

PostPosted: Mar 11th, '24, 11:16
by magfan
After upgrading from mga8 to mga9, I get an error message when booting the system that "nfs-idmapd.service" was not started.

Code: Select all
$ systemctl status nfs-idmapd.service
× nfs-idmapd.service - NFSv4 ID-name mapping service
     Loaded: loaded (/usr/lib/systemd/system/nfs-idmapd.service; static)
     Active: failed (Result: exit-code) since Mon 2024-03-11 09:53:04 CET; 11min ago
    Process: 1174 ExecStart=/usr/sbin/rpc.idmapd (code=exited, status=1/FAILURE)
        CPU: 2ms

Mär 11 09:53:04 amygdala systemd[1]: Starting nfs-idmapd.service...
Mär 11 09:53:04 amygdala systemd[1]: nfs-idmapd.service: Control process exited, code=exited, status=1/FAILURE
Mär 11 09:53:04 amygdala systemd[1]: nfs-idmapd.service: Failed with result 'exit-code'.
Mär 11 09:53:04 amygdala systemd[1]: Failed to start nfs-idmapd.service.
$


This service seems to be dependent on nfs-server.service, which was started without any problems:

Code: Select all
$ cat /usr/lib/systemd/system/nfs-idmapd.service
[Unit]
Description=NFSv4 ID-name mapping service
DefaultDependencies=no
Requires=rpc_pipefs.target
After=rpc_pipefs.target local-fs.target

BindsTo=nfs-server.service

[Service]
Type=forking
ExecStart=/usr/sbin/rpc.idmapd
$
$ systemctl status nfs-server.service
● nfs-server.service - NFS server and services
     Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; preset: disabled)
    Drop-In: /run/systemd/generator/nfs-server.service.d
             └─order-with-mounts.conf
     Active: active (exited) since Mon 2024-03-11 09:53:06 CET; 15min ago
    Process: 1362 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
    Process: 1366 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
    Process: 2545 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then systemctl reload gssproxy ; fi (code=exited, st>
   Main PID: 2545 (code=exited, status=0/SUCCESS)
        CPU: 22ms

Mär 11 09:53:06 amygdala systemd[1]: Starting nfs-server.service...
Mär 11 09:53:06 amygdala systemd[1]: Finished nfs-server.service.
$

How can I solve this problem?

Re: nfs-idmapd.service fails after Mageia upgrade

PostPosted: Mar 11th, '24, 18:32
by doktor5000
Where do you get that error message? And what happens if you run /usr/sbin/rpc.idmapd directly ?
Also please show your /etc/exports, and mention whether you want to use NFSv3 or NFSv4. And is that server running on hardware or in a VM/container ?

edit: Do you actually want to use ID mapping with NFSv4 or do you only want to get rid of the message? In the latter case you could simply mask nfs-idmapd.service

Re: nfs-idmapd.service fails after Mageia upgrade

PostPosted: Mar 12th, '24, 15:50
by magfan
Where do you get that error message?


When booting the system.

And what happens if you run /usr/sbin/rpc.idmapd directly ?


Code: Select all
# /usr/sbin/rpc.idmapd
#


Also please show your /etc/exports


Code: Select all
# cat /etc/exports
# generated by drakhosts.pl
/data 10.168.44.33(no_root_squash,async,no_subtree_check,rw)
#


I prefer NFS4. The server runs on hardware and the mounting of /data works. So I will probably just hide the message by masking nfs-idmapd.service.

Re: nfs-idmapd.service fails after Mageia upgrade

PostPosted: Mar 12th, '24, 19:22
by doktor5000
If this is reproducible on a fresh install you should probably still report it as a bug.