[SOLVED] Slackware-current 16Dec2015? update broke installation via NFS mount

kingbeowulf · 12-18-2015, 02:23 AM

I've had a PXE syslinux boot server set up for quite some time. It's more convenient than a DVD or USB stick for this recent -current upgrade cycle. Until today, installation via NFS worked ok (last used about 2 weeks ago). Both Slackware-current and Slackware64-current boot up ok, setting up drives etc is ok, and setup starts its normal cycle. However, now, when I select NFS for the installation media, mount fails. Doesn't matter if I choose to setup the network via DHCP or manually. I can mount manually just fine and NFS is set up correctly on the server (Slackware-14.1 stock) as I can mount just fine from any other Slackware box. When I exit setup, and try to mount manually,

Code:

mount -r -t nfs 192.168.1.4:/data/slackware/slackware-current/slackware /var/log/mount
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: 192.168.1.4:/data/slackware/slackware-current/slackware failed, ...
...

Adding 'nolock' works:

Code:

mount -r -t nfs -o nolock 192.168.1.4:/data/slackware/slackware-current/slackware /var/log/mount

Workaround:
In the NFS dialogs, set up network as normal, but prepend "nolock" to server address:
NFS server = '-o nolock 192.168.1.4'
directory = /data/slackware/slackware-current/slackware

Changelogs show rpcbind replaced portmap, so was something left out or a script error?

kikinovak · 12-18-2015, 02:44 AM

The December 16th update replaced portmap (obsolete) with two new packages: rpcbind and libtirpc. Check if you have these installed.

Edit: on second reading, I just understand this concerns the installation process. My bad.

nolretou · 12-18-2015, 04:58 AM

Don't forget to
chmod +x /etc/rc.d/rc.rpc
after the update.

kingbeowulf · 12-18-2015, 12:37 PM

Quote:

Originally Posted by nolretou

Don't forget to
chmod +x /etc/rc.d/rc.rpc
after the update.

sad state of affairs when no one bothers to read the actual post. I did NOT update but did a FULL install from mirrored Slackware64-current tree - as I have before 14.1. I should NOT need to chmod anything.

sanjioh · 12-19-2015, 02:18 AM

unrelated: last line of error message seems somehow left-truncated:

Code:

mount.nfs: 92.168.1.4:/data/slackware/slackware-current/slackware failed,

OldHolborn · 12-20-2015, 12:27 PM

Adding

rpcbind: 127.0.0.1

to hosts.allow

fixes the problem, and I think, correctly too

kingbeowulf · 12-20-2015, 09:33 PM

This is driving me nuts. I finally had a moment to unpack the Slackare-14.1,-current isolinux/initrd.img and compare a bit. Neither has a /etc/host.allow file or /etc/rc.d/rc.rpc file. Flipping to another console, /var/log/setup/tmp/nsfout doesn't show any errors other than the (a) successful NFS mont of Slackware-14.1 tree or (b) unsuccessful NFS mont of Slackware-current tree.

NOTE: I do not use the internal NFS server within Slackware installation media. I have my own tpftboot/syslinux on a Slackware-14.1 box.

At the NSF MOUNT RESULT dialog, I get for Slackware-14.1:

Code:

#ps -A |grep rpc
  18 ?    00:00:00 rpciod
1040 ?    00:00:00 rpc.portmap
1042 ?    00:00:00 rpc.statd

as specified in the /usr/lib/setup/INSNFS script.
However, for Slackware-current /usr/lib/setup/INSNFS script now uses rpcbind. Neither rpcbind nor rpc.statd are running but there are no errors that I can see.

Code:

#ps -A |grep -E 'rpc|bind|stat'
  29 ?    00:00:00 rpciod

Once I use '-o nolock' I can install via NFS and after a full install, chmod +x /etc/rc.d/rc.rpc, I get the expected results and NFS mounting works as it should.

Code:

#ps -A |grep rpc
  29 ?    00:00:00 rpciod
 857 ?    00:00:00 rpcbind
 863 ?    00:00:00 rpc.statd

Conclusion: There is something missing in the Slackware{32,64}-current installation media initrd.img. Is libtirpc.so missing?

EDIT: found libtirpc.so.3.0.0 and symlink libtirpc.so.3. symlink for libtirpc.so missing?

MarcT · 12-23-2015, 07:13 AM

The -current changelog from today has this:

Code:

usb-and-pxe-installers/usbboot.img: Rebuilt.
       Fixed NFS install. Thanks to Stuart Winter.

Hopefully that will resolve the issue!

kingbeowulf · 12-23-2015, 09:17 PM

and also,

Code:

isolinux/initrd.img:  Rebuilt.
  Fixed NFS install.  Thanks to Stuart Winter.
  Added nvme and sdhci-acpi kernel modules.

So I will mark this thread solved. I won't be abe to test for a few days but I wil trust our beloved BDFL!