Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of jwcarman@gmail.com designates
 64.233.162.201 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=TB5C+fxGcWC0xunlDQ/FYE58Qoev9iJRozlCqOvpkgtJNbLwfqDif2A34cR/dcdiSo0fqohSWQ4NuohIvGyyezK2+otUqwRPsjrUGNmLqMBwUgzBboc8MZ2Qyj0+Xeu4mXjtUX8yRtnDt7/dR9chFhTC17SrnLJJI3LD6LyHcCc=
Message-ID: <eb4296c40611210457t2bbdf9fbqa7f6e21cb73d8ad0@mail.gmail.com>
Date: Tue, 21 Nov 2006 07:57:06 -0500
From: "James Carman" <james@carmanconsulting.com>
Sender: jwcarman@gmail.com
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [nightly build] codec net proxy failed.
In-Reply-To: <8a81b4af0611190831j1ff99f62w597197cb9679aa99@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20061113120102.64395.qmail@minotaur.apache.org>
	 <31cc37360611150231n1720b4f8j78a2e22d4463c206@mail.gmail.com>
	 <31cc37360611150259y3a6784b9r4333c45152e9a5a5@mail.gmail.com>
	 <eb4296c40611150516v5141beadhdd706973940efc5@mail.gmail.com>
	 <8a81b4af0611181129h5f8a6d56rabbc502998952b35@mail.gmail.com>
	 <ejnv0m$sqg$1@sea.gmane.org> <ejo1u8$4cm$1@sea.gmane.org>
	 <8a81b4af0611181523h49692354ua22be89eabed1265@mail.gmail.com>
	 <ejo5mm$d8k$1@sea.gmane.org>
	 <8a81b4af0611190831j1ff99f62w597197cb9679aa99@mail.gmail.com>

Great!  Glad to hear we figured that out.

On 11/19/06, Phil Steitz <phil.steitz@gmail.com> wrote:
> On 11/18/06, Bill Barker <wbarker@wilshire.com> wrote:
> >
> > "Phil Steitz" <phil.steitz@gmail.com> wrote in message
> > news:8a81b4af0611181523h49692354ua22be89eabed1265@mail.gmail.com...
> > > On 11/18/06, Bill Barker <wbarker@wilshire.com> wrote:
> > >> I found the problem with Gump, and I'm betting that it is the same
> > >> problem
> > >> with [nightly build].  The /etc/hosts file on vmgump still had the old IP
> > >> address for vmgump.  I changed it to the new address, and now
> > >> INA.getLocalHost() returns the right address.
> > >>
> > > Thanks, Bill.  I see this in /etc/hosts on vmbuild:
> > > 209.237.227.200 vmbuild
> > >
> > > I get a different IP when I ping or do nslookup.  I guess I should
> > > change it to what DNS gives?  Why is this entry there, anyway?
> > >
> > Yes, if you change it to the DNS address, then c-n will quit trying to
> > connect to a machine that no longer exists, and connect to vmbuild instead
> > :).
> >
> > It's there so that the machine can locate itself during bootup (before the
> > bind daemon starts), or at least that's the traditional reason to have it.
>
> Thanks, Bill!
>
> Looks like Hen fixed this last night and both [net] and [proxy] (and
> everything else) ran clean last night.
>
> Phil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org