Postgres Pro
Downloads
Home   >   mailing lists

Thread: Logging attempt to connect with odbc

Logging attempt to connect with odbc

From
"Fred Parkinson"
Date:
Are there any postgresql logs that will tell me why the server is refusing my attempt to create an odbc connection to a database?
I am trying to get to one of our virtual servers with an odbc connection but am refused.
I have other connections to other databases on the same machine, and I thought I duplicated everything from a connecable database to the one I am now trying to connect to, but must have left something out.  Hopefully a database log will tell me what is defective about my attempt to connect.
 
(I browsed through responses to a search on 'server logs' but couldn't find what I need.)
 
Thanks.  Fred

Re: Logging attempt to connect with odbc

From
Craig Ringer
Date:
Please read: http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
and try again. Insufficient information.

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

Re: Logging attempt to connect with odbc

From
"Fred Parkinson"
Date:
I am using:
postgres odbc version: 7.03.02.00 (been using this successfully for about 10 years)
server version 8.1.22
running on a (virtualized) Suse Linux 10.1 instance
 
Digging into the results of a search on 'log files' I figured out where they are and how to configure server log output (mostly), but cannot interpret the results
 
(new) postgresql.conf settings:
log_error_verbosity = verbose
log_connections = on
log_line_prefix = '%t %d %u %r'
log_min_error_statement = info
log_min_duration_statement = 0
 
Log results of trying to establish an odbc connection from a windos machine:
2011-06-08 07:49:01 PDT [unknown] [unknown] LOG:  00000: connection received: host=172.16.2.42 port=3534  (172.16.2.42 is my windows intranet ip address)
2011-06-08 07:49:01 PDT [unknown] [unknown] LOCATION:  BackendRun, postmaster.c:2712
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: connection authorized: user=postgres database=timecard_development
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  BackendRun, postmaster.c:2782
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 0.162 ms  statement:  
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 0.689 ms  statement: select version()
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 0.139 ms  statement: set DateStyle to 'ISO'
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 0.028 ms  statement: set geqo to 'OFF'
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 0.058 ms  statement: set extra_float_digits to 2
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 1.584 ms  statement: select oid from pg_type where typname='lo'
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOG:  00000: duration: 0.130 ms  statement: select pg_client_encoding()
2011-06-08 07:49:01 PDT timecard_development postgres 172.16.2.42(3534)LOCATION:  exec_simple_query, postgres.c:1105
 
 that's it. that's all I get before Windows reports that "a connection could not be made (with) ... the connection parameters..."
Perhaps there is another configuration parameter I can set to get more information, or set the ones described above to something else?
Or perhaps the information I need is here but I can't interpret it?

 All help is greatly appreciated.

Fred
 
 

>>> Craig Ringer <craig@postnewspapers.com.au> 06/07/2011 9:57 PM >>>
Please read: http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
and try again. Insufficient information.

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: Logging attempt to connect with odbc

From
Craig Ringer
Date:
On 09/06/11 01:04, Fred Parkinson wrote:

>  that's it. that's all I get before Windows reports that "a connection
> could not be made (with) ... the connection parameters..."

There are no errors in the server-side logs, so I'd be looking at the
client-side ODBC logging.

Turn on ODBC client logging and look at the "mylog" file to see if
there's anything informative. You can enable driver-level logging in the
DSN options using the "MyLog" option; this is **NOT** the same as "ODBC
Logging" which will not tell you what you need to know.

See:

http://psqlodbc.projects.postgresql.org/config.html

http://psqlodbc.projects.postgresql.org/

--
Craig Ringer