Re: [gentoo-user] Can't fetch distfiles in chroot

[Tom H]

On Thu, Apr 26, 2018 at 4:12 AM, Peter Humphrey  wrote:
>
> So, again, I went off half-cocked (sorry about the noise). The problem is that
> the NFS mount in the chroot picks different ports each time, so the client's
> firewall drops all NFS packets.
>
> Now I just have to find out why that happens.

Set up static ports for mountd and statd in "/etc/conf.d/nfs".

Set up static ports for lockd in "/etc/modprobe.d/" or
"/etc/sysctl.d/" (depending on how you compiled your kernel).

Non-official but more or less conventional ports (IIRC, first used in
an old Slackware howto):

mountd: "--port 32767"

statd: "--port 32765 --outgoing-port 32766"

lockd-sysctl.d:
fs.nfs.nlm_udpport=32768
fs.nfs.nlm_tcpport=32768

lockd--modprobe.d:
options lockd nlm_udpport=32768 nlm_tcpport=32768

[ If you want to be "modern," the nfs-utils tarball (v2.1.1 and above)
includes "nfs.conf" that you can copy into "/etc/" and edit ]

Re: [gentoo-user] Can't fetch distfiles in chroot

[Peter Humphrey]

On Thursday, 26 April 2018 09:07:51 BST Neil Bothwick wrote:
> On Thu, 26 Apr 2018 08:59:22 +0100, Peter Humphrey wrote:
> > So, again, what could possibly prevent portage from seeing the network
> > inside a chroot, while other programs use it just the same as always?
> 
> Are you using a proxy?

Nope, not since I had an unlimited data allowance.

-- 
Regards,
Peter.

Re: [gentoo-user] Can't fetch distfiles in chroot

[Peter Humphrey]

On Thursday, 26 April 2018 08:59:22 BST Peter Humphrey wrote:
> On Tuesday, 24 April 2018 09:43:35 BST Peter Humphrey wrote:
> > On Sunday, 22 April 2018 06:13:30 BST Peter Humphrey wrote:
> > > I've been NFS-exporting the portage treee from a 32-bit atom box to a
> > > chroot on my workstation, and it's worked well for years, if slowly.
> > > 
> > > Now when I try to do the same with a 64-bit celeron machine I'm having a
> > > problem getting portage to work. If the required distfile is already
> > > present, no problem, but otherwise, trying to fetch it just hangs. No
> > > errors, no status, no fetch log, no progress.
> > > 
> > > Www-client/links works in the chroot as expected, so the network is set
> > > up
> > > all right; portage just can't use it.
> > > 
> > > I've compared /etc/exports on the two clients; also the chroot setup
> > > scripts, /usr/portage permissions, the USE flags of nfs-utils and
> > > everything else I can think of. All identical apart from obvious things
> > > like 32/64 bits and network names and IPs. Google hasn't helped either.
> > > 
> > > Any ideas, anyone?
> > 
> > Never mind. I've rebuilt the chroot from stage 3 and it seems to be
> > working
> > fine.
> 
> The appearance was deceptive; all the distfiles needed must have been
> present already. Today, one wasn't and the fetching process hung and had to
> be killed.
> 
> So, again, what could possibly prevent portage from seeing the network
> inside a chroot, while other programs use it just the same as always?

So, again, I went off half-cocked (sorry about the noise). The problem is that 
the NFS mount in the chroot picks different ports each time, so the client's 
firewall drops all NFS packets.

Now I just have to find out why that happens.

-- 
Regards,
Peter.

Re: [gentoo-user] Can't fetch distfiles in chroot

[Neil Bothwick]

On Thu, 26 Apr 2018 08:59:22 +0100, Peter Humphrey wrote:

> So, again, what could possibly prevent portage from seeing the network
> inside a chroot, while other programs use it just the same as always?

Are you using a proxy?


-- 
Neil Bothwick

Top Oxymorons Number 48: freewill offering


pgpR0ZjlrCtVZ.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Can't fetch distfiles in chroot

[Peter Humphrey]

On Tuesday, 24 April 2018 09:43:35 BST Peter Humphrey wrote:
> On Sunday, 22 April 2018 06:13:30 BST Peter Humphrey wrote:
> > I've been NFS-exporting the portage treee from a 32-bit atom box to a
> > chroot on my workstation, and it's worked well for years, if slowly.
> > 
> > Now when I try to do the same with a 64-bit celeron machine I'm having a
> > problem getting portage to work. If the required distfile is already
> > present, no problem, but otherwise, trying to fetch it just hangs. No
> > errors, no status, no fetch log, no progress.
> > 
> > Www-client/links works in the chroot as expected, so the network is set up
> > all right; portage just can't use it.
> > 
> > I've compared /etc/exports on the two clients; also the chroot setup
> > scripts, /usr/portage permissions, the USE flags of nfs-utils and
> > everything else I can think of. All identical apart from obvious things
> > like 32/64 bits and network names and IPs. Google hasn't helped either.
> > 
> > Any ideas, anyone?
> 
> Never mind. I've rebuilt the chroot from stage 3 and it seems to be working
> fine.

The appearance was deceptive; all the distfiles needed must have been present 
already. Today, one wasn't and the fetching process hung and had to be killed.

So, again, what could possibly prevent portage from seeing the network inside 
a chroot, while other programs use it just the same as always?

-- 
Regards,
Peter.

Re: [gentoo-user] Can't fetch distfiles in chroot

[Peter Humphrey]

On Sunday, 22 April 2018 06:13:30 BST Peter Humphrey wrote:
> I've been NFS-exporting the portage treee from a 32-bit atom box to a chroot
> on my workstation, and it's worked well for years, if slowly.
> 
> Now when I try to do the same with a 64-bit celeron machine I'm having a
> problem getting portage to work. If the required distfile is already
> present, no problem, but otherwise, trying to fetch it just hangs. No
> errors, no status, no fetch log, no progress.
> 
> Www-client/links works in the chroot as expected, so the network is set up
> all right; portage just can't use it.
> 
> I've compared /etc/exports on the two clients; also the chroot setup
> scripts, /usr/portage permissions, the USE flags of nfs-utils and
> everything else I can think of. All identical apart from obvious things
> like 32/64 bits and network names and IPs. Google hasn't helped either.
> 
> Any ideas, anyone?

Never mind. I've rebuilt the chroot from stage 3 and it seems to be working 
fine. I only asked in the hope of not having to do that. But then, it didn't 
take too long really. Hey-ho.

-- 
Regards,
Peter.