Mailing List Archive

NFS connection refused
Hello list,

This machine is a compute-server for other machines on the network, which it
does by NFS-mounting the portage directories in a chroot. You may remember
that I've messed about a bit with USE flags and the like, but only on this
machine, the compute server and NFS client. The other machine, the NFS server,
has not been touched.

I've tried wikis and man pages, and I've compared the current config with
historical ones, but I can't find anything wrong, or even different.

Does the output attached suggest anything? (It's a bit long to be in line.)

The NFS host shows no log messages at all. Both the firewalls are exactly the
same as they have been for years.

/etc/exports on the NFS host:

# cat /etc/exports
# /etc/exports: NFS file systems being exported. See exports(5).
/mnt/nfs \
192.168.178.7(rw,sync,no_subtree_check,anonuid=250,anongid=250,crossmnt,fsid=0)
/mnt/nfs/portage \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
/mnt/nfs/portage.packages \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
/mnt/nfs/portage.distfiles \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
/mnt/nfs/port.resc \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
/mnt/nfs/port.resc.packages \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
/mnt/nfs/port.resc.distfiles \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)

Also on the NFS host:
# mount | grep nfs
/dev/sda6 on /mnt/nfs/portage type ext4 (rw,noatime)
/dev/sda9 on /mnt/nfs/portage.packages type ext4 (rw,noatime)
/dev/sda10 on /mnt/nfs/portage.distfiles type ext4 (rw,noatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)

# grep nfs /etc/fstab
/var/db/repos/gentoo /mnt/nfs/portage none bind 0 0
/var/cache/packages /mnt/nfs/portage.packages none bind 0 0
/var/cache/distfiles /mnt/nfs/portage.distfiles none bind 0 0

The compute host is 192.168.178.7, the NFS host is 192.168.178.2.

--
Regards,
Peter.
Re: NFS connection refused [ In reply to ]
On Friday, 20 May 2022 15:35:25 BST Peter Humphrey wrote:
> Hello list,
>
> This machine is a compute-server for other machines on the network, which it
> does by NFS-mounting the portage directories in a chroot. You may remember
> that I've messed about a bit with USE flags and the like, but only on this
> machine, the compute server and NFS client. The other machine, the NFS
> server, has not been touched.
>
> I've tried wikis and man pages, and I've compared the current config with
> historical ones, but I can't find anything wrong, or even different.
>
> Does the output attached suggest anything? (It's a bit long to be in line.)
>
> The NFS host shows no log messages at all. Both the firewalls are exactly
> the same as they have been for years.

In fact, I'd missed the one clue, as it was days old: rpcbind failed to start
during boot. it said it couldn't find a transport. I'm poking into that, but I
haven't found it yet...

--
Regards,
Peter.