Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

This site requires JavaScript to be enabled to function correctly, please enable it.

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050523 CentOS/1.0.4-1.4.1.centos4 Firefox/1.0.4
Description of problem:
After an update we started seeing a lot of these messages in /var/log/messages
rpc.statd[1906]: Received erroneous SM_UNMON request from eth0.domain.com
We didn't have any of those messages before the update.
It's not clear to me if those indicate a problem or not.
The machine where these messages show up has 2 network interfaces. The name in the logs is from eth0 interface and the nfs servers it's connecting to is through eth1.
Version-Release number of selected component (if applicable):
nfs-utils-1.0.6-33EL.src.rpm
How reproducible:
Didn't try
Additional info:
kernel-smp-2.4.21-32.0.1.EL

we have been seeing these for a while. (since before January of this year
and whatever the current RHEL3 releast kernel was at that time and, i'm
sorry to say, for some indefinite time prior.) our messages look more like
rpc.statd[4450]: Received erroneous SM_UNMON request from
`uname -n` for 172.31.206.72
where 172.31.206.72 is the host that the NFS is ``import''-ed from, from
what i've been able to discern from the logs. this may have something to
do with amd, in our case. what seems to be happening in at least one in-
stance is that amd unmounts a fileystem from 172.31.206.72 and then 30
seconds later it logs that it's successfully remounted the filesystem,
immediately after which the rpc.statd message shows up in the logs, so i
don't know if maybe there's some confusion b/w amd and the kernel nfs/
lockd about what's mounted and what's not maybe, but amd is unequivocal
about thinking that it has successfully re-mounted the filesystem (on the
same mount point), so i wouldn't expect so
sorry if i'm hijacking the thread by bringing up amd. if it's a separate
pathology, please, whoever responds to this, let me know to open another
bugzilla