https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289711
--- Comment #10 from Peter Much <[email protected]> ---
(In reply to Rick Macklem from comment #9)
Yes that is interesting. I have also some interesting things observed. I had to
hunt a bug crashing my apache webserver (lingering there for apparently 20+
years with nobody bothering), so I had to rebuild it a couple of times.
Rebuiling with stdout/err redirected into /usr/ports/www/apache24, into the
NFS, most invocations of ranlib get stuck in 'nfstryop' and take an eternity.
NOT redirecting the output, things run normally. but the server's syslog gets
occasionally flooded with this kind of messages:
Feb 25 15:23:02 <kern.crit> edge kernel: [598789] nfsrv_cache_session: no
session IPaddr=192.168.97.5, check NFS clients for unique /etc/hostid's
Feb 25 15:23:03 <kern.crit> edge kernel: [598790] nfsrv_cache_session: no
session IPaddr=192.168.97.5, check NFS clients for unique /etc/hostid's
Feb 25 15:23:04 <kern.crit> edge kernel: [598791] nfsrv_cache_session: no
session IPaddr=192.168.97.5, check NFS clients for unique /etc/hostid's
Feb 25 15:23:08 <kern.crit> edge kernel: [598795] nfsrv_cache_session: no
session IPaddr=192.168.97.5, check NFS clients for unique /etc/hostid's
I checked that hostid, it looks fine, and it is recorded in nfs-stablerestart
on the server also hundreds of times.
There is also some interesting data in the client syslog:
Feb 25 15:12:41 vbuild0 kernel: Initiate recovery. If server has not rebooted,
check NFS clients for unique /etc/hostid's
Feb 25 15:12:41 vbuild0 syslogd: last message repeated 2 times
Feb 25 15:12:41 vbuild0 kernel: nfscl: never fnd open
Feb 25 15:17:02 vbuild0 kernel: nfsv4 expired locks lost
Feb 25 15:17:24 vbuild0 kernel: Initiate recovery. If server has not rebooted,
check NFS clients for unique /etc/hostid's
Feb 25 15:17:45 vbuild0 syslogd: last message repeated 4 times
Feb 25 15:23:02 vbuild0 syslogd: last message repeated 1 times
Feb 25 15:23:14 vbuild0 syslogd: last message repeated 2 times
Setting debuglevel=1 on the client gives a bit more data, but rather
unintellegible to me.
At 20:55:31 is the delay, and 20:59:24 is reflected on the server with this:
Feb 25 20:59:24 <kern.crit> edge kernel: [618971] nfsrv_cache_session: no
session IPaddr=192.168.97.5, check NFS clients for unique /etc/hostid's
Feb 25 20:59:24 <kern.crit> edge syslogd: last message repeated 3 times
Feb 25 20:53:25 vbuild0 kernel: proc=69 reps=10025
Feb 25 20:53:25 vbuild0 kernel: exchangeid err=0 reps=0
Feb 25 20:53:25 vbuild0 kernel: aft exch=0
Feb 25 20:53:25 vbuild0 kernel: aft createsess=0
Feb 25 20:53:25 vbuild0 kernel: aft reclaimcomp=0
Feb 25 20:53:25 vbuild0 kernel: cbproc=0
Feb 25 20:53:25 vbuild0 kernel: cbrep sent
Feb 25 20:55:00 vbuild0 kernel: proc=69 reps=10025
Feb 25 20:55:00 vbuild0 kernel: exchangeid err=0 reps=0
Feb 25 20:55:00 vbuild0 kernel: aft exch=0
Feb 25 20:55:00 vbuild0 kernel: aft createsess=0
Feb 25 20:55:00 vbuild0 kernel: aft reclaimcomp=0
Feb 25 20:55:00 vbuild0 kernel: cbproc=0
Feb 25 20:55:00 vbuild0 kernel: cbrep sent
Feb 25 20:55:00 vbuild0 kernel: proc=14 reps=10008
Feb 25 20:55:31 vbuild0 syslogd: last message repeated 15 times
Feb 25 20:57:01 vbuild0 syslogd: last message repeated 6 times
Feb 25 20:59:24 vbuild0 kernel: proc=2 reps=10025
Feb 25 20:59:24 vbuild0 kernel: exchangeid err=0 reps=0
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10011
Feb 25 20:59:24 vbuild0 kernel: aft exch=0
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10011
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10052
Feb 25 20:59:24 vbuild0 kernel: fop=53 fst=10052
Feb 25 20:59:24 vbuild0 kernel: failed seq=10052
Feb 25 20:59:24 vbuild0 kernel: Got badsession
Feb 25 20:59:24 vbuild0 kernel: Initiate recovery. If server has not rebooted,
check NFS clients for unique /etc/hostid's
Feb 25 20:59:24 vbuild0 kernel: Marked defunct
Feb 25 20:59:24 vbuild0 kernel: aft createsess=0
Feb 25 20:59:24 vbuild0 kernel: nop=53 nst=10052
Feb 25 20:59:24 vbuild0 kernel: aft reclaimcomp=0
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10025
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10025
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10025
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10025
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10025
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10025
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10025
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10025
Feb 25 20:59:24 vbuild0 kernel: cbproc=0
Feb 25 20:59:24 vbuild0 kernel: cbrep sent
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10025
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10025
Feb 25 20:59:24 vbuild0 kernel: proc=35 reps=10025
Feb 25 20:59:24 vbuild0 kernel: n2op=8 n2st=10025
...
--
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.