Re: AWL: postgres odbc woes, continued .......

From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: applixware-list(at)applix(dot)com, Postgres Interfaces Mailing List <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: AWL: postgres odbc woes, continued .......
Date: 1999-01-15 15:44:55
Message-ID: 369F6277.D5A14AAD@insightdist.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Thomas G. Lockhart wrote:

> > This is a physical socket connection problem. The Socket Info (above)
> > shows errornumber=4, which is a failure in the connect()
> > system call. At this point in communications, protocol has not have
> > come into play yet.
> > I would suggest checking to see if the postmaster is running with -i,
> > and can connect from the machine, and all that network jazz.
>
> I copied the older version's source code to the new tree and it worked
> fine. No other changes, and I left postmaster running in between these
> tests.
>

I was looking at the logfile again, and this might explain it. Notice the
port has some junk in it. That would make the connect() call fail
alright.CC_connect(): DSN = 'Test', server = 'localhost', port = '',
database = 'test', username= 'tgl', password='no$way'

I'm not sure why the port has that stuff. It could be a bug, but check your
odbcinst.ini and odbc.ini files for anything weird.

Byron

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message jerome 1999-01-15 17:22:28 pgaccess connection failed
Previous Message Thomas G. Lockhart 1999-01-15 15:22:04 Re: AWL: postgres odbc woes, continued .......