Paul Theodoropoulos wrote: > I'm getting failures on a couple of syncs today, and I've no idea what > to make of these errors. Do these ring a bell for anyone? > > (4860) [Wed Apr 23 10:20:31 2014] KID (trumgr_group_sync) New kid, > sync "trumgr_group_sync" alive=1 Parent=28837 PID=4860 kicked=1 > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > (4860) [Wed Apr 23 10:50:48 2014] KID (trumgr_group_sync) Warning! > Aborting due to exception for public.unit_history_89:? Error was > DBD::Pg::db pg_result failed: No asynchronous query is running at > /usr/local/share/perl/5.10.1/Bucardo.pm line 8720. > DBI::db=HASH(0xa7476b8)->disconnect invalidates 37 active statement > handles (either destroy statement handles or call finish on them > before disconnecting) at /usr/local/share/perl/5.10.1/Bucardo.pm line > 2291. > DBI::db=HASH(0xa75d800)->disconnect invalidates 3 active statement > handles (either destroy statement handles or call finish on them > before disconnecting) at /usr/local/share/perl/5.10.1/Bucardo.pm line > 2291. > (4860) [Wed Apr 23 10:50:49 2014] KID (trumgr_group_sync) DBD::Pg::db > pg_result failed: No asynchronous query is running at > /usr/local/share/perl/5.10.1/Bucardo.pm line 8720. Line: 4920 Main DB > state: ? Error: none DB local_trumgr_group state: ? Error: 7 DB > remote_trumgr_group state: ? Error: none > (4860) [Wed Apr 23 10:50:49 2014] KID (trumgr_group_sync) Kid 4860 > exiting at cleanup_kid. Sync "trumgr_group_sync" > public.unit_history_89 Reason: DBD::Pg::db pg_result failed: No > asynchronous query is running at > /usr/local/share/perl/5.10.1/Bucardo.pm line 8720. Line: 4920 Main DB > state: ? Error: none DB local_trumgr_group state: ? Error: 7 DB > remote_trumgr_group state: ? Error: none > (17197) [Wed Apr 23 10:50:52 2014] KID (trumgr_group_sync) New kid, > sync "trumgr_group_sync" alive=1 Parent=28837 PID=17197 kicked=1 > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > Exiting eval via redo at /usr/local/share/perl/5.10.1/Bucardo.pm line > 4953. > > I've restarted bucardo, and the logs have quieted down, but I'm > particularly worried about those HASH errors (mainly just because they > look ind of ominous). > > I'm running bucardo 4.9.11, pulled from git on Jan 23. DBD::Pg is v > 2.19.3, DBIx::Safe is 1.2.5. Postgresql 9.1, Debian Squeeze, 32bit. > -- > Paul Theodoropoulos > www.anastrophe.com > ------------------------------------------------------------------------ > > _______________________________________________ > Bucardo-general mailing list > [email protected] > https://mail.endcrypt.com/mailman/listinfo/bucardo-general > I see them from time to time, a restart fixes and no data is lost... Not found the cause here yet except its always the same table that starts it ...
Michelle -- Michelle Sullivan http://www.mhix.org/ _______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
