My original question was...
> A server that has just suffered a power cut has started to misbehave
> - in particular I'm seeing the messages
>
> call_rpc to (local hostname) STATv1 failed: RPC: Timed out
> rpc.lockd: Cannot contact status monitor!
>
> Thinking that maybe some config files had got damaged, I restored the
> root partition from a backup made a few days previously, but this
> hasn't cured the problem. Any suggestions as to where I should be
> looking (before I restore the entire system image!)?
Thanks to all those who responded, so far:
Knut Hellebų <Knut.Hellebo_at_nho.hydro.com>
Gwen Pettigrew <gwen_at_itg.cam.ac.uk>
Olle Eriksson <olle_at_cb.uu.se>
Bevan Broun <bevanb_at_ee.uwa.edu.au>
and apologies for not mentioning in my original message that both
rpc.statd and rpc.lockd were running on the server. The solution came
from Gwen Pettigrew, who said...
====
try checking the /etc/sm.bak on the client machines. If it has the
name of your server in this directory delete the file and reboot the
client. I'd check the server too.
We had a similar problem with masses of rpc.statd and rpc.lockd
errors. Removing the files in /etc/sm.bak seemed to cure it.
There is a man page for sm.bak
====
There were a number of old entries in the server's sm.bak directory
(relating to the clients); after cleaning them out and rebooting, the
problem appears to have gone away.
Now, just a few joind and tftpd oddities to resolve...I may be back...
Thanks again
Richard
-----------------------------------
Richard Rogers
Information Technology Services
Staffordshire University
Tel: 01785 (+44 1785) 353395
E-mail: R.M.Rogers_at_staffs.ac.uk
...Sit back, relax, and soon it will just go away...
Received on Wed Aug 18 1999 - 10:49:01 NZST