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 file in the system
> Able to login as postgres and application users from the same system (as
> long as it is not from the chroot environment). So this is not a
> show-stopper- I am able to work and application is also working fine
> Even in the chroot, as I mentioned, once I do a 'su - postgres', I am
> able to login.
So, if when you are in the chroot environment what user(s) fail to log
in and are they the same user(s) as outside the chroot?
>
> Overall, it is just a minor inconvenience, but I would like to resolve
> this. The no password supplied message comes back so fast, it is as if
> it did not even attemp to connect.
Well, per Toms suggestion you will need to look at the Postgres log file
to see from the servers perspective.
Also, in case there is third party program involved it would not hurt to
tail the system log during your connection attempts.
>
>
>
>
--
Adrian Klaver
adrian.klaver@gmail.com