Description of problem: After upgrade to Rawhide nfslock doesn't start: bradford:~# systemctl status nfslock.service nfslock.service - LSB: Start up the NFS file locking sevice Loaded: loaded (/etc/rc.d/init.d/nfslock) Active: failed since Sun, 17 Jul 2011 23:16:20 +0200; 3s ago Process: 2523 ExecStart=/etc/rc.d/init.d/nfslock start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/nfslock.service bradford:~# tail /var/log/messages Jul 17 23:15:41 bradford NetworkManager[1049]: <info> nameserver '192.168.1.13' Jul 17 23:15:41 bradford dbus[1079]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Jul 17 23:15:41 bradford dbus[1079]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 17 23:15:43 bradford nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/90-ipv6-tunnel' exited with error status 127. Jul 17 23:15:43 bradford NMdispatch-dnsmasq: INTERFACE=wlan0, UPDOWN=dhcp4-change Jul 17 23:16:20 bradford rpc.statd[2537]: Version 1.2.4 starting Jul 17 23:16:20 bradford sm-notify[2538]: Version 1.2.4 starting Jul 17 23:16:20 bradford rpc.statd[2537]: failed to create RPC listeners, exiting Jul 17 23:16:20 bradford systemd[1]: nfslock.service: control process exited, code=exited status=1 Jul 17 23:16:20 bradford systemd[1]: Unit nfslock.service entered failed state. bradford:~# Version: nfs-utils-1.2.4-2.fc16.x86_64
Checking 'systemctl status nfslock.service' shows that this tries to run: ... Process: 1211 ExecStart=/etc/rc.d/init.d/nfslock start ... ... and fails. OTOH tracing '/etc/rc.d/init.d/nfslock start' one can see that sourcing from that file /etc/rc.d/init.d/functions results in an attempt to run 'systemctl_redirect /etc/init.d/nfslock start' which ends up with a circular run of '/bin/systemctl start nfslock.service' and we are back when we started. It seems to me that this is very unlikely to run.
Michal: we actually guard against that and forward things to systemctl only if the PPID is not 1. So this is not the explanation here.
(In reply to comment #2) > ... and forward things to systemctl only if the PPID is not 1. I am not entirely sure what is "the PPID" but we are not running here init so it will be not 1. > So this is not the explanation here. In such case maybe this is related to bug 725259? In the current rawhide attempts to start NFS just failed. Yes, I know that nfslock should be able to run independently.
(In reply to comment #3) > I am not entirely sure what is "the PPID" but we are not running here init so > it will be not 1. Parent PID. Every process (aside from process 1) has some parent.
Hmm... I bet this has to with changes I made to rpcbind.... I converted rpcbind to use systemd but not nfs-utils...
I've started manually systemctl start rpcbind.service systemctl restart nfs.service And it now works for me.
(In reply to comment #6) > I've started manually > > systemctl start rpcbind.service > > systemctl restart nfs.service > > And it now works for me. Ok... thanks for verifying that... I'm working on the nfs-utils conversion atm...
(In reply to comment #6) > I've started manually > > systemctl start rpcbind.service > > systemctl restart nfs.service That looks like pertinent to bug 725259 and not that one which was about nfslock. :-) But indeed nfslock requires at least rpc.statd and starting rpcbind.service seems to help in case of nfslock.service too. OTOH NFS would like to see rpc.mountd and rpc.rquotad running (and not necessarily rpc.statd, right?).
*** This bug has been marked as a duplicate of bug 699040 ***