I can´t connect to my postgresql8.1 server running on Debian. The pgadmin
client says it can't connect. I already edited the pg_hba.conf and
postgresql.conf (listen_addresses = '*' and port) but the problem remains,
pg_admin is running on a XP machine without Firewalls enabled, Debian is
also not running any kind of firewall. I should also note the I just
upgraded to 8.1, some minutes ago I was running 7.4 and connections **were
working fine**.

pg_hba.conf:

http://www.pastebin.ca/980122

postgresql.conf (connection settings section):

http://www.pastebin.ca/980147

PostgreSQL 8.1 Debain Etch package.

Any hints greatly appreciated!

Marcelo.

On Thu, Apr 10, 2008 at 1:26 PM, Marcelo de Moraes Serpa <
celoserpa@gmail.com> wrote:

> I can´t connect to my postgresql8.1 server running on Debian. The pgadmin
> client says it can't connect. I already edited the pg_hba.conf and
> postgresql.conf (listen_addresses = '*' and port) but the problem remains,
> pg_admin is running on a XP machine without Firewalls enabled, Debian is
> also not running any kind of firewall. I should also note the I just
> upgraded to 8.1, some minutes ago I was running 7.4 and connections **were
> working fine**.
>
> pg_hba.conf:
>
> http://www.pastebin.ca/980122
>
> postgresql.conf (connection settings section):
>
> http://www.pastebin.ca/980147
>
> PostgreSQL 8.1 Debain Etch package.
>
> Any hints greatly appreciated!



Your postgresql.conf has port set to 5433 (PostgreSQL default port is 5432)..


Did you change the port in pgadmin to connect to 5433?

Joey

Did you purposely change the default port? Are you specifying the
change in pgadmin? If the pg_hba.conf file is the problem, pgadmin will
tell you with a message like:

FATAL: no pg_hba.conf entry for host "IPADDRESS", user "USER", database
"DATABASE", SSL ON/OFF

Are you getting a similar message or is the connection timing out?

Marcelo de Moraes Serpa wrote:
> I can´t connect to my postgresql8.1 server running on Debian. The pgadmin
> client says it can't connect. I already edited the pg_hba.conf and
> postgresql.conf (listen_addresses = '*' and port) but the problem remains,
> pg_admin is running on a XP machine without Firewalls enabled, Debian is
> also not running any kind of firewall. I should also note the I just
> upgraded to 8.1, some minutes ago I was running 7.4 and connections **were
> working fine**.
>
> pg_hba.conf:
>
> http://www.pastebin.ca/980122
>
> postgresql.conf (connection settings section):
>
> http://www.pastebin.ca/980147
>
> PostgreSQL 8.1 Debain Etch package.
>
> Any hints greatly appreciated!
>
> Marcelo.
>

--

Kyle Wilcox
NOAA Chesapeake Bay Office
410 Severn Avenue
Suite 107A
Annapolis, MD 21403
office: (410) 295-3151
Kyle.Wilcox@noaa.gov

A: It takes over twice as long to understand the conversation.
Q: What's wrong with top-posting?
A: Top-posting.
Q: What's the worst thing about plain text email discussions?

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Thank you for the replies,

Actually I did not change the port number. For some bizarre reason, the
pgsql 8.1 debian package comes with port 5433 pre-configured and this was
exactly was causing the problem, of course, I wasn't noting that the port
was different, but they are so similar (that's what happens when you have a
stressful day of work..). I changed it to 5432 and everything went fine.

Do you see how little changes can make a **big** difference. I wonder what
was going through the head of the person who altered the port number for
this release...

Thanks,

Marcelo.

On Thu, Apr 10, 2008 at 5:50 PM, Kyle Wilcox <Kyle.Wilcox@noaa.gov> wrote:

> Did you purposely change the default port? Are you specifying the change
> in pgadmin? If the pg_hba.conf file is the problem, pgadmin will tell you
> with a message like:
>
> FATAL: no pg_hba.conf entry for host "IPADDRESS", user "USER", database
> "DATABASE", SSL ON/OFF
>
> Are you getting a similar message or is the connection timing out?
>
>
> Marcelo de Moraes Serpa wrote:
>
> > I can´t connect to my postgresql8.1 server running on Debian. The
> > pgadmin
> > client says it can't connect. I already edited the pg_hba.conf and
> > postgresql.conf (listen_addresses = '*' and port) but the problem
> > remains,
> > pg_admin is running on a XP machine without Firewalls enabled, Debian is
> > also not running any kind of firewall. I should also note the I just
> > upgraded to 8.1, some minutes ago I was running 7.4 and connections
> > **were
> > working fine**.
> >
> > pg_hba.conf:
> >
> > http://www.pastebin.ca/980122
> >
> > postgresql.conf (connection settings section):
> >
> > http://www.pastebin.ca/980147
> >
> > PostgreSQL 8.1 Debain Etch package.
> >
> > Any hints greatly appreciated!
> >
> > Marcelo.
> >
> >
> --
>
> Kyle Wilcox
> NOAA Chesapeake Bay Office
> 410 Severn Avenue
> Suite 107A
> Annapolis, MD 21403
> office: (410) 295-3151
> Kyle.Wilcox@noaa.gov
>
> A: It takes over twice as long to understand the conversation.
> Q: What's wrong with top-posting?
> A: Top-posting.
> Q: What's the worst thing about plain text email discussions?
>

On Thu, Apr 10, 2008 at 06:00:30PM -0300, Marcelo de Moraes Serpa wrote:
> Thank you for the replies,
>
> Actually I did not change the port number. For some bizarre reason, the
> pgsql 8.1 debian package comes with port 5433 pre-configured and this was
> exactly was causing the problem, of course, I wasn't noting that the port
> was different, but they are so similar (that's what happens when you havea
> stressful day of work..). I changed it to 5432 and everything went fine.

Debian allows parallel installs. In all likelyhood you had 7.4 still
installed using port 5432 and then you installed 8.1 which got assigned
the next available port. It would have mentioned this during
installation and also pg_lsclusters would have told you this.

Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH/oOdIB7bNG8LQkwRAqB+AJ0RftElOyDE16GyGA1+MhUdquhZ+AC fWJWP
TarVp0nelHyQZ+McLpQ9Rg4=
=cP0I
-----END PGP SIGNATURE-----

On Thu, Apr 10, 2008 at 3:00 PM, Marcelo de Moraes Serpa
<celoserpa@gmail.com> wrote:
> Thank you for the replies,
>
> Actually I did not change the port number. For some bizarre reason, the
> pgsql 8.1 debian package comes with port 5433 pre-configured and this was
> exactly was causing the problem, of course, I wasn't noting that the port
> was different, but they are so similar (that's what happens when you have a
> stressful day of work..). I changed it to 5432 and everything went fine.
>
> Do you see how little changes can make a **big** difference. I wonder what
> was going through the head of the person who altered the port number for
> this release...

Actually, what debian and ubuntu do is allow you to have > 1 version
of pgsql installed at a time, and each version gets the next available
port. So, it's likely your machine once had another version like 8.0
on it, and then had 8.1 added.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general