O79VPfAiggsHfx5v+E=; b=V8H8rZkBVIck2+R1NayP7y5x00+fc9QGsa1j6gb7MeeppTP1fN56cL5Z56Aej61cZm NC2/XPxYStDiQB32hNVmzvC7hbFXqtqAzPPvVHDu10P8LGXzyclw1SG7AnPGcFrTKhk/ kAhE9YJ337euA7AvMWz27EVItUAvlLsWMa2QlG5mtKUJaUrM4Kb4XuRucC6RYIUFOhx7 bn/zv4ICrgXcboEkRSqOTSLwatRyvr9kDQfjvW+WtZiEAa0XqRpT3ps1mmV2MRG3oE7C 0vwyqsMuKGSIgCct7uhdNUlbNpFIsFEJWUcM+xkv+MC4fR1nQworDd4i65+IvJ1O9hqo /HGg== X-Gm-Message-State: AOJu0YyPPqHzBEJHJmPOATjr287dnqBI0X4SqZoIMYMPljXuRabvQfkZ feL6G26fj4Tlkx3bbyiuSY9pQSR3hJH8+byj5Fji9CQnt2Dkq7cbz6tGkcoMst0L3GDcToJQDFM QYo3lZxpncz8sYKGVbrlFFzEJqkSS X-Google-Smtp-Source: AGHT+IFqOPCLUO3OZkRJkzC/p46aKo85YEASe1bs9pkr1cL7s6K9XqMuLgvZPEDjNOt/HgIHsnyhqnA9E3tBIEZhoa4= X-Received: by 2002:a05:6a20:c51c:b0:1bd:272a:84ed with SMTP id adf61e73a8af0-1bd272a8623mr6500313637.61.1719505801893; Thu, 27 Jun 2024 09:30:01 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Thu, 27 Jun 2024 09:29:51 -0700 Message-ID: Subject: Re: new error messages after upgrade 14.0-p5 to 14.1-p1 amd64 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.80 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.80)[-0.802]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::531:from] X-Rspamd-Queue-Id: 4W93vH3RRTz4QR2 On Thu, Jun 27, 2024 at 7:52=E2=80=AFAM void wrote: > > After upgrading, I noticed messages like these appearing during > rebooting, immediately after kernel: NFS access cache time=3D60 > > kernel: rpc.umntall: 10.1.1.102: MOUNTPROG: RPC: Port mapper failure - RP= C: Timed out > > sometimes it appears twice, once it appeared five times. The system > eventually completes booting and there are no more messages like this. It indicates that mount_nfs is having trouble talking to rpcbind, but I do = not know why that would happen? Do you have either of these lines in your /etc/rc.conf? (Having either one of them should be sufficient to ensure rpcbind is started before the mount is attempted.) rpcbind_enable=3D"YES" nfs_client_enable=3D"YES" If you have at least one of these in your /etc/rc.conf, then all I can thin= k of is some sort of network/routing issue that interferes with rpcbind worki= ng. You can also look at the output of: # rpcinfo once it is booted, to see that rpcbind seems correctly configured. It should be attached to tcp, tcp6, udp, udp6 and /var/run/rpcbind.sock. rick > > /etc/fstab has the following > > 10.1.1.102:/usr/src /usr/src nfs rw,readahead=3D16,late 0 0 > > Logging in, the nfs share is mounted normally. > -- >