From: | Stephen Carville <scarville(at)lereta(dot)com> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cannot connect to remote postgres database |
Date: | 2013-07-03 22:17:32 |
Message-ID: | 51D4A2FC.2070100@lereta.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/03/2013 01:27 PM, Andrew Sullivan wrote:
> Nothin' for nothin', but . . .
>
> On Wed, Jul 03, 2013 at 01:11:35PM -0700, Stephen Carville wrote:
>>
>> I have the software (v 8.4.13) installed on 64 bit Centos 6. It is
>
> Why for a new project would you select such an old release of the software?
Convenience. It is already there.
Anyways, I figured it out.
I used tshark to capture the traffic. When I looked at the packets I
could see that I was asking for the wrong database!
This does not work:
# psql -h scadev02.lereta.com -U stephen
This does:
# psql -h scadev02.lereta.com -U stephen postgres
I guess it's always easy once you know the answer.
>> I tried changing "md5" to "password" and "pam" without success. Onlt
>> "trust" works As near as I can tell by reading the documentation, it is
>> setup correctly but I have, obviously, done something wrong.
>>
>> Any hints on where to start looking?
>
> If this is the packaged software for the OS, you probably need to look
> at the package-specific notes about the authentication methods. But
> your experience does seem pretty strange: looking at what you did
> _appears_ like it ought to work. Are you sure you have the right
> file? Sometimes distributions put them in funky places.
>
> A
>
--
Stephen Carville
Apprentice Cook and Bottle Washer
Lereta LLC
1-800-537-3821 X1326
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Carville | 2013-07-03 22:17:36 | Re: Cannot connect to remote postgres database |
Previous Message | Joe Van Dyk | 2013-07-03 21:58:13 | Re: Analyzing last run query in psql |