On 01/06/2014 02:42 PM, Tom Lane wrote:
Jayadevan M writes:
I am able to login as postgres with password from the same machine. So it
is not an expiry issue (as you too concluded). Output from strace is about
500 lines. I am pasting what I feel may be relevant. I hope this will be
useful.
Wel
Jayadevan M writes:
> I am able to login as postgres with password from the same machine. So it
> is not an expiry issue (as you too concluded). Output from strace is about
> 500 lines. I am pasting what I feel may be relevant. I hope this will be
> useful.
Well, this is pretty interesting:
> o
I am able to login as postgres with password from the same machine. So it
is not an expiry issue (as you too concluded). Output from strace is about
500 lines. I am pasting what I feel may be relevant. I hope this will be
useful.
execve("/usr/pgsql-9.3/bin/psql", ["psql", "-h", "localhost"], [/*
On 01/05/2014 07:47 AM, Jayadevan M wrote:
With md5
psql
psql: FATAL: password authentication failed for user "postgres"
with trust
psql -h localhost
psql (9.3.2)
Type "help" for help.
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user "postgres"
But...
find
I wrote:
> Perhaps the postgres user has a password that's marked as expired
> in pg_authid.rolvaliduntil?
Ah, no, scratch that: a look at the code shows the backend doesn't
check rolvaliduntil until after the client has given a valid password.
Seems like psql *must* be getting a password from som
Jayadevan M writes:
> back to md5
> psql -h localhost
> psql: FATAL: password authentication failed for user "postgres"
> [ but there's no .pgpass file ]
Perhaps the postgres user has a password that's marked as expired
in pg_authid.rolvaliduntil? Try
select rolname, rolvaliduntil from pg_authi
On 01/05/2014 07:47 AM, Jayadevan M wrote:
With md5
psql
psql: FATAL: password authentication failed for user "postgres"
with trust
psql -h localhost
psql (9.3.2)
Type "help" for help.
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user "postgres"
Just noticed
With md5
psql
psql: FATAL: password authentication failed for user "postgres"
with trust
psql -h localhost
psql (9.3.2)
Type "help" for help.
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user "postgres"
But...
find / -name .pgpass
$ env | grep PG
PGPORT=1234
On 01/04/2014 08:46 PM, Jayadevan M wrote:
Log entries for 3 situations - 2 successful and one failed attempt -
From non-chroot, shell user postgres
2014-01-05 10:11:58 IST [17008]: [2-1] user=postgres,db=postgres LOG:
connection authorized: user=postgres database=postgres
2014-01-05 10:12:03
On Sun, Jan 5, 2014 at 6:45 PM, Jayadevan wrote:
> Sameer Kumar wrote
> > This only tells that there is one instance running!
> >
> > There could be multiple PostgreSQL installations. And I guess that is
> what
> > Tom meant here.
>
> I doubt that was what Tom meant. Anyway, we can see from the er
Sameer Kumar wrote
> This only tells that there is one instance running!
>
> There could be multiple PostgreSQL installations. And I guess that is what
> Tom meant here.
I doubt that was what Tom meant. Anyway, we can see from the error that the
request did reach the server.
Sameer Kumar wrote
On Sat, Jan 4, 2014 at 1:29 PM, Jayadevan M wrote:
> There is only one instance -
>
> ps -eaf | grep bin/postgres | grep -v grep
> postgres 3203 1 0 2013 ?00:02:04 /usr/pgsql-9.3/bin/postgres
>
This only tells that there is one instance running!
There could be multiple PostgreSQL
Log entries for 3 situations - 2 successful and one failed attempt -
>From non-chroot, shell user postgres
2014-01-05 10:11:58 IST [17008]: [2-1] user=postgres,db=postgres LOG:
connection authorized: user=postgres database=postgres
2014-01-05 10:12:03 IST [17008]: [3-1] user=postgres,db=postgres
On 01/03/2014 09:29 PM, Jayadevan M wrote:
There is only one instance -
ps -eaf | grep bin/postgres | grep -v grep
postgres 3203 1 0 2013 ?00:02:04 /usr/pgsql-9.3/bin/postgres
The basic checks I did -
Connectivity from other machines work (so server is accessible)
No .pgpass fi
There is only one instance -
ps -eaf | grep bin/postgres | grep -v grep
postgres 3203 1 0 2013 ?00:02:04 /usr/pgsql-9.3/bin/postgres
The basic checks I did -
Connectivity from other machines work (so server is accessible)
No .pgpass file in the system
Able to login as postgres and
Adrian Klaver writes:
> On 01/03/2014 04:54 AM, Jayadevan M wrote:
>> Yes. All the basic checks I have done. I upgraded from CENTOs 6.4 to
>> 6.5. Another interesting thing - if I su - postgres and then try, it
>> works. So it has something to do with the chrt user (root) settings.
> It might be
On 01/03/2014 04:54 AM, Jayadevan M wrote:
Yes. All the basic checks I have done. I upgraded from CENTOs 6.4 to
6.5. Another interesting thing - if I su - postgres and then try, it
works. So it has something to do with the chrt user (root) settings.
It might be helpful to detail what are the '
Yes. All the basic checks I have done. I upgraded from CENTOs 6.4 to 6.5.
Another interesting thing - if I su - postgres and then try, it works. So
it has something to do with the chrt user (root) settings.
On Fri, Jan 3, 2014 at 5:36 PM, dinesh kumar wrote:
>
> On Fri, Jan 3, 2014 at 5:13 PM, J
On Fri, Jan 3, 2014 at 5:13 PM, Jayadevan M wrote:
> I am able to login from the non-chroot environment. So it is not an issue
> with pg_hba.conf and not an issue of password expiration. Is there a debug
> psql option?
>
> OK.
Have you checked the PGPASSWORD environment variable, from where you a
I am able to login from the non-chroot environment. So it is not an issue
with pg_hba.conf and not an issue of password expiration. Is there a debug
psql option?
On Fri, Jan 3, 2014 at 5:09 PM, Chris Curvey wrote:
>
>
>
> On Fri, Jan 3, 2014 at 4:16 AM, Jayadevan M
> wrote:
>
>> Hi,
>> I am
On Fri, Jan 3, 2014 at 4:16 AM, Jayadevan M wrote:
> Hi,
> I am trying to login from psql and consistently getting a
> "psql: FATAL: password authentication failed for user "xyz"" for all
> users. I am not being prompted for a password at all. I faced a similar
> issue sometime ago because there
Hi,
On Fri, Jan 3, 2014 at 3:32 PM, Jayadevan M wrote:
> Nope -
> psql -W
> psql: FATAL: password authentication failed for user "postgres"
>
>
There might be possible of the user's password expiration. Make the user's
local authentication as trust, and reload the postgres instance, and check
th
Nope -
psql -W
psql: FATAL: password authentication failed for user "postgres"
On Fri, Jan 3, 2014 at 2:49 PM, Ashesh Vashi
wrote:
> Try "psql -W" for prompting the password forcefully.
>
>
> On Fri, Jan 3, 2014 at 2:46 PM, Jayadevan M
> wrote:
>
>> Hi,
>> I am trying to login from psql and c
Try "psql -W" for prompting the password forcefully.
On Fri, Jan 3, 2014 at 2:46 PM, Jayadevan M wrote:
> Hi,
> I am trying to login from psql and consistently getting a
> "psql: FATAL: password authentication failed for user "xyz"" for all
> users. I am not being prompted for a password at all
Hi,
I am trying to login from psql and consistently getting a
"psql: FATAL: password authentication failed for user "xyz"" for all
users. I am not being prompted for a password at all. I faced a similar
issue sometime ago because there was a .pgpass file and it had wrong
entries. This time there i
25 matches
Mail list logo
