On 12/13/13, 2:17 AM, Michelle Sullivan wrote:
David E. Wheeler wrote:
As a matter of interest (and that I could possibly write a patch for
this... Care to explain more?
I see this with bucardo status on my systems:
michelle@corkscrew:~$ bucardo status
PID of Bucardo MCP: 15446
Name State Last good Time
Last I/D Last bad Time
============+====================================+============+========+===========+=======================+===============
dnsmm | Good | 10:01:30 | 8m 22s |
0/0 | Dec 05, 2013 00:08:30 | 202h 1m 22s
dnsrbls | Good | 10:01:32 | 8m 20s |
0/0 | 01:01:33 | 9h 8m 19s
dnsseq | Good | 10:00:02 | 9m 50s |
0/0 | Oct 18, 2013 16:24:39 | 1337h 45m 13s
sessions | Begin txn (KID 15982) | 10:09:43 | 9s |
0/4 | Dec 10, 2013 18:35:21 | 63h 34m 31s
sessionsdb | Sync public.sessions (KID 15976) | 10:09:50 | 2s |
6/9 | Dec 11, 2013 06:13:32 | 51h 56m 20s
sorbsmm | Sync public.timestamps (KID 25351) | 10:09:45 | 7s |
16/64 | 07:57:56 | 2h 11m 56s
sorbsmmseq | Begin txn (KID 15986) | none |
| | Dec 11, 2013 06:13:32 | 51h 56m 20s
sorbsqs | Begin txn (KID 16001) | 10:08:30 | 1m 22s |
0/40 | Dec 10, 2013 18:55:49 | 63h 14m 4s
sorbsstats | Good | 10:09:45 | 7s |
0/0 | 06:09:27 | 4h 26s
Which shows quite a mixture.. you want to clear the 'last bad' field?
My example should probably be refined as:
bucardo clear lasterr some_sync
If I do:
bucardo status trumgr_main_sync
I get this output:
======================================================================
Last good : Dec 09, 2013 13:04:02 (time to run: 2s)
Rows deleted/inserted : 994 / 994
Last bad : Dec 09, 2013 09:53:39 (time until fail: 3s)
Sync name : trumgr_main_sync
Current state : Good
Source relgroup/database : trumgr_main_rels / local_trumgr_main
Tables in sync : 75
Status : Active
Check time : None
Overdue time : 00:00:00
Expired time : 00:00:00
Stayalive/Kidsalive : Yes / Yes
Rebuild index : No
Autokick : Yes
Onetimecopy : No
Post-copy analyze : Yes
Last error: : Failed : DBD::Pg::db pg_putcopyend failed:
ERROR: extra data after last expected column
CONTEXT: COPY breadsticks_are_delicious, line 1: "94 323 232
119906880787 \N 46" at /usr/local/share/perl/5.10.1/Bucardo.pm
line 9054. Line: 4920 Main DB state: ? Error: none DB local_trumgr_main
state: ? Error: none DB remote_trumgr_main state: 22P04 Error: 7 (KID
29577)
======================================================================
(This during testing). So, the last thing that hits my eye is "oh shit
errors", even though about 13 lines up, the current state is 'good', and
the error is quite stale. If I had 'bucardo clear lasterr
trumgr_main_sync', the field could perhaps reflect:
======================================================================
Last good : Dec 09, 2013 13:04:02 (time to run: 2s)
Rows deleted/inserted : 994 / 994
Last bad : Dec 09, 2013 09:53:39 (time until fail: 3s)
Sync name : trumgr_main_sync
Current state : Good
Source relgroup/database : trumgr_main_rels / local_trumgr_main
Tables in sync : 75
Status : Active
Check time : None
Overdue time : 00:00:00
Expired time : 00:00:00
Stayalive/Kidsalive : Yes / Yes
Rebuild index : No
Autokick : Yes
Onetimecopy : No
Post-copy analyze : Yes
Last error: : Cleared Dec 13, 2013
======================================================================
I'm adding the above as an 'issue' right now per David.
--
Paul Theodoropoulos
www.anastrophe.com
_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
