From: Jeff Moyer Subject: Re: latest autofs from centos 4 Date: Wed, 17 Sep 2008 13:47:17 -0400 Message-ID: References: <1221621937.3001.3.camel@raven.themaw.net> <1221668372.3001.28.camel@raven.themaw.net> <1221669383.3001.35.camel@raven.themaw.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: (Joe Pruett's message of "Wed, 17 Sep 2008 10:26:10 -0700 (PDT)") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: Joe Pruett Cc: autofs@linux.kernel.org, Ian Kent Joe Pruett writes: >> Yep, gather a debug log and include the other pertinent information >> from: >> http://people.redhat.com/~jmoyer/ > > well, it's a production box and only seems to show the problem at boot > time. from looking at the logs, i think this is the underlying > culprit: > > Sep 17 09:18:08 hyperion kernel: RPC: Can't bind to reserved port (98). > Sep 17 09:18:08 hyperion kernel: RPC: can't bind to reserved port. > Sep 17 09:18:08 hyperion kernel: RPC: error 5 connecting to server jupiter.spiretech.com > Sep 17 09:18:08 hyperion kernel: RPC: Can't bind to reserved port (98). > Sep 17 09:18:08 hyperion kernel: RPC: can't bind to reserved port. > Sep 17 09:18:08 hyperion kernel: RPC: error 5 connecting to server jupiter.spiretech.com > that is from the client trying to talk to the server. That's strange. Errno 98 is EADDRINUSE. So, this means that you cycled through the entire port range and all of the ports were bound. Do you do a lot of mounts upon boot? Can you try tweaking sunrpc.min_resvport and sunrpc.max_resvport? Max can't be more than 1023. Try pushing min down to 500 or so. Cheers, Jeff