On 31/01/15 21:32, Genes Lists wrote:
On 01/31/2015 04:28 PM, Bardur Arantsson wrote:
On 01/31/2015 10:14 PM, Genes Lists wrote:
This was original thread: https://lists.archlinux.org/pipermail/arch-general/2014-June/036617.html
So I tried the same commands - specifically:
systemctl restart proc-fs-nfsd.mount
systemctl restart rpcbind systemctl restart nfs-mountd.service systemctl restart rpc-statd.service systemctl restart nfs-idmapd.service systemctl restart rpc-svcgssd.service systemctl restart rpc-statd-notify.service systemctl restart nfs-mountd systemctl restart rpc-gssd.service rpc-svcgssd.service
rpc-statd still does not start but now .. it failes with rpc-statd.service start operation timed out. Terminating.
After 5 mins i tried nfs-server which now starts ... rpc-statd is still not running.
And the server is once again serving NFS.
This is a real mess ... eeeek!!
At last NFS server is up now ... but yikes I need help so this starts by itself again.
thanks!
I've been having a few rather strange problems recently with services requiring an upped network interface starting before the interface is up, this is using systemd-networkd-wait-online.service. In any case, it is possible you are having a similar problem, are you sure the interfaces nfs-server is set to listen on are up? -- Tomasz Kramkowski E-Mail: tk@the-tk.com PGP: 6FCE87503AAF42AB3BF4 94FE40B037BA0A5B8680