[opensuse-factory] Tumbleweed update to 20200201 destroyed nfs/nfs-server
I have five local Tumbleweed machine that can no longer utilize nfs nor nfs-server since the movement of /etc/services & company to /usr/ No changes have been made to firewall since nfs was working, but disabling firewall does not enable nfs connection(s). Have temporarily converted nearly everything to sshfs. I can access nfs exports from a server running a locked down 42.2. <correction> I *could* ... <more> 192.168.1.10 yast nfs while adding another export from a newly installed Tw reports it cannot access 2 nfs shares from the 42.2 server. BUT I can access those shares. I cannot access the nfs share from the new Tw box. will reboot desktop, 192.168.1.10, and see if any nfs shares survive. *** The shares from the 42.2 server survived, including the ones yast reported broken but the new share from the new Tw did not mount and I cannot mount manually. So another attempt to add an nfs share from the new Tw (192.168.1.8). yast reports: new share failed (show parameters) stderr: mount.nfs: No route to host exit code 32 and: Mounting 192.168.1.8:/home/paka at /mnt/nfs/crash2-paka Unexpected situation found in the system. Click below to see more details (English only). Continue despite the error? details: command '/bin/mount -t nfs '192.168.1.8:/home/paka' '/mnt/nfs/crash2-paka'' failed: stderr: mount.nfs: No route to host exit code: 32 <ok> said to continue despite error: nfs share mount was added to /etc/fstab manual attempt to mount from 192.168.1.10: mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.8,clientaddr=192.168.1.10' mount.nfs: mount(2): No route to host attempts to share from 192.168.1.10 provide similar results I have no idea where to go next to trouble-shoot this issue. -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Feb 08, 2020 at 11:19:34AM -0500, Patrick Shanahan wrote:
I have five local Tumbleweed machine that can no longer utilize nfs nor nfs-server since the movement of /etc/services & company to /usr/
No changes have been made to firewall since nfs was working, but disabling firewall does not enable nfs connection(s).
Have temporarily converted nearly everything to sshfs.
I can access nfs exports from a server running a locked down 42.2. <correction> I *could* ...
<more> 192.168.1.10 yast nfs while adding another export from a newly installed Tw reports it cannot access 2 nfs shares from the 42.2 server. BUT I can access those shares. I cannot access the nfs share from the new Tw box.
will reboot desktop, 192.168.1.10, and see if any nfs shares survive.
***
The shares from the 42.2 server survived, including the ones yast reported broken but the new share from the new Tw did not mount and I cannot mount manually.
So another attempt to add an nfs share from the new Tw (192.168.1.8). yast reports: new share failed (show parameters) stderr: mount.nfs: No route to host exit code 32
and: Mounting 192.168.1.8:/home/paka at /mnt/nfs/crash2-paka Unexpected situation found in the system. Click below to see more details (English only). Continue despite the error?
details: command '/bin/mount -t nfs '192.168.1.8:/home/paka' '/mnt/nfs/crash2-paka'' failed: stderr: mount.nfs: No route to host exit code: 32
<ok> said to continue despite error:
nfs share mount was added to /etc/fstab manual attempt to mount from 192.168.1.10: mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.8,clientaddr=192.168.1.10' mount.nfs: mount(2): No route to host
attempts to share from 192.168.1.10 provide similar results
I have no idea where to go next to trouble-shoot this issue.
Check if /etc/nsswitch.conf.rpmnew exists and merge it into /etc/nsswitch.conf Basically it needs "usrfiles" in the services related entries now: grep usrf /etc/nsswitch.conf.rpmnew services: files usrfiles protocols: files usrfiles rpc: files usrfiles ethers: files usrfiles aliases: files usrfiles Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Marcus Meissner <meissner@suse.de> [02-08-20 11:39]:
On Sat, Feb 08, 2020 at 11:19:34AM -0500, Patrick Shanahan wrote:
I have five local Tumbleweed machine that can no longer utilize nfs nor nfs-server since the movement of /etc/services & company to /usr/
No changes have been made to firewall since nfs was working, but disabling firewall does not enable nfs connection(s).
Have temporarily converted nearly everything to sshfs.
I can access nfs exports from a server running a locked down 42.2. <correction> I *could* ...
<more> 192.168.1.10 yast nfs while adding another export from a newly installed Tw reports it cannot access 2 nfs shares from the 42.2 server. BUT I can access those shares. I cannot access the nfs share from the new Tw box.
will reboot desktop, 192.168.1.10, and see if any nfs shares survive.
***
The shares from the 42.2 server survived, including the ones yast reported broken but the new share from the new Tw did not mount and I cannot mount manually.
So another attempt to add an nfs share from the new Tw (192.168.1.8). yast reports: new share failed (show parameters) stderr: mount.nfs: No route to host exit code 32
and: Mounting 192.168.1.8:/home/paka at /mnt/nfs/crash2-paka Unexpected situation found in the system. Click below to see more details (English only). Continue despite the error?
details: command '/bin/mount -t nfs '192.168.1.8:/home/paka' '/mnt/nfs/crash2-paka'' failed: stderr: mount.nfs: No route to host exit code: 32
<ok> said to continue despite error:
nfs share mount was added to /etc/fstab manual attempt to mount from 192.168.1.10: mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.8,clientaddr=192.168.1.10' mount.nfs: mount(2): No route to host
attempts to share from 192.168.1.10 provide similar results
I have no idea where to go next to trouble-shoot this issue.
Check if /etc/nsswitch.conf.rpmnew exists and merge it into /etc/nsswitch.conf
No, I merged nsswitch.conf.rpmnew about a week ago on all systems.
Basically it needs "usrfiles" in the services related entries now:
grep usrf /etc/nsswitch.conf.rpmnew services: files usrfiles protocols: files usrfiles rpc: files usrfiles ethers: files usrfiles aliases: files usrfiles
# grep usrf /etc/nsswitch.conf services: files usrfiles protocols: files usrfiles rpc: files usrfiles ethers: files usrfiles aliases: files usrfiles tks, -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marcus Meissner composed on 2020-02-08 17:37 (UTC+0100):
On Sat, Feb 08, 2020 at 11:19:34AM -0500, Patrick Shanahan wrote:
I have five local Tumbleweed machine that can no longer utilize nfs nor nfs-server since the movement of /etc/services & company to /usr/ ... Check if /etc/nsswitch.conf.rpmnew exists and merge it into /etc/nsswitch.conf
Basically it needs "usrfiles" in the services related entries now:
grep usrf /etc/nsswitch.conf.rpmnew services: files usrfiles protocols: files usrfiles rpc: files usrfiles ethers: files usrfiles aliases: files usrfiles
Thanks for this thread! I looked in changelogs for nfs-client, nfs-kernel-server and netcfg and found nothing about nfs-server failure to connect it to an upgrade from 20200121 to 20200205. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Felix Miata -
Marcus Meissner -
Patrick Shanahan