[TriLUG] erroneous SM_UNMON request
dave at logicalgeek.com
Thu Mar 3 12:26:47 EST 2005
A quick google turned up this snippet:
"Basically it means that your rpc.statd daemon is unaware of a lot of
its clients. It is probably failing to save their IP-numbers to disk.
Check therefore that the directories /var/lib/nfs/sm, and
/var/lib/nfs/sm.bak (or /var/lib/nfs/statd/sm, ... on some platforms)
are writable by the rpc.statd process. "
see original URL
Hope this helps!
Blackburn, Marvin wrote:
> I updated our RHEL 3.0 AS sytem
> from 2.4.21-20 to 2.4.21-20ELsmp to 2.4.21-27.02ELsmp
> nfs-utils to 1.0.6-33EL.
> I started getting these messages intermittently afterwards:
> rpc.statd: Received erroneous SM_UNMON request from han.us.glenraven.com
> fro 172.19.8.213
> Any ideas what might be causing this?
> Marvin Blackburn
> Systems Administrator
> Glen Raven
> "He's no failure. He's not dead yet" --William Lloyd George
More information about the TriLUG