lockd: fail to monitor ERRORS

lockd: fail to monitor ERRORS

Post by Jos » Mon, 06 Mar 2000 04:00:00



I'm using the NFS program and often I get an error saying

"Error: failed to monitor <IP ADDRESS>"

I get this several times....

I mounted the /var/spool/mail directory and the /home directory

Any help on how to fix this would be great, thanks in advance

 
 
 

lockd: fail to monitor ERRORS

Post by Steve Housem » Tue, 07 Mar 2000 04:00:00


It is said to be because statd or lockd are not running ...
I believe they both need to run on the server and the lockd
on the client.

However having said that I have a diskless client and I kept getting
that despite having both running, and only fix was to mount with
option nolock ....

I dont know if it is connected but some appns seem to want to use
flock and some fcntl but nfs only supports fcntl (and I'm not sure
that works either).

(my sys is rh6.1)

Cheers,

Steve Houseman

--

currently  steve.houseman at * net      

 
 
 

1. lockd: fail to monitor ERRORS

I'm using the NFS program and often I get an error saying

"Error: failed to monitor <IP ADDRESS>"

I get this several times....

I mounted the /var/spool/mail directory and the /home directory

Any help on how to fix this would be great, thanks in advance

2. ISS Security Alert Summary v1 n2

3. lockd: failed to monitor 127.0.0.1

4. cvsup trick

5. lockd: failed to monitor

6. Linux!!! Help me please!!!

7. SunOS error msg: rpc.lockd: Cannot contact status monitor!

8. ODBC exported to a FreeBSD system?

9. rpc.lockd (or lockd) on Linux ?

10. Problem with rpc.lockd [lockd] process

11. rpc.lockd failing when running on 2.4.2

12. HELP: rpc.lockd: Cannot contact status monitor!