On 12/07/2015 11:32 AM, Josh Berkus wrote:
> On 12/07/2015 10:56 AM, Josh Berkus wrote:
>> So, the prepare clone method above worked perfectly twice.  But then we
>> tried to bring up a new node as a prepared clone from node 11 and things
>> went to hell.
> 
> One thing I just realized was different between the first two,
> successful, runs and the failed runs:  the first two times, we didn't
> have pg_hba.conf configured, so when we brought up slony on the new node
> it couldn't connect until we fixed that.
> 
> So I'm wondering if there's a timing issue here somewhere.

So, this problem was less interesting than I thought.  As it turns out,
the sysadmin was handling "make sure slony doesn't start on the server"
by letting it autostart, then shutting it down.  In the couple minutes
it was running, though, it did enough to prevent finish clone from working.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com