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@xxxxxxxxx
<mailto:mohdfazil_p_a@xxxxxxxxx>> 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
