From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Strange message from pg_receivexlog |
Date: | 2013-08-21 02:10:31 |
Message-ID: | CAL_0b1tzvjLSjmX0qVX7ThtwUkVE7v+41bUw3U6GHqx6efZuQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 20, 2013 at 2:10 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> It looks like something outside postgres or pg_receivexlog did
> terminate the connection. pg_receievexlog noticed it was closed,
> whereas postgres waited for the timeout (but probably would've noticed
> if it had actually had some other data to send maybe?). Do you have
> some iptables connection tracking or something like that which could
> be interfering?
AFAIU, just standard things:
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
Nothing looks suspicious for me.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | S H | 2013-08-21 03:01:24 | Commit hung bug |
Previous Message | Tom Lane | 2013-08-20 23:58:21 | Re: pg_extension_config_dump() with a sequence |