[opensuse-support] Unable to nfs-mount exported directories
Hi, Since a few days I'm unable to mount directories exported from my Tumbleweed system. TW is on the latest snapshot (20191112). systemctl mentions the server is running: systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-server.service.d └─options.conf /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: active (exited) since Thu 2019-11-14 10:36:32 CET; 16min ago Process: 2725 ExecStart=/usr/sbin/rpc.nfsd $NFSD_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2725 (code=exited, status=0/SUCCESS) nov 14 10:36:31 linux-mkay systemd[1]: Starting NFS server and services... nov 14 10:36:32 linux-mkay systemd[1]: Started NFS server and services. But all other systems at home are unable to mount the directories exported. Some say "Connection refused", some wait endlessly without any messages. Some time ago I was bitten by https://bugzilla.opensuse.org/show_bug.cgi?id=1151044. As a workaround for that bug was suggested to create /etc/nfs.conf.local as an empty file, and this solution worked for me back then. That file still exists, I checked. Any ideas here? regards, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 14-11-2019 om 11:04 schreef Jogchum Reitsma:
Hi,
Since a few days I'm unable to mount directories exported from my Tumbleweed system. TW is on the latest snapshot (20191112).
systemctl mentions the server is running:
systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-server.service.d └─options.conf /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: active (exited) since Thu 2019-11-14 10:36:32 CET; 16min ago Process: 2725 ExecStart=/usr/sbin/rpc.nfsd $NFSD_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2725 (code=exited, status=0/SUCCESS)
nov 14 10:36:31 linux-mkay systemd[1]: Starting NFS server and services... nov 14 10:36:32 linux-mkay systemd[1]: Started NFS server and services.
But all other systems at home are unable to mount the directories exported. Some say "Connection refused", some wait endlessly without any messages.
Some time ago I was bitten by https://bugzilla.opensuse.org/show_bug.cgi?id=1151044. As a workaround for that bug was suggested to create /etc/nfs.conf.local as an empty file, and this solution worked for me back then. That file still exists, I checked.
Any ideas here?
regards, Jogchum
Solved: the host system appeared to have gotten a new ip-address.... Why that happened beats me, it had the old address for some years now. Changed it on all the client systems, now things are working again... My apologies. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Jogchum Reitsma <j.reitsma@hccnet.nl> [11-14-19 08:43]: [...]
Solved: the host system appeared to have gotten a new ip-address.... Why that happened beats me, it had the old address for some years now. Changed it on all the client systems, now things are working again...
why not assign the "host" a static address? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thu, 14 Nov 2019, 14:51:17 +0100, Patrick Shanahan wrote:
* Jogchum Reitsma <j.reitsma@hccnet.nl> [11-14-19 08:43]: [...]
Solved: the host system appeared to have gotten a new ip-address.... Why that happened beats me, it had the old address for some years now. Changed it on all the client systems, now things are working again...
why not assign the "host" a static address?
or, at least, an IP alias? Cheers. l8er manfred
On Thu, 14 Nov 2019, 15:21:28 +0100, Manfred Hollstein wrote:
On Thu, 14 Nov 2019, 14:51:17 +0100, Patrick Shanahan wrote:
* Jogchum Reitsma <j.reitsma@hccnet.nl> [11-14-19 08:43]: [...]
Solved: the host system appeared to have gotten a new ip-address.... Why that happened beats me, it had the old address for some years now. Changed it on all the client systems, now things are working again...
why not assign the "host" a static address?
or, at least, an IP alias?
in case you run your own DNS server for the local zone, which I forgot to mention ;) Cheers. l8er manfred
participants (3)
-
Jogchum Reitsma -
Manfred Hollstein -
Patrick Shanahan