NFS lockd and statd fail after power surge

Brian Densmore DensmoreB at ctbsonline.com
Thu Jun 13 15:48:41 CDT 2002


This is highly strange. It appears networking is not running. I wouldn't
worry about
eth0 yet. You need to get localhost working.

> -----Original Message-----
> From: "Marvin "GodfatherofSoul" Bellamy" [mailto:mbellamy at kc.rr.com]
> Sent: Thursday, June 13, 2002 10:41 AM
> To: Kclug
> Subject: Re: NFS lockd and statd fail after power surge
> 
> 
> just a guess, but is your card up or down.  I think it's 
> something like:
> 
> ifconfig eth0 up
> 
> In any case, send us a dump of ifconfig.  It's odd that your loopback 
> device isn't active.
> 
> jd0g wrote:
> 
> >I am running Redhat 7.x and have had no problems until now.  
> After two power
> >failures, two days in a row, the linux box now can't connect 
> to the network,
> >connect: Network is unreachable.  I get the following error 
> messages on
> >bootup:
> >lockd [FAILED]
> >statd [FAILED]
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >portmap: server localhost not responding, timed out
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >lockd_up: makesock failed, error=-5
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >RPC: sendmsg returned error 101
> >lockdsvc: Input/output error
> >
> >
> >and then the computer boots just fine.
> >eth0 and lo interfaces initialize without errors, but I can't ping,
> >traceroute anything, not even localhost or 127.0.0.1 and no 
> other computers
> >can ping it either.  The NIC card seems to be working ( the 
> LEDs light up ).
> >
> >Any suggestions, ideas?
> >
> >J
> >
> >
> >
> >
> majordomo at kclug.org
> >
> 
> 
> 
> 
> majordomo at kclug.org
> 




More information about the Kclug mailing list