[Bucardo-general] Bucardo Crash

Balman, Matthew D. (GSFC-428.0)[Embedded Flight Systems, Inc] matthew.d.balman at nasa.gov
Tue Jun 7 19:54:59 UTC 2016


Hi All,

Running bucardo 5.4.1
Any idea why bucardo would crash?
We have 2 master dbs with 1 slave.
The 2 master Dbs are basically redundant log servers and usually get identical/conflicting records all the time which bucardo usually resolves just fine.

Here are my log entries:

(29610) [Sun Jun  5 10:47:42 2016] KID (greatsync) Conflicts for public.events: 1
(29610) [Sun Jun  5 10:47:42 2016] KID (greatsync) Conflicts have been resolved
(29610) [Sun Jun  5 10:47:42 2016] KID (greatsync) Warning! Aborting due to exception for public.events:? Error was DBD::Pg::db pg_putcopyend failed: ERROR:  duplicate key value violates unique constraint "events_pkey"\nDETAIL:  Key ("UNIQUE-ID")=(<some long string id>) already exists.\nCONTEXT:  COPY events, line 2 at Bucardo.pm line 9879.
(29610) [Sun Jun  5 10:47:42 2016] KID (greatsync) Kid has died, error is: DBD::Pg::db pg_putcopyend failed: ERROR:  duplicate key value violates unique constraint "events_pkey"\nDETAIL:  Key ("UNIQUE-ID")=(<some long string id>) already exists.\nCONTEXT:  COPY events, line 2 at Bucardo.pm line 9879. Line: 5041 Main DB state: ? Error: none DB greatdb1 state: ? Error: none DB greatdb2 state: 23505 Error: 7 DB greatdbo state: ? Error: none
(29610) [Sun Jun  5 10:47:42 2016] KID (greatsync) Kid 29610 exiting at cleanup_kid. Sync "greatsync" public.events Reason: DBD::Pg::db pg_putcopyend failed: ERROR:  duplicate key value violates unique constraint "events_pkey"\nDETAIL:  Key ("UNIQUE-ID")=(<some long string id>) already exists.\nCONTEXT:  COPY events, line 2 at Bucardo.pm line 9879. Line: 5041 Main DB state: ? Error: none DB greatdb1 state: ? Error: none DB greatdb2 state: 23505 Error: 7 DB greatdbo state: ? Error: none
(25509) [Sun Jun  5 10:47:42 2016] MCP Warning: Killed (line 6353): DBD::Pg::db do failed: no connection to the server at Bucardo.pm line 6353.
(25534) [Sun Jun  5 10:47:44 2016] CTL Controller for "easync" was killed at line 1755: MCP request
(25519) [Sun Jun  5 10:47:44 2016] CTL Controller for "greatsync" was killed at line 1755: MCP request
(25537) [Sun Jun  5 10:47:44 2016] KID (easync) Kid has died, error is: CTL request Line: 5001
(25537) [Sun Jun  5 10:47:44 2016] KID (easync) Kid 25537 exiting at cleanup_kid. Sync "easync" public.zenoss_devices Reason: CTL request Line: 5001
(25509) [Sun Jun  5 10:47:44 2016] MCP End of cleanup_mcp. Sys time: Sun Jun  5 10:47:44 2016. Database time: 2016-06-05 10:47:44.239691+00
(25534) [Sun Jun  5 10:47:44 2016] CTL Controller 25534 exiting at cleanup_controller. Reason: MCP request
(25519) [Sun Jun  5 10:47:44 2016] CTL Controller 25519 exiting at cleanup_controller. Reason: MCP request


/*****************************
Matthew Balman
Software Engineer
EOS Automation
Embedded Flight Systems, Inc.
Matthew.D.Balman at NASA.gov
******************************/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20160607/c66b927a/attachment-0001.html>


More information about the Bucardo-general mailing list