× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Pinging 127.0.0.1 worked for us and all processes that
used 127.0.0.1 worked - it was just pinging loopback and
all process that used loopback that failed.

They failed because the default host name search priority (in chgtcpdmn)
changed from *local to *remote in v7r1 and there was a device on the
network named the same thing as our domain name. We never noticed
in v5r4 because v5r4 always searched locally for "loopback" first.

We put an explicit full name for loopback (loopback.company.local) and
that worked. Later we found out changing the host name search priority
would have worked as well.

One of the things that made it hard to debug was it would sometimes
connect loopback to 127.0.0.1 in the cache and then everything would
would until the next ipl when the cache was flushed and troubles started
again.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Monday, January 28, 2013 12:43 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: localhost weirdness


On Mon, 28 Jan 2013, at 18:33:21, Lance Gillespie <LGillespie@xxxxxxxx> wrote:

date: Mon, 28 Jan 2013 18:33:21 +0000
from: Lance Gillespie <LGillespie@xxxxxxxx>
subject: RE: localhost weirdness

We had a weird one that took a week to figure out.

Our domain setup was iseries.company.local and we had host entries for
loopback and localhost at 124.0.0.1.

At some point, a vendor installed a router in you HVAC system and
named it company.local

After that, iseries stuff directed to 127.0.0.1 worked fine, but stuff
directed to localhost or loopback did not. The clue was that pinging localhost resolved to a strange address.

We added a host entry for loopback.company.local (not just loopback)
pointing to 127.0.0.1 and everything was fine.

Probably not your issue, but the symptoms sound similar.


Now that would have been a lovely one - but sadly when I ping localhost I get 127.0.0.1 - thanks though for the suggestion.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.