Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA32555 for ; Wed, 1 Mar 2000 22:46:48 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id WAA07336; Wed, 1 Mar 2000 22:46:29 -0500 (EST) To: "Don Oliver" cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Pgaccess - Error trying to connect In-reply-to: <20000302002021.29212.qmail@hotmail.com> References: <20000302002021.29212.qmail@hotmail.com> Comments: In-reply-to "Don Oliver" message dated "Wed, 01 Mar 2000 16:20:21 -0800" Date: Wed, 01 Mar 2000 22:46:29 -0500 Message-ID: <7333.951968789@sss.pgh.pa.us> From: Tom Lane "Don Oliver" writes: > PostgreSQL is always on, and works fine from the command line. (A console in > X.) If you mean that "psql" works, that's good, but by default psql tries to connect via a Unix socket file, not via TCP/IP. So TCP connection problems won't necessarily show up. If you use the -h option then psql tries to use a TCP connection, which is what pgaccess always tries. I'll bet if you do "psql -h localhost" you see the same failure as in pgaccess. > If I try to start pgaccess with: "pgaccess don", the main PgAccess window > comes up, > (empty) but there is an error message box in front of it. The message is: > "Error trying to connect to database "don" on host localhost. > PostgreSQL error message: Connection to database failed: > Network is unreachable. is the postmaster running (with -i) at > 'localhost' and accepting connections on TCP/IP port '5432'?" The critical part of that message is the "Network is unreachable" part, which is the kernel error message that pgaccess is getting when it tries to connect. That's a pretty darn bizarre error code to get for an attempt to contact 'localhost'. I think there's something screwy in the networking configuration of your machine. Dunno what exactly; but it likely doesn't have anything directly to do with Postgres. If you do, say, "telnet localhost 23", do you get a telnet login prompt or an error? regards, tom lane