Обсуждение: Database port changing issue

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

> But i am getting an error as mentioned below
>
> *org.postgresql.util.PSQLException: Connection refused. Check that the
> hostname and port are correct and that the postmaster is accepting
> TCP/IP connections.*
> **
> What are the changes that i have to do for changing port.
>
> If i am replacing it to *5432*, it is working fine.
>
> I had a great support and help from this mailing team and i expect the same.
>

did you reload the postgresql.conf file or stop/start the server after
changing the port?


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

That's because your listen_addresses parameter points to localhost,
and that means that your will listen for connections through unix
sockets instead of via TCP/IP.

In order to change this, you'll need to replace the string localhost
with the proper value. (A bad habit, to replace the 'localhost' with a
'*').

Read the man page :)

 # - Connection Settings -
 listen_addresses = 'localhost'  # what IP address(es) to listen on;

# Would be something like:
listen_addresses = '*'

Best wishes,
Guido







On 6/9/06, Mohamed Fazil <mohdfazil_p_a@yahoo.com> wrote:
>
> Hi to all,
>
> I am facing an issue while changing database port in the new version 8.1.
> The previous version which i used was 7.3 and for the port change i used to
> change in postgresql.conf
>
> From PG 7.3
> #---------------------------------------------------------------------------
> # CONNECTIONS AND AUTHENTICATION
> #---------------------------------------------------------------------------
> # - Connection Settings -
> #tcpip_socket = false
> #max_connections = 100
>  # note: increasing max_connections costs about 500 bytes of shared
>  # memory per connection slot, in addition to costs from shared_buffers
>         # and max_locks_per_transaction.
> #superuser_reserved_connections = 2
> port = 5432
> #unix_socket_directory = ''
> #unix_socket_group = ''
> #unix_socket_permissions = 0777 # octal
> #virtual_host = ''  # what interface to listen on; defaults to any
> #rendezvous_name = ''  # defaults to the computer name
> # - Security & Authentication -
> #authentication_timeout = 60 # 1-600, in seconds
> #ssl = false
> #password_encryption = true
> #krb_server_keyfile = ''
> #db_user_namespace = false
>
>
> Now for the port change in the newer version i tried to change the same as
> shown below in postgresql.conf.
>
> From PG 8.1
> #---------------------------------------------------------------------------
> # CONNECTIONS AND AUTHENTICATION
> #---------------------------------------------------------------------------
> # - Connection Settings -
> listen_addresses = 'localhost'  # what IP address(es) to listen on;
>      # comma-separated list of addresses;
>      # defaults to 'localhost', '*' = all
> port = 5478
> max_connections = 100
> # note: increasing max_connections costs ~400 bytes of shared memory per
> # connection slot, plus lock space (see max_locks_per_transaction).  You
> # might also need to raise shared_buffers to support more connections.
> #superuser_reserved_connections = 2
> #unix_socket_directory = ''
> #unix_socket_group = ''
> #unix_socket_permissions = 0777  # octal
> #bonjour_name = ''   # defaults to the computer name
> # - Security & Authentication -
> #authentication_timeout = 60  # 1-600, in seconds
> #ssl = off
> #password_encryption = on
> #db_user_namespace = off
> # Kerberos
> #krb_server_keyfile = ''
> #krb_srvname = 'postgres'
> #krb_server_hostname = ''  # empty string matches any keytab entry
> #krb_caseins_users = off
> # - TCP Keepalives -
> # see 'man 7 tcp' for details
> #tcp_keepalives_idle = 0  # TCP_KEEPIDLE, in seconds;
>      # 0 selects the system default
> #tcp_keepalives_interval = 0  # TCP_KEEPINTVL, in seconds;
>      # 0 selects the system default
> #tcp_keepalives_count = 0  # TCP_KEEPCNT;
>      # 0 selects the system default
>
> But i am getting an error as mentioned below
>
> org.postgresql.util.PSQLException: Connection refused.
> Check that the hostname and port are correct and that the postmaster is
> accepting TCP/IP connections.
>
> What are the changes that i have to do for changing port.
>
> If i am replacing it to 5432, it is working fine.
>
> I had a great support and help from this mailing team and i expect the same.
>
> Thanks to all in advance.
>
> Regards
>
> Mohamed Fazil
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com


