Re: Problem with woody statd? (was Re: RPC failures)

[Jonathan D. Proulx]

Hi,

I've been having NFS locking trouble on my sid system for a while, but
never got around to really looking at it.  Based no your mail I did a
little debuging and discovered statd was dying here too with:

[EMAIL PROTECTED] jon]$ sudo /sbin/rpc.statd  -F -d
06/20/2001 12:19:25 rpc.statd[6177]: Version 0.3.2 Starting
06/20/2001 12:19:25 rpc.statd[6177]: Flags: No-Daemon Log-STDERR 
/sbin/rpc.statd: error while loading shared libraries:
/sbin/rpc.statd: symbol __rpc_thread_variables, version GLIBC_2.2.3
not defined in file libc.so.6 with link time reference

nfs-common 0.3.2-1
libc6  2.2.3-6

upgrading my nfs-common to
nfs-common (0.3.2-2)

has fixed this.

-Jon

Problem with woody statd? (was Re: RPC failures)

[Dave Sherohman]

Well, I've made some progress.  The major original problem was a library
version mismatch; this does not seem to be a good time to be doing anything
RPC-related on a mixed woody/potato system.

Although everything seems to be functional now, I'm still getting lots of

kernel: nsm_mon_unmon: rpc failed, status=-93
kernel: lockd: cannot monitor 192.168.23.4
kernel: lockd: failed to monitor 192.168.23.4

messages in the client's log.  Based on some googling, this likely means that
statd isn't running.  So I checked and, sure enough:

bradley:/home/dsherohman# ps ax | grep stat
11211 pts/0S  0:00 grep stat

This should be simple to fix, but...

# /etc/init.d/nfs-common start
Starting NFS common utilities: statd.
# tail -1 /var/log/syslog
Jun 19 15:39:52 foo rpc.statd[11215]: Version 0.3.2 Starting
# ps 11215
  PID TTY  STAT   TIME COMMAND
#

statd reports itself as starting, but doesn't, on both the client and the
server.

-- 
That's not gibberish...  It's Linux. - Byers, The Lone Gunmen
Geek Code 3.12:  GCS d? s+: a C++ UL$ P+ L+++ E- W--(++) N+
o+ !K w--- O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv+ b+ DI D G e* h r y+