[Pgpool-general] pgpool thinks a backend is down even though its not

[Lonni J Friedman]

Thanks for your quick reply!  I figured this out on my own about 2
minutes ago.  All good now.

On Mon, Sep 12, 2011 at 10:24 AM,  <Daniel.Crespo at l-3com.com> wrote:
> You have to use pcp_attach_node command to re-attach that node. Pgpool
> doesn't know if a database that went down is in good shape even if it is
> back online. So, after you perform the synching (it seems like you did),
> call the pcp_attach_node to bring it back to pgpool's pool of databases.
>
> -Daniel
>
>
>> -----Original Message-----
>> From: pgpool-general-bounces at pgfoundry.org [mailto:pgpool-general-
>> bounces at pgfoundry.org] On Behalf Of Lonni J Friedman
>> Sent: Monday, September 12, 2011 1:14 PM
>> To: pgpool-general at pgfoundry.org
>> Subject: [Pgpool-general] pgpool thinks a backend is down even though
>> its not
>>
>> Greetings,
>> I've got a 3 node postgresql-9.0.4 cluster (1 master, two standby, all
>> running on Linux-x86_64.  I had a hardware problem on one of the
>> standby's, and had to bring it down to swap out the bad HW.  I got it
>> synced back up with the mater successfully, and I can successfully
>> manually run SQL queries from the pgpool server to the standby.
>> However, pgpool is convinced that the standby is still down:
>> read_status_file: 1 th backend is set to down status
>>
>> I'm confused how its making this determination, or how to fix it,
>> especially since I've set:
>> health_check_period = 0
>>
>> Help?!
>> _________________________