Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 May 1996 23:20:15 +0100 (GMT-1)
From:      af@biomath.jussieu.fr
To:        rolands@nucleus.com
Cc:        questions@freebsd.org
Subject:   Re: NFS Problem
Message-ID:  <199605272220.XAA04006@garfield.biomath.jussieu.fr>
In-Reply-To: <31A9FFCC.15E2@quattttro.com> from "Roland Schoettle" at May 27, 96 01:17:32 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> I am having a problem with a new FreeBSD install. Specifically NFS does 
> not seem to work.
> 
> When connecting to another UNIX host, all appears well - the mount works
> running "ls -l" across the mount shows the files on the mounted system. 
> But when trying to "cp" a file across the NFS mount the tty doing the 
> "cp" appears to hang (other ttys are OK). After a few minutes the tty 
> comes back with the following message:
>   monty sendmail[8031]: timeout waiting for input from local
>     during message body read
>   monty sendmail[8078]: timeout waiting for input from local
>     during message body read
>   monty sendmail[8078]: CAA08078: SYSERR: putoutmsg (NO-HOST): error
>     on output channel sending "451 timeout waiting for input during 
>     message body read": Broken pipe
>   monty sendmail[8078]: CAA08078: SYSERR: putoutmsg (NO-HOST): error
>     on output channel sending "451 timeout waiting for input during 
>     message body read": Broken pipe
>   monty sendmail[8177]: timeout waiting for input from local during 
>     initial message read
> 

It looks much like an NFS file locking problem to  me.  Would  you  by
chance mount /var/mail (/var/spool/mail or whatever it  is  called  on
the system you are copying from) through NFS from the same machine you
are copying to ?

My feeling is that the cp requests a file lock which hangs the  remote
rpc.lockd  which  in  turn  causes any incoming request to sendmail to
freeze.  I  sometimes  observe very similar behaviour when the locking
daemon  on  my  Solaris  2.x  server  gets confused. I usually have to
reboot, deleting the contents of /var/statmon/sm[.bak] (path varies on
other flavours of Unix, see man statd). As for what your exact problem
is,  I  don't  know.  I just suggest that you take a close look at NFS
locking on either systems (do the statd and lockd daemons run ?).

Good luck,
_Alain_
-- 
Alain FAUCONNET    Ingenieur systeme - System Manager     AP-HP/SIM
Public Health                91 bld de l'Hopital 75013 PARIS FRANCE
Medical Computing Research Labs         Mail: af@biomath.jussieu.fr
Tel: (+33) 1-40-77-96-19                   Fax: (+33) 1-45-86-80-68
    I've RTFMed. It says: "Refer to your system administrator"
            But... I *am* the system administrator :-]



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605272220.XAA04006>