Re: authentication problems
От | Nick Fankhauser |
---|---|
Тема | Re: authentication problems |
Дата | |
Msg-id | NEBBLAAHGLEEPCGOBHDGCEKBDLAA.nickf@ontko.com обсуждение исходный текст |
Ответ на | authentication problems (Russ McBride <Russ@psyex.com>) |
Ответы |
Re: authentication problems
|
Список | pgsql-admin |
Russ- You've got a real poser there... our system works fine with the same lines in pg_hba. I think that means you may find your answer in the operating system environment instead of the postgres setup. > local all trust > host all 127.0.0.1 255.255.255.255 trust > Also, I don't understand what's special about the above numbers > (127.0.0.1 and it's mask) such that they are used to allow any ips to > come in from the same machine. The explanation may be a clue to the problem. 127.0.0.1 is universally reserved and recognized to mean "this machine", but this is not hard-coded in the networking programs, so most systems will have lines in the IP configuration files equating localhost to 127.0.0.1. For instance, your etc/hosts file should have an entry that says: 127.0.0.1 localhost I wonder if this line, or something like it in your system's IP configuration is missing & hence postgres can't use localhost to reach the the local machine. One way to test this would be to try to ping localhost & see if it responds by telling you it is attempting to ping 127.0.0.1 If you can't ping localhost, or it doesn't resolve to 127.0.0.1, then you know the problem is at the operating system/network level & postgres and JDBC are probably just fine. -Nick --------------------------------------------------------------------- Nick Fankhauser Business: nickf@doxpop.com Phone 1.765.965.7363 Fax 1.765.962.9788 doxpop - Court records at your fingertips - http://www.doxpop.com/ Personal: nick@fankhausers.com http://www.fankhausers.com
В списке pgsql-admin по дате отправления: