[Bucardo-general] Install Bucardo on Amazon RDS PostgreSQL

caleb ayodele ulo23k at gmail.com
Wed Jan 17 15:32:35 UTC 2018


[cayodele at ip-1xx-x-x-xx bucardo-master]$ bucardo validate sync auth_sync
Validating sync auth_sync ... OK

On Wed, Jan 17, 2018 at 10:26 AM, David Christensen <david at endpoint.com>
wrote:

> What happens when you run “bucardo validate sync <syncname>”?
>
>
> On Jan 17, 2018, at 9:23 AM, caleb ayodele <ulo23k at gmail.com> wrote:
>
> That doesn't exist in the source RDS instance.
>
> \df bucardo.bucardo_check_delta
>                        List of functions
>  Schema | Name | Result data type | Argument data types | Type
> --------+------+------------------+---------------------+------
> (0 rows)
>
> auth=> \d bucardo.bucardo_check_delta
> Did not find any relation named "bucardo.bucardo_check_delta".
>
> On Wed, Jan 17, 2018 at 10:18 AM, David Christensen <david at endpoint.com>
> wrote:
>
>> That would exist on the database that you setup as the source, not on the
>> main bucardo database.
>>
>>
>> On Jan 17, 2018, at 9:04 AM, caleb ayodele <ulo23k at gmail.com> wrote:
>>
>> The problem is that i already tried to find the function and it doesn't
>> exist in the local database that bucardo installed in.
>>
>> bucardo=# \d bucardo.bucardo_check_delta
>> Did not find any relation named "bucardo.bucardo_check_delta".
>>
>> bucardo=# \df bucardo.bucardo_check_delta
>>                        List of functions
>>  Schema | Name | Result data type | Argument data types | Type
>> --------+------+------------------+---------------------+------
>> (0 rows)
>>
>> On Wed, Jan 17, 2018 at 9:20 AM, David Christensen <david at endpoint.com>
>> wrote:
>>
>>>
>>>
>>> On Jan 15, 2018, at 2:06 PM, caleb ayodele <ulo23k at gmail.com> wrote:
>>>
>>> Bucardo Inernal log:
>>> --------------------------
>>>
>>> (17427) [Mon Jan 15 20:03:49 2018] KID (auth_sync) New kid, sync
>>> "auth_sync" alive=1 Parent=17424 PID=17427 kicked=1
>>> (17427) [Mon Jan 15 20:04:08 2018] KID (auth_sync) Kid has died, error
>>> is: DBD::Pg::st execute failed: ERROR:  query string argument of EXECUTE is
>>> null CONTEXT:  PL/pgSQL function bucardo.bucardo_delta_check(text,text)
>>> line 24 at EXECUTE statement at /usr/local/share/perl5/Bucardo.pm line
>>> 3407. Line: 5037 Main DB state: ? Error: none DB auth93 state: 22004 Error:
>>> 7 DB auth96 state: ? Error: none
>>> (17427) [Mon Jan 15 20:04:08 2018] KID (auth_sync) Kid 17427 exiting at
>>> cleanup_kid. Sync "auth_sync" public.activation_token_id_seq Reason:
>>> DBD::Pg::st execute failed: ERROR:  query string argument of EXECUTE is
>>> null CONTEXT:  PL/pgSQL function bucardo.bucardo_delta_check(text,text)
>>> line 24 at EXECUTE statement at /usr/local/share/perl5/Bucardo.pm line
>>> 3407. Line: 5037 Main DB state: ? Error: none DB auth93 state: 22004 Error:
>>> 7 DB auth96 state: ? Error: none
>>> (17419) [Mon Jan 15 20:04:09 2018] MCP Starting check_sync_health
>>>
>>>
>>> Can you raise the log level to DEBUG for that function?  (`ALTER
>>> FUNCTION bucardo.bucardo_check_delta SET log_min_messages = DEBUG`)  I’d
>>> like to see the inputs to the bucardo_delta_check function; if either of
>>> them were NULL for some reason then the overall statement will be NULL that
>>> gets executed.
>>>
>>>
>>> RDS log:
>>> --------------
>>> 2018-01-15 20:02:58 UTC::[unknown]@[unknown]:[28222]:WARNING:
>>> pg_getnameinfo_all() failed: Temporary failure in name resolution
>>> 2018-01-15 20:03:18 UTC::[unknown]@[unknown]:[28420]:WARNING:
>>> pg_getnameinfo_all() failed: Temporary failure in name resolution
>>> 2018-01-15 20:03:38 UTC::[unknown]@[unknown]:[28632]:WARNING:
>>> pg_getnameinfo_all() failed: Temporary failure in name resolution
>>> 2018-01-15 20:03:38 UTC::[unknown]@[unknown]:[28633]:WARNING:
>>> pg_getnameinfo_all() failed: Temporary failure in name resolution
>>> 2018-01-15 20:03:58 UTC::[unknown]@[unknown]:[28870]:WARNING:
>>> pg_getnameinfo_all() failed: Temporary failure in name resolution
>>>
>>>
>>> I’m interested in this, but not convinced this is related, at least
>>> directly.
>>>
>>>
>>> --
>>> David Christensen
>>> End Point Corporation
>>> david at endpoint.com
>>> 785-727-1171 <(785)%20727-1171>
>>>
>>>
>>>
>>>
>>
>> --
>> David Christensen
>> End Point Corporation
>> david at endpoint.com
>> 785-727-1171 <(785)%20727-1171>
>>
>>
>>
>>
>
> --
> David Christensen
> End Point Corporation
> david at endpoint.com
> 785-727-1171 <(785)%20727-1171>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20180117/95c207de/attachment.html>


More information about the Bucardo-general mailing list