For several weeks, maybe several months, most of my Rawhide installations generate an error trying to mount noauto nfs items in fstab:
Job for rpc-statd.service failed. See 'systemctl status rpc-statd.service' and 'journalctl -xn' for details.
Output from those: [start]rpc-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; enabled) Active: failed (Result: exit-code) since Thu 2014-05-29 00:41:00 EDT; 3min 12s ago Process: 691 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE)
May 29 00:40:00 g5eas systemd[1]: Starting NFS status monitor for NFSv2/3 locking.... May 29 00:40:00 g5eas rpc.statd[692]: Version 1.3.0 starting May 29 00:40:00 g5eas rpc.statd[692]: Flags: TI-RPC May 29 00:41:00 g5eas rpc.statd[692]: failed to create RPC listeners, exiting May 29 00:41:00 g5eas systemd[1]: rpc-statd.service: control process exited, code=exited status=1 May 29 00:41:00 g5eas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. May 29 00:41:00 g5eas systemd[1]: Unit rpc-statd.service entered failed state. -- Logs begin at Sat 2014-03-22 18:49:34 EDT, end at Thu 2014-05-29 00:41:00 EDT. -- May 29 00:40:00 g5eas rpcbind[693]: cannot create socket for tcp6 May 29 00:40:00 g5eas systemd[1]: Started RPC bind service. -- Subject: Unit rpcbind.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rpcbind.service has finished starting up. -- -- The start-up result is done. May 29 00:40:07 g5eas systemd[1]: Starting Stop Read-Ahead Data Collection... -- Subject: Unit systemd-readahead-done.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.service has begun starting up. May 29 00:40:07 g5eas systemd[1]: Started Stop Read-Ahead Data Collection. -- Subject: Unit systemd-readahead-done.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.service has finished starting up. -- -- The start-up result is done. May 29 00:41:00 g5eas rpc.statd[692]: failed to create RPC listeners, exiting May 29 00:41:00 g5eas systemd[1]: rpc-statd.service: control process exited, code=exited status=1 May 29 00:41:00 g5eas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. -- Subject: Unit rpc-statd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rpc-statd.service has failed. -- -- The result is failed. May 29 00:41:00 g5eas systemd[1]: Unit rpc-statd.service entered failed state. May 29 00:41:00 g5eas rpc.statd[709]: Version 1.3.0 starting May 29 00:41:00 g5eas rpc.statd[709]: Flags: TI-RPC [end]
I see no similar problem in Factory or Cauldron using identical fstab entries and mount syntax. What needs to be done to eliminate this delay?