From: | Jay Wren <jrwren(at)xmtp(dot)net> |
---|---|
To: | Derek Neighbors <derek(at)gnue(dot)org> |
Cc: | Jodi Kanter <jkanter(at)virginia(dot)edu>, Postgres Admin List <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: setting up ODBC |
Date: | 2001-12-04 23:07:00 |
Message-ID: | Pine.BSO.4.33.0112041803540.15034-100000@pain.xmtp.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
You can also use netstat to see if it is listening.
Postgres usually listens on port 5432 right? so examine netstat -na and
see if anything is listening on tcp port 5432.
If you are using a recent version of linux, netstat has the -p option that
will name the process listening on that port. Otherwise, use lsof to find
that.
If you find it is listening, make sure the name/password you are using
works. Try psql to verify this.
-J
On Tue, 4 Dec 2001, Derek Neighbors wrote:
> > ... I am still getting the following error when trying to connect:
> > ODBC--call failed
> > could not connect to the server
> > could not connect to remote socket #101
> >
> > any thoughts?
> Try psql -h localhost <dbname> on the server witth postgres. If that fails
> then you know you have a sockets problem and not an odbc problem.
>
> -Derek
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | A. L. Meyers | 2001-12-05 06:32:13 | Re: setting up ODBC |
Previous Message | Bruce Momjian | 2001-12-04 21:43:20 | Re: [ADMIN] compression -Fx "problem" |