> From: Steve Singer <ssinger at ca.afilias.info>
>To: Glyn Astill <glynastill at yahoo.co.uk> 
>Cc: "slony1-general at lists.slony.info" <slony1-general at lists.slony.info> 
>Sent: Tuesday, 6 August 2013, 16:47
>Subject: Re: Removing dead provider node gone wrong?
> 
>
>On 08/06/2013 11:33 AM, Glyn Astill wrote:
>
>
>> Hi Guys,
>>
>> We're running slony 2.1.3, and one of my slaves has failed. The issue is
>> that the failed slave node is a provider to another downstream slave; am
>> I right in thinking I have to drop both the failed node and the
>> downstream subscriber slave?
>>
>> My setup basically looks like this, where subscriber2 has failed:
>>
>> origin ---> subscriber1
>> ---> subscriber2 ---> subscriber3
>>
>>
>> First I tried to reshape the subscription on subscriber3, but this
>> didn't work:
>>
>> SUBSCRIBE SET ( ID=@my_set, PROVIDER = @origin, RECEIVER = @subscriber3,
>> FORWARD = YES);
>>
>> This failed with the following message:
>>
>> glyn at x:/usr/share/slonik$ slonik reshape_provider.scr
>> reshape_provider.scr:3: could not connect to server: Connection refused
>> Is the server running on host "10.16.10.101" and accepting
>> TCP/IP connections on port 5432?
>
>You need to make the resubscribe set work before doing the DROP NODE, 
>you can't drop a provider node.
>
>It isn't obvious to me why why slonik is trying to connect to node 2. 
>Which command is line 3 of that script?  What is on lines 1 and 2?  Are 
>the conninfo lines correct for nodes 1 and 3?
>

I presume it's trying to update the subscriptions on subscriber2 (which is node 4 btw), when re-subscribing subscriber3?  Line 1 is an include with the preamble (which I've sent to you off list) , line2 is a blank line.

Conninfo is as follows:

subscriber2 'dbname=mydb host=10.16.10.101 user=slony';
subscriber3 'dbname=mydb host=10.16.10.102 user=slony';
origin 'dbname=mydb host=10.10.10.92 user=slony';
subscriber1 'dbname=mydb host=10.10.10.93 user=slony';