× 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.



From: DrFranken
Sent: Tuesday, January 29, 2013 21:02
Subject: loopback or loopback which will connect?

Because all database access is local every connection is defined to 'localhost'.
This of course makes the code easily portable to other servers and means any changes to IP won't affect these connections.

Agreed.

Developers finally tried replacing loopback with 127.0.0.1 in the failing scripts. This worked. After fixing a few scripts, all seemed well.

You mentioned PHP and Easycom, which I snipped. When I upgraded to 7.1, I replaced Zend Core with Zend Server, and all my Easycom i5* connections failed. I replaced all my code with db2* connections instead and had to change the database to *LOCAL to match the WRKRDBDIRE RMTLOCNAME name.

A couple weeks later we took a full save and restored it to POWER7.

We decided to fall back to the POWER5 server which was still running.

Just curious: Same OS version or different?

So we simply shut down the IPV6 loopback since we weren't using IPV6 and had Never configured any of it.

Does that refer to ENDTCPIFC or some other action?

I do see that I have a host table entry for ::1 named IPV6-LOOPBACK and IPV6-LOCALHOST that is new, but I don't see any interfaces or routes with IPv6.

1) Have others ran into this seemingly random connection failure problem with loopback while IPV6 is active?

Refer to my previous question as to what you mean by "active".

2) A suggestion that if you are NOT using IPV6 turning it off to prevent that land-mine from being discovered.

A general recommendation is to turn off anything you're not using.
--
Sean Porterfield

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.