-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
what does that mean?
<snip>
Dec 21 11:49:28 freedom rpc.statd[104]: Received erroneous SM_UNMON
request from freedom for 192.168.88.100
Dec 21 11:49:28 kryton rpc.statd[13057]: Received erroneous SM_UNMON
request from kryton for 195.58.191.166
<snip>
best regards
Michael Kummer
- ---
Web: http://www.packetst0rm.net / http://www.sprinter-sbg.at
Email: [email protected]
UIN: 96628703
IRC: irc.packetst0rm.net #taskforce
Addr: Lieferinger-Hauptstrasse 47 / A - 5020 Salzburg
Mobil: +43 664 3333995
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQE8IxR/TOeKpVx8ESMRAqDGAJ42IbLuvOa3EUQO8CiRiK1v1aJwlQCglce7
OTPbwW33g1sG+pUkXXE5MQA=
=Xj7x
-----END PGP SIGNATURE-----
>>>>> " " == Michael Kummer <[email protected]> writes:
> what does that mean? <snip> Dec 21 11:49:28 freedom
> rpc.statd[104]: Received erroneous SM_UNMON request from
> freedom for 192.168.88.100 Dec 21 11:49:28 kryton
> rpc.statd[13057]: Received erroneous SM_UNMON request from
> kryton for 195.58.191.166 <snip>
The above question is pretty much off-topic for Linux Kernel...
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.
Cheers,
Trond