Re: portmap timeout

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Eric Brueggmann wrote:
> 
>         I keep getting "portmap: server localhost not responding timed out."
> and "lockd_up: makesock failed, error -5" errors when ever I try to mount
> something in the "%post" section in a kickstart config script.

I just worked through this problem.  For nfs client to work in RedHat 7.1 the
portmap and nfs-utils packages (rpc.statd, lockd daemons) are needed.  I found
2 ways to cope with this:

1. Make the mount read-only.  This prevents the need for lockd.

   ex. mount -t nfs -o ro,nolock,rsize=8192,wsize=8192 ...

2. Install nfs-utils and portmap in the %packages section.

I use #1 if the only reason I want the server to use nfs is for the install. I
use #2 if the server will be an nfs client once it's setup and in use.  You
probably also want to then secure your portmap and nfs daemons using a
firewall or hosts.allow/deby files.

I think the reason for this change is actually the newer linux kernel nfs
implementation.  I've run into the same problem after upgrading the kernel on
a Red Hat 6.2 server.

-- 
Marlys A. Nelson                      Sr. Network Specialist
Information Technology Services       Network Services
University of Wisconsin - River Falls 715/425-4357
410 South Third Street                Email: Marlys.A.Nelson@xxxxxxxx
River Falls  WI  54022                http://www.uwrf.edu/





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux