Bug 1129425
Summary: | /usr/sbin/start-statd is unreliable | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Lutomirski <luto> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | bfields, jlayton, steved, tmraz, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://fedorahosted.org/fesco/ticket/1310 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-12-13 19:09:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1099595 |
Description
Andy Lutomirski
2014-08-12 17:56:28 UTC
(In reply to Andy Lutomirski from comment #0) > I think there are multiple problems here. The script's fallback to manually > starting rpc.statd is bad -- it starts it in the wrong context, preventing > systemd from starting it correctly in the future. But that fallback > shouldn't happen at all, and I'm not entirely sure what the issue is. The failback is needed for when systemd is not installed > > If I manually kill rpc.statd and stop all the related systemd units, then > this does seem to work: > > sudo systemctl start nfs-lock.service; sudo rpcinfo > > It shows 'status' in the output. The lockd service doesn't show up, but I > assume that's because nothing has asked the kernel to start it yet. lockd is a kernel modules that will get loaded when the NFS server is started. (In reply to Steve Dickson from comment #1) > (In reply to Andy Lutomirski from comment #0) > > I think there are multiple problems here. The script's fallback to manually > > starting rpc.statd is bad -- it starts it in the wrong context, preventing > > systemd from starting it correctly in the future. But that fallback > > shouldn't happen at all, and I'm not entirely sure what the issue is. > The failback is needed for when systemd is not installed Is that even possible on Fedora? In any case, wouldn't checking for the existence of systemctl be better than checking whether systemctl start succeeds? > > > > > If I manually kill rpc.statd and stop all the related systemd units, then > > this does seem to work: > > > > sudo systemctl start nfs-lock.service; sudo rpcinfo > > > > It shows 'status' in the output. The lockd service doesn't show up, but I > > assume that's because nothing has asked the kernel to start it yet. > lockd is a kernel modules that will get loaded when the NFS server is > started. I must be missing something here. start-statd is for the NFS *client*, I think. |