Message-ID: <51098E49.9020701@pro-open.de>
Date: Wed, 30 Jan 2013 22:19:05 +0100
From: "Gunnar \"Nick\" Bluth" <gunnar.bluth@pro-open.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: =?UTF-8?B?U3RyYWhpbmphIEt1c3R1ZGnEhw==?= <strahinjak@nordeus.com>
CC: "Rajagopalan, Jayashree" <Jayashree.Rajagopalan@emc.com>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: postgres 9.0 - unable to bind to localhost.
References: <672B315321EBEC4CA4B5627D112E0896067F53F7D4@MX25A.corp.emc.com>
	<672B315321EBEC4CA4B5627D112E0896067F53F7E4@MX25A.corp.emc.com>
	<CADKbJJVYJ7=fZ2h87b3SqVmPXCOCcASrrO483dW1ubhyqAEG4w@mail.gmail.com>
In-Reply-To: 
 <CADKbJJVYJ7=fZ2h87b3SqVmPXCOCcASrrO483dW1ubhyqAEG4w@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------060305050105020804080906"
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multi-part message in MIME format.
--------------060305050105020804080906
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Am 23.12.2012 12:38, schrieb Strahinja Kustudi=C4=87:
> Sorry for a late reply, but I had the exact same problem and it was a=20
> bug in the Red Hat RPM package upgrade script of the sudo package.=20
> This basically means the user running Postgres cannot resolve hostname=20
> localhost. Have you tried logging in as the user running Postgres and=20
> trying to resolve localhost? In RHEL/Centos you would do this with:
>
> *su - postgres*
> *nslookup localhost*
>

A late comment on this one... but I've learnt this lesson the hard way :/
If you want to know what am actual program will get, use "getent hosts=20
<hostname/IP>", that will follow the directions in nsswitch.conf and=20
also use an nscd, if you're running one.

So, if someone (for whatever reason) once put a line
     1.2.3.4 localhost
in your /etc/hosts, the "nslookup" will return what you'd expect (i.e.,=20
hopefully ;-), but Postgres will try to open a socket on 1.2.3.4. Bang!

Apart from that:
a) nslookup is deprecated since ages, use "host" or "dig" (well, no, use=20
"getent hosts" ;-)
b) I doubt that all DNS possible servers (M$ ones spring to mind...)=20
will provide answers to "localhost"

Just my 2p...

--=20
Gunnar "Nick" Bluth
RHCE/SCLA

Mobil   +49 172 8853339
Email: gunnar.bluth@pro-open.de
_________________________________________________________________________=
_
In 1984 mainstream users were choosing VMS over UNIX.  Ten years later
they are choosing Windows over UNIX.  What part of that message aren't yo=
u
getting? - Tom Payne


--------------060305050105020804080906
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Am 23.12.2012 12:38, schrieb Strahinja
      Kustudi=C4=87:<br>
    </div>
    <blockquote
cite=3D"mid:CADKbJJVYJ7=3DfZ2h87b3SqVmPXCOCcASrrO483dW1ubhyqAEG4w@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">Sorry for a late reply, but I had the exact same
        problem and it was a bug in the Red Hat RPM package upgrade
        script of the sudo package. This basically means the user
        running Postgres cannot resolve hostname localhost. Have you
        tried logging in as the user running Postgres and trying to
        resolve localhost? In RHEL/Centos you would do this with:
        <div>
          <br>
        </div>
        <div style=3D""><font face=3D"courier new, monospace"><b>su -
              postgres</b></font></div>
        <div style=3D""><font face=3D"courier new, monospace"><b>nslookup
              localhost</b></font></div>
        <div style=3D""><font face=3D"courier new, monospace"><br>
          </font></div>
      </div>
    </blockquote>
    <br>
    A late comment on this one... but I've learnt this lesson the hard
    way :/<br>
    If you want to know what am actual program will get, use "getent
    hosts &lt;hostname/IP&gt;", that will follow the directions in
    nsswitch.conf and also use an nscd, if you're running one. <br>
    <br>
    So, if someone (for whatever reason) once put a line <br>
    =C2=A0=C2=A0=C2=A0 1.2.3.4 localhost<br>
    in your /etc/hosts, the "nslookup" will return what you'd expect
    (i.e., hopefully ;-), but Postgres will try to open a socket on
    1.2.3.4. Bang!<br>
    <br>
    Apart from that:<br>
    a) nslookup is deprecated since ages, use "host" or "dig" (well, no,
    use "getent hosts" ;-)<br>
    b) I doubt that all DNS possible servers (M$ ones spring to mind...)
    will provide answers to "localhost"<br>
    <br>
    Just my 2p...<br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Gunnar "Nick" Bluth
RHCE/SCLA

Mobil   +49 172 8853339
Email: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:gunnar.bluth@=
pro-open.de">gunnar.bluth@pro-open.de</a>
_________________________________________________________________________=
_
In 1984 mainstream users were choosing VMS over UNIX.  Ten years later
they are choosing Windows over UNIX.  What part of that message aren't yo=
u
getting? - Tom Payne</pre>
  </body>
</html>

--------------060305050105020804080906--