Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
nfs-idmapd.service contains dependency on nfs-server.service on nfs client as well. The only service required at client end is nfs-idmapd. Looking at the /usr/lib/systemd/system/nfs-idmapd.service, it shows that it is binded to nfs-server.service.
Description of problem:
Restarting nfs-idmapd service is also restarting nfs-server.service as nfs-idmapd service is binded to nfs-server.service.
We can clearly see that nfs-idmapd.service is static which means that its dependent on other service.
[root@dhcp5-106 ~]# systemctl list-unit-files --type service|grep -i nfs
nfs-blkmap.service disabled
nfs-config.service static
nfs-idmap.service static
nfs-idmapd.service static
nfs-lock.service static
nfs-mountd.service static
nfs-secure-server.service static
nfs-secure.service static
nfs-server.service enabled
nfs-utils.service static
nfs.service disabled
nfslock.service static
To determine what services are ordered to start before the specified service, here is the command and output:
[root@dhcp5-106 ~]# systemctl status nfs-idmapd.service
● nfs-idmapd.service - NFSv4 ID-name mapping service
Loaded: loaded (/usr/lib/systemd/system/nfs-idmapd.service; static; vendor preset: disabled)
Active: active (running) since Sun 2016-02-07 11:49:04 IST; 2 days ago
Process: 554 ExecStart=/usr/sbin/rpc.idmapd $RPCIDMAPDARGS (code=exited, status=0/SUCCESS) Main PID: 564 (rpc.idmapd)
CGroup: /system.slice/nfs-idmapd.service
└─564 /usr/sbin/rpc.idmapd
Feb 07 11:49:04 dhcp5-106.gsslab.pnq.redhat.com systemd[1]: Starting NFSv4 ID-name mapping service...
Feb 07 11:49:04 dhcp5-106.gsslab.pnq.redhat.com systemd[1]: Started NFSv4 ID-name mapping service.
To determine what services are ordered to start before the specified service, here is the command and output:
[root@dhcp5-106 ~]# systemctl list-dependencies --after nfs-idmapd.service nfs-idmapd.service ● ├─nfs-config.service ● ├─system.slice ● ├─systemd-journald.socket ● ├─var-lib-nfs-rpc_pipefs.mount ● └─local-fs.target
● ├─-.mount
● ├─boot.mount
● ├─dm-event.service
● ├─lvm2-monitor.service
● ├─rhel-readonly.service
● ├─sys-kernel-config.mount
● ├─systemd-fsck-root.service
● ├─systemd-remount-fs.service
● └─local-fs-pre.target
● ├─systemd-remount-fs.service
● └─systemd-tmpfiles-setup-dev.service
To determine what services are ordered to start after the specified service, here is the command and output:
[root@dhcp5-106 ~]# systemctl list-dependencies --before nfs-idmapd.service nfs-idmapd.service ● └─nfs-server.service <----------here we can see nfs-server.service
There should be no need to start nfs-server.service @ nfs client end while restarting the nfs-idmapd.service.
The dependency should be removed.
(In reply to Harshula Jayasuriya from comment #3)
> My understanding is that we've moved to using nfsidmap on the NFS client
> instead of rpc.idmapd.
This is true... the client kernel does use an upcall
to nfsidmap to resolve id/gid for v4.X....
Why is restarting of rpc.idmapd evening happening?
Description of problem: Restarting nfs-idmapd service is also restarting nfs-server.service as nfs-idmapd service is binded to nfs-server.service. We can clearly see that nfs-idmapd.service is static which means that its dependent on other service. [root@dhcp5-106 ~]# systemctl list-unit-files --type service|grep -i nfs nfs-blkmap.service disabled nfs-config.service static nfs-idmap.service static nfs-idmapd.service static nfs-lock.service static nfs-mountd.service static nfs-secure-server.service static nfs-secure.service static nfs-server.service enabled nfs-utils.service static nfs.service disabled nfslock.service static To determine what services are ordered to start before the specified service, here is the command and output: [root@dhcp5-106 ~]# systemctl status nfs-idmapd.service ● nfs-idmapd.service - NFSv4 ID-name mapping service Loaded: loaded (/usr/lib/systemd/system/nfs-idmapd.service; static; vendor preset: disabled) Active: active (running) since Sun 2016-02-07 11:49:04 IST; 2 days ago Process: 554 ExecStart=/usr/sbin/rpc.idmapd $RPCIDMAPDARGS (code=exited, status=0/SUCCESS) Main PID: 564 (rpc.idmapd) CGroup: /system.slice/nfs-idmapd.service └─564 /usr/sbin/rpc.idmapd Feb 07 11:49:04 dhcp5-106.gsslab.pnq.redhat.com systemd[1]: Starting NFSv4 ID-name mapping service... Feb 07 11:49:04 dhcp5-106.gsslab.pnq.redhat.com systemd[1]: Started NFSv4 ID-name mapping service. To determine what services are ordered to start before the specified service, here is the command and output: [root@dhcp5-106 ~]# systemctl list-dependencies --after nfs-idmapd.service nfs-idmapd.service ● ├─nfs-config.service ● ├─system.slice ● ├─systemd-journald.socket ● ├─var-lib-nfs-rpc_pipefs.mount ● └─local-fs.target ● ├─-.mount ● ├─boot.mount ● ├─dm-event.service ● ├─lvm2-monitor.service ● ├─rhel-readonly.service ● ├─sys-kernel-config.mount ● ├─systemd-fsck-root.service ● ├─systemd-remount-fs.service ● └─local-fs-pre.target ● ├─systemd-remount-fs.service ● └─systemd-tmpfiles-setup-dev.service To determine what services are ordered to start after the specified service, here is the command and output: [root@dhcp5-106 ~]# systemctl list-dependencies --before nfs-idmapd.service nfs-idmapd.service ● └─nfs-server.service <----------here we can see nfs-server.service There should be no need to start nfs-server.service @ nfs client end while restarting the nfs-idmapd.service. The dependency should be removed.