[ psqlodbc-Bugs-1000600 ] odbc via the local net (lan & Wan)

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1000600 ] odbc via the local net (lan & Wan)
Date: 2010-05-05 12:20:32
Message-ID: 20100505122032.CC3CC107171F@pgfoundry.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Bugs item #1000600, was opened at 2006-03-27 20:44
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000600&group_id=1000125

Category: Interface (example)
Group: v1.0 (example)
Status: Closed
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: odbc via the local net (lan & Wan)

Initial Comment:
When you have installed the odbc driver local where the db also is installed, it does work.

When you have istalled the odbc driver local on a client machine, the connection failed - it is always looking for the pg_hba.conf file.
-

log:
LIBPQ returned -> FATAL: missing or erroneous pg_hba.conf file
HINT: See server log for details.

[1452]CONN ERROR: func=PGAPI_DriverConnect, desc='Error from CC_Connect', errnum=113, sqlstate=08001, errmsg='FATAL: missing or erroneous pg_hba.conf file
HINT: See server log for details.
'
[1452][SQLGetDiagRecW]

----------------------------------------------------------------------

Comment By: Sorin Cristescu (scr53005)
Date: 2010-05-05 14:20

Message:
OK, you are right, I've enabled verbose logging on the postgres server and when attempting to connect from psqlODBC I got the answer. For further reference : the standard, default pg_hba.conf contains an IPv6 example on the second line, "host - all - all - ::1/128 - md5". This line was "enabled" on my server and came second (the first line was "host - all - all - 127.0.0.1/32 - md5" and was verified when connecting locally). This line caused a fatal server error "invalid IP address ::1". Once disabled, connecting from the LAN works fine

----------------------------------------------------------------------

Comment By: Dave Page (dpage)
Date: 2010-05-05 12:58

Message:
Yes, the error does come from the server. psqlODBC doesn't have any way to read the pg_hba.conf file - that is *always* done by the server, which will return the error shown if it cannot parse the file.

If you believe I am incorrect, please feel free to check the source code and see for yourself.

----------------------------------------------------------------------

Comment By: Sorin Cristescu (scr53005)
Date: 2010-05-05 12:26

Message:
Hi,

I have the same problem. The pg_hba.conf is NOT missing and does NOT contain an error : the server works fine AND psqlODBC works fine AS LONG AS I set the "Server" as 127.0.0.1 when defining a psqlODBC-based DSN. BUT ... when I replace 127.0.0.1 with 10.128.54.77 (IP address of the Postgres server ...) I get a "missing or erroneous pg_hba.conf". The error is NOT reported by the server, it only appears when defining a DSN in odbcad32.exe

----------------------------------------------------------------------

Comment By: Dave Page (dpage)
Date: 2006-04-28 10:24

Message:
This error is being reported by the server because your pg_hba.conf file is missing or contains an error. This is not a psqlodbc problem.

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000600&group_id=1000125

Browse pgsql-odbc by date

  From Date Subject
Next Message Al 2010-05-05 15:16:11 Need help with ODBC/TNS name
Previous Message noreply 2010-05-05 10:58:51 [ psqlodbc-Bugs-1000600 ] odbc via the local net (lan & Wan)