--
Guido Barosio
-----------------------
http://www.globant.com
guido.barosio@globant.com

s/that your will listen /your server will listen/

eof
:x

On 6/9/06, Guido Barosio <gbarosio@gmail.com> wrote:
> That's because your listen_addresses parameter points to localhost,
> and that means that your will listen for connections through unix
> sockets instead of via TCP/IP.
>
> In order to change this, you'll need to replace the string localhost
> with the proper value. (A bad habit, to replace the 'localhost' with a
> '*').
>
> Read the man page :)
>
>  # - Connection Settings -
>  listen_addresses = 'localhost'  # what IP address(es) to listen on;
>
> # Would be something like:
> listen_addresses = '*'
>
> Best wishes,
> Guido
>
>
>
>
>
>
>
> On 6/9/06, Mohamed Fazil <mohdfazil_p_a@yahoo.com> wrote:
> >
> > Hi to all,
> >
> > I am facing an issue while changing database port in the new version 8.1.
> > The previous version which i used was 7.3 and for the port change i used to
> > change in postgresql.conf
> >
> > From PG 7.3
> > #---------------------------------------------------------------------------
> > # CONNECTIONS AND AUTHENTICATION
> > #---------------------------------------------------------------------------
> > # - Connection Settings -
> > #tcpip_socket = false
> > #max_connections = 100
> >  # note: increasing max_connections costs about 500 bytes of shared
> >  # memory per connection slot, in addition to costs from shared_buffers
> >         # and max_locks_per_transaction.
> > #superuser_reserved_connections = 2
> > port = 5432
> > #unix_socket_directory = ''
> > #unix_socket_group = ''
> > #unix_socket_permissions = 0777 # octal
> > #virtual_host = ''  # what interface to listen on; defaults to any
> > #rendezvous_name = ''  # defaults to the computer name
> > # - Security & Authentication -
> > #authentication_timeout = 60 # 1-600, in seconds
> > #ssl = false
> > #password_encryption = true
> > #krb_server_keyfile = ''
> > #db_user_namespace = false
> >
> >
> > Now for the port change in the newer version i tried to change the same as
> > shown below in postgresql.conf.
> >
> > From PG 8.1
> > #---------------------------------------------------------------------------
> > # CONNECTIONS AND AUTHENTICATION
> > #---------------------------------------------------------------------------
> > # - Connection Settings -
> > listen_addresses = 'localhost'  # what IP address(es) to listen on;
> >      # comma-separated list of addresses;
> >      # defaults to 'localhost', '*' = all
> > port = 5478
> > max_connections = 100
> > # note: increasing max_connections costs ~400 bytes of shared memory per
> > # connection slot, plus lock space (see max_locks_per_transaction).  You
> > # might also need to raise shared_buffers to support more connections.
> > #superuser_reserved_connections = 2
> > #unix_socket_directory = ''
> > #unix_socket_group = ''
> > #unix_socket_permissions = 0777  # octal
> > #bonjour_name = ''   # defaults to the computer name
> > # - Security & Authentication -
> > #authentication_timeout = 60  # 1-600, in seconds
> > #ssl = off
> > #password_encryption = on
> > #db_user_namespace = off
> > # Kerberos
> > #krb_server_keyfile = ''
> > #krb_srvname = 'postgres'
> > #krb_server_hostname = ''  # empty string matches any keytab entry
> > #krb_caseins_users = off
> > # - TCP Keepalives -
> > # see 'man 7 tcp' for details
> > #tcp_keepalives_idle = 0  # TCP_KEEPIDLE, in seconds;
> >      # 0 selects the system default
> > #tcp_keepalives_interval = 0  # TCP_KEEPINTVL, in seconds;
> >      # 0 selects the system default
> > #tcp_keepalives_count = 0  # TCP_KEEPCNT;
> >      # 0 selects the system default
> >
> > But i am getting an error as mentioned below
> >
> > org.postgresql.util.PSQLException: Connection refused.
> > Check that the hostname and port are correct and that the postmaster is
> > accepting TCP/IP connections.
> >
> > What are the changes that i have to do for changing port.
> >
> > If i am replacing it to 5432, it is working fine.
> >
> > I had a great support and help from this mailing team and i expect the same.
> >
> > Thanks to all in advance.
> >
> > Regards
> >
> > Mohamed Fazil
> >
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
>
>
> --
> Guido Barosio
> -----------------------
> http://www.globant.com
> guido.barosio@globant.com
>


--
Guido Barosio
-----------------------
http://www.globant.com
guido.barosio@globant.com

gbarosio@gmail.com ("Guido Barosio") writes:
> That's because your listen_addresses parameter points to localhost,
> and that means that your will listen for connections through unix
> sockets instead of via TCP/IP.
>
> In order to change this, you'll need to replace the string localhost
> with the proper value. (A bad habit, to replace the 'localhost' with a
> '*').
>
> Read the man page :)
>
>  # - Connection Settings -
>  listen_addresses = 'localhost'  # what IP address(es) to listen on;
>
> # Would be something like:
> listen_addresses = '*'

We found that listen_addresses='*' turned out fairly badly on AIX
5.3...

When we did so, the stats collector wouldn't start up, and there would
be complaints about trying to open port 5432 multiple times.

This appeared to relate to IPv6; evidently, PostgreSQL would try to
open up a socket on both the IPv4 and IPv6 addresses, and this somehow
conflicted.

Interestingly, 'localhost' would also fall prey to this; evidently
that can be multiply interpreted in both IPv4 and IPv6.  '

We had no difficulties when we set up a list of specific IPv4
addresses...
--
select 'cbbrowne' || '@' || 'cbbrowne.com';
http://cbbrowne.com/info/internet.html
When ever in doubt consult a song. --JT Fletcher

Hello Chris,
While yes, IF one were in a relative 'external' position - such as the
Internet - attempting to connect to this database that was internal -
assuming there was a firewall separating the two systems, one could
possibly assume there is a firewall filter, preventing this
connectivity; however, from the below email, jumping to the conclusion
that this may be a firewall issue, is a bit presumptuous.

As I think the original poster made a comment about the conflict with
opening up on port (wxyz) on BOTH IPv(4/6), this seems closer to the
truth of what is going on.  The general error message about the
server(ice) not being available, this could simply imply that the
service is not running on the port on is attempting to connect to.

After _any_ service is started up, a certain way to verify that it is at
least in a listening state ( in terms of TCP/IP layer 4 (TCP and/or
UDP)) one can issue the following commands:
Unix/Linux(aren't they the same thing? :)
    netstat -an | grep your_port_number_here
Windows
    netstat -an | find /i "your_port_number_here"

NOW, if this command returns anything, in particular what you're looking
for, and it shows that it's "LISTENING" then you KNOW there is
potentially an issue elsewhere - i.e. a firewall, OR the application is
just broken.



Chris Hoover wrote:

> sounds like you might have a firewall blocking the new port.  Make
> sure you can connect locally the the database, and then get a hole
> poked in your iptables firewall (assuming this is a linux server)
>
> HTH,
>
> Chris
>
> On 6/9/06, *Mohamed Fazil* <mohdfazil_p_a@yahoo.com
> <mailto:mohdfazil_p_a@yahoo.com>> wrote:
>
>     Hi to all,
>
>     I am facing an issue while changing database port in the new
>     version 8.1. The previous version which i used was 7.3 and for the
>     port change i used to change in postgresql.conf
>
>     _From PG 7.3_
>     #---------------------------------------------------------------------------
>     # CONNECTIONS AND AUTHENTICATION
>     #---------------------------------------------------------------------------
>
>     # - Connection Settings -
>     #tcpip_socket = false
>     #max_connections = 100
>      # note: increasing max_connections costs about 500 bytes of shared
>      # memory per connection slot, in addition to costs from
>     shared_buffers
>             # and max_locks_per_transaction.
>     #superuser_reserved_connections = 2
>     *port = 5432
>     *#unix_socket_directory = ''
>     #unix_socket_group = ''
>     #unix_socket_permissions = 0777 # octal
>     #virtual_host = ''  # what interface to listen on; defaults to any
>     #rendezvous_name = ''  # defaults to the computer name
>     # - Security & Authentication -
>     #authentication_timeout = 60 # 1-600, in seconds
>     #ssl = false
>     #password_encryption = true
>     #krb_server_keyfile = ''
>     #db_user_namespace = false
>
>
>     Now for the port change in the newer version i tried to change the
>     same as shown below in postgresql.conf.
>
>     _From PG 8.1_
>     #---------------------------------------------------------------------------
>     # CONNECTIONS AND AUTHENTICATION
>     #---------------------------------------------------------------------------
>
>     # - Connection Settings -
>     listen_addresses = 'localhost'  # what IP address(es) to listen on;
>          # comma-separated list of addresses;
>          # defaults to 'localhost', '*' = all
>     port = *5478
>     *max_connections = 100
>     # note: increasing max_connections costs ~400 bytes of shared
>     memory per
>     # connection slot, plus lock space (see
>     max_locks_per_transaction).  You
>     # might also need to raise shared_buffers to support more connections.
>     #superuser_reserved_connections = 2
>     #unix_socket_directory = ''
>     #unix_socket_group = ''
>     #unix_socket_permissions = 0777  # octal
>     #bonjour_name = ''   # defaults to the computer name
>     # - Security & Authentication -
>     #authentication_timeout = 60  # 1-600, in seconds
>     #ssl = off
>     #password_encryption = on
>     #db_user_namespace = off
>     # Kerberos
>     #krb_server_keyfile = ''
>     #krb_srvname = 'postgres'
>     #krb_server_hostname = ''  # empty string matches any keytab entry
>     #krb_caseins_users = off
>     # - TCP Keepalives -
>     # see 'man 7 tcp' for details
>     #tcp_keepalives_idle = 0  # TCP_KEEPIDLE, in seconds;
>          # 0 selects the system default
>     #tcp_keepalives_interval = 0  # TCP_KEEPINTVL, in seconds;
>          # 0 selects the system default
>     #tcp_keepalives_count = 0  # TCP_KEEPCNT;
>          # 0 selects the system default
>
>     But i am getting an error as mentioned below
>
>     *org.postgresql.util.PSQLException: Connection refused. Check that
>     the hostname and port are correct and that the postmaster is
>     accepting TCP/IP connections.*
>     **
>     What are the changes that i have to do for changing port.
>
>     If i am replacing it to *5432*, it is working fine.
>
>     I had a great support and help from this mailing team and i expect
>     the same.
>
>     Thanks to all in advance.
>
>     Regards
>
>     Mohamed Fazil
>
>
>
>
>     __________________________________________________
>     Do You Yahoo!?
>     Tired of spam? Yahoo! Mail has the best spam protection around
>     http://mail.yahoo.com
>
>

I'm sorry but this is wrong, localhost IS 127.0.0.1 and IS a fundamental
component of TCP/IP.  UNIX Domain sockets - known to most as file
descriptors - are entirely different!

localhost != UNIX Domain sockets!

I wish people would read up on this to stop perpetuating the
misunderstanding of 'localhost' and UNIX domain sockets.

 From below, and from what another has already mentioned - that seems
more plausible - is that with the listen_address = '*' and with IPv6
enabled, there is potentially a confliect there.



Guido Barosio wrote:

> That's because your listen_addresses parameter points to localhost,
> and that means that your will listen for connections through unix
> sockets instead of via TCP/IP.
>
> In order to change this, you'll need to replace the string localhost
> with the proper value. (A bad habit, to replace the 'localhost' with a
> '*').
>
> Read the man page :)
>
> # - Connection Settings -
> listen_addresses = 'localhost'  # what IP address(es) to listen on;
>
> # Would be something like:
> listen_addresses = '*'
>
> Best wishes,
> Guido
>
>
>
>
>
>
>
> On 6/9/06, Mohamed Fazil <mohdfazil_p_a@yahoo.com> wrote:
>
>>
>> Hi to all,
>>
>> I am facing an issue while changing database port in the new version
>> 8.1.
>> The previous version which i used was 7.3 and for the port change i
>> used to
>> change in postgresql.conf
>>
>> From PG 7.3
>> #---------------------------------------------------------------------------
>>
>> # CONNECTIONS AND AUTHENTICATION
>> #---------------------------------------------------------------------------
>>
>> # - Connection Settings -
>> #tcpip_socket = false
>> #max_connections = 100
>>  # note: increasing max_connections costs about 500 bytes of shared
>>  # memory per connection slot, in addition to costs from shared_buffers
>>         # and max_locks_per_transaction.
>> #superuser_reserved_connections = 2
>> port = 5432
>> #unix_socket_directory = ''
>> #unix_socket_group = ''
>> #unix_socket_permissions = 0777 # octal
>> #virtual_host = ''  # what interface to listen on; defaults to any
>> #rendezvous_name = ''  # defaults to the computer name
>> # - Security & Authentication -
>> #authentication_timeout = 60 # 1-600, in seconds
>> #ssl = false
>> #password_encryption = true
>> #krb_server_keyfile = ''
>> #db_user_namespace = false
>>
>>
>> Now for the port change in the newer version i tried to change the
>> same as
>> shown below in postgresql.conf.
>>
>> From PG 8.1
>> #---------------------------------------------------------------------------
>>
>> # CONNECTIONS AND AUTHENTICATION
>> #---------------------------------------------------------------------------
>>
>> # - Connection Settings -
>> listen_addresses = 'localhost'  # what IP address(es) to listen on;
>>      # comma-separated list of addresses;
>>      # defaults to 'localhost', '*' = all
>> port = 5478
>> max_connections = 100
>> # note: increasing max_connections costs ~400 bytes of shared memory per
>> # connection slot, plus lock space (see max_locks_per_transaction).  You
>> # might also need to raise shared_buffers to support more connections.
>> #superuser_reserved_connections = 2
>> #unix_socket_directory = ''
>> #unix_socket_group = ''
>> #unix_socket_permissions = 0777  # octal
>> #bonjour_name = ''   # defaults to the computer name
>> # - Security & Authentication -
>> #authentication_timeout = 60  # 1-600, in seconds
>> #ssl = off
>> #password_encryption = on
>> #db_user_namespace = off
>> # Kerberos
>> #krb_server_keyfile = ''
>> #krb_srvname = 'postgres'
>> #krb_server_hostname = ''  # empty string matches any keytab entry
>> #krb_caseins_users = off
>> # - TCP Keepalives -
>> # see 'man 7 tcp' for details
>> #tcp_keepalives_idle = 0  # TCP_KEEPIDLE, in seconds;
>>      # 0 selects the system default
>> #tcp_keepalives_interval = 0  # TCP_KEEPINTVL, in seconds;
>>      # 0 selects the system default
>> #tcp_keepalives_count = 0  # TCP_KEEPCNT;
>>      # 0 selects the system default
>>
>> But i am getting an error as mentioned below
>>
>> org.postgresql.util.PSQLException: Connection refused.
>> Check that the hostname and port are correct and that the postmaster is
>> accepting TCP/IP connections.
>>
>> What are the changes that i have to do for changing port.
>>
>> If i am replacing it to 5432, it is working fine.
>>
>> I had a great support and help from this mailing team and i expect
>> the same.
>>
>> Thanks to all in advance.
>>
>> Regards
>>
>> Mohamed Fazil
>>
>>
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>
>
>