On 12-11-29 11:53 AM, Tory M Blue wrote:
>
>
>
> On Thu, Nov 29, 2012 at 12:57 AM, Glyn Astill <glynastill at yahoo.co.uk
> <mailto:glynastill at yahoo.co.uk>> wrote:
>
>     Hi Tory
>
>      > From: Tory M Blue <tmblue at gmail.com <mailto:tmblue at gmail.com>>
>
>      >To: slony1-general <slony1-general at lists.slony.info
>     <mailto:slony1-general at lists.slony.info>>
>      >Sent: Wednesday, 28 November 2012, 18:35
>      >Subject: [Slony1-general] data copy for set 1 failed 3 times -
>     sleep 60 seconds
>      >
>      >
>      >Greetings
>      >
>      >I've just brought up a replication node across the state, we have
>     gig circuits, but still going over the net over a vpn tunnel. So
>     there is some delay,
>      >
>      >I'm getting these errors and can't get the initial replication to
>     finish
>      >
>      >4273435:2012-11-27 16:45:17 PST WARN   remoteWorkerThread_1: data
>     copy for set 1 failed 3 times - sleep 60 seconds
>      >
>
>     Is that the only line you get in your logs?  If so use a higher
>     setting for log_level (like log_level=4).
>
>     Also is there anything in the postgresql log to indicate the problem?
>
>
> I get the following
>
> 2012-11-29 08:34:38 PST CONFIG remoteWorkerThread_1: 3858.988 seconds to
> copy table "cls"."listings"
> 2012-11-29 08:34:38 PST CONFIG remoteWorkerThread_1: copy table
> "cls"."customers"
> 2012-11-29 08:34:38 PST CONFIG remoteWorkerThread_1: Begin COPY of table
> "cls"."customers"
> 2012-11-29 08:34:38 PST ERROR  remoteWorkerThread_1: "select
> "_admissioncls".copyFields(8);"
>

What is the structure of the table with table_id=8 (ie set add 
table(id=8, fully qualified name=?????)

If you do
manually run
select _admissioncls".copyFields(8);
from psql, what does it come back with?




2012-11-29 08:34:38 PST WARN   remoteWorkerThread_1: data copy for set 1
> failed 1 times - sleep 15 seconds
> 2012-11-29 08:34:39 PST DEBUG2 localListenThread: Received event
> 10,5000000195 SYNC
>
>
>
>      >The above error causes a rollback and a complete subscribe
>     node/set restart
>      >
>      >This is postgres 9.1.4 and slony 2.1.1
>      >
>      >I'm not sure if something is reaping the connection or something
>     internal to slon. Is there configuration settings I should adjust or
>     a watcher or something else daemon that I should be running?
>      >
>
>     Could be, what platform is it on?  Is there anything in syslog or
>     messages?
>
>
> CentOS6.2
> Nothing that I see in dmesg or messages.
>
>
>     Check the postgres log first, it could be something like another
>     transaction blocking it, or like you say some other reason for the
>     connection to be hoofed out like a flakey connection, ssl
>     renegotiation, oom killer etc
>
>
> I'll keep poking around, don't see anything from oom, thankfully!
>
> Tory
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>