[Bucardo-general] Bucardo Crash

[Balman, Matthew D. (GSFC-428.0)[Embedded Flight Systems, Inc]]

No. The excluded tables shouldn¹t have caused this issue as far as I can
tell.
This may have been a follow on from a previous issue.
We had a sync that went to ³stalled² and the only way to get it back was
to deactivate it and reactivate it.
That was about a week before this issue.

I understand there are some pending fixes in development.
I would be interested in the next release.

As it stands now we will probably have to implement a cron job that
monitors the status of bucardo and
1) Restart it if it crashes
2) Reactivate stalled syncs

Using Postgresql 9.3.10
There have been some postgres fixes that sound like they would affect
pgperl code so that probably means we should update to postgres 9.3.13 as
well.
SSL fixes: https://www.postgresql.org/docs/9.3/static/release-9-3-13.html
Perl fixes: https://www.postgresql.org/docs/9.3/static/release-9-3-12.html

So if nobody else is seeing these problems it¹s probably the particular
version of postgres we are using.

On 6/16/16, 12:05 PM, "Greg Sabino Mullane" <greg at endpoint.com> wrote:

>On Tue, Jun 07, 2016 at 08:02:21PM +0000, Balman, Matthew D.
>(GSFC-428.0)[Embedded Flight Systems, Inc] wrote:
>> I now see 4 log entries as like this:
>> 
>> (6234) [Tue Jun  7 19:20:25 2016] MCP Table public.table1 is referenced
>>by public.table2(fk_pri_0), which is not part of this sync!
>> 
>> I guess that's the first thing to fixŠ
>
>Any progress on this?
>
>-- 
>Greg Sabino Mullane greg at endpoint.com
>End Point Corporation
>PGP Key: 0x14964AC8