Jayadevan M maymala.jayade...@gmail.com 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
On 01/06/2014 02:42 PM, Tom Lane wrote:
Jayadevan M maymala.jayade...@gmail.com 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
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 Sun, Jan 5, 2014 at 6:45 PM, Jayadevan maymala.jayade...@gmail.comwrote:
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
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
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
no file found
$ env | grep PG
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
Jayadevan M maymala.jayade...@gmail.com 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,
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
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 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], [/* 24 vars
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
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 Sat, Jan 4, 2014 at 1:29 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
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
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 is
Try psql -W for prompting the password forcefully.
On Fri, Jan 3, 2014 at 2:46 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
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
Nope -
psql -W
psql: FATAL: password authentication failed for user postgres
On Fri, Jan 3, 2014 at 2:49 PM, Ashesh Vashi
ashesh.va...@enterprisedb.comwrote:
Try psql -W for prompting the password forcefully.
On Fri, Jan 3, 2014 at 2:46 PM, Jayadevan M
maymala.jayade...@gmail.comwrote:
Hi,
On Fri, Jan 3, 2014 at 3:32 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
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
On Fri, Jan 3, 2014 at 4:16 AM, Jayadevan M maymala.jayade...@gmail.comwrote:
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
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 ch...@chriscurvey.com wrote:
On Fri, Jan 3, 2014 at 4:16 AM, Jayadevan M
On Fri, Jan 3, 2014 at 5:13 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
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
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 dineshkuma...@gmail.comwrote:
On Fri, Jan
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
Adrian Klaver adrian.kla...@gmail.com 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)
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
25 matches
Mail list logo
