Search Postgresql Archives

Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yes I'm running on amazon.aws and yes I requested my admin to open the port, do you know how I can check its status

iptables -L -vn
Chain INPUT (policy ACCEPT 44554 packets, 6381K bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:5436

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 43998 packets, 6200K bytes)
 pkts bytes target     prot opt in     out     source               destination


-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@xxxxxxxxx] 
Sent: Tuesday, December 27, 2011 2:42 PM
To: Jacques Lamothe
Cc: rod@xxxxxx; pgsql-general@xxxxxxxxxxxxxx
Subject: Re:  UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

On 12/27/2011 11:39 AM, Jacques Lamothe wrote:
> Yes I did

More guesses.
Looks like you may be running on Amazon AWS?
If so, did you change the AWS firewall to allow port 5436?

>
>


-- 
Adrian Klaver
adrian.klaver@xxxxxxxxx

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



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux