commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz" <phil.ste...@gmail.com>
Subject Re: [nightly build] codec net proxy failed.
Date Sun, 19 Nov 2006 16:31:03 GMT
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


Mime
View raw message