[Bucardo-general] 5.6.0 double free in VAC on CentOS7

Jeff Ross rossj at cargotel.com
Tue Mar 31 13:52:18 UTC 2020


bucardo went down last night.  On startup I got the following in the 
bucardo log:



*** Error in `Bucardo VAC.': double free or corruption (!prev): 0x00000000215ec990 ***
======= Backtrace: =========
/usr/lib64/libc.so.6(+0x7c503)[0x7fb60ba9e503]
/usr/lib64/perl5/vendor_perl/auto/DBD/Pg/Pg.so(pg_st_destroy+0x16f)[0x7fb603a67b3f]
/usr/lib64/perl5/vendor_perl/auto/DBD/Pg/Pg.so(+0xc2aa)[0x7fb603a532aa]
/usr/lib64/perl5/vendor_perl/auto/DBI/DBI.so(XS_DBI_dispatch+0xc47)[0x7fb6050e9707]
/usr/lib64/perl5/CORE/libperl.so(Perl_pp_entersub+0x58f)[0x7fb60ce2e42f]
/usr/lib64/perl5/CORE/libperl.so(Perl_call_sv+0x69d)[0x7fb60cdbe41d]
/usr/lib64/perl5/CORE/libperl.so(+0xc5185)[0x7fb60ce37185]
/usr/lib64/perl5/CORE/libperl.so(Perl_sv_clear+0x4b0)[0x7fb60ce37aa0]
/usr/lib64/perl5/CORE/libperl.so(Perl_sv_free2+0x4a)[0x7fb60ce3810a]
/usr/lib64/perl5/CORE/libperl.so(+0xbd887)[0x7fb60ce2f887]
/usr/lib64/perl5/CORE/libperl.so(Perl_sv_clean_objs+0x26)[0x7fb60ce38586]
/usr/lib64/perl5/CORE/libperl.so(perl_destruct+0x14be)[0x7fb60cdc08de]
Bucardo VAC.[0x400d61]
/usr/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fb60ba43b35]
Bucardo VAC.[0x400dd1]


The rest of the startup logs with double free report at 
https://www.openvistas.net/bucardo_log.txt -- too long to post to the 
mailing list.

bucardo status shows the following--other than the times nothing else 
changes.
[postgres at dbp3 ~]$ bucardo status
PID of Bucardo MCP: 26658
  Name State                                            Last 
good               Time          Last I/D    Last bad    Time
======================+================================================+=======================+=============+===========+===========+=========
  cargotel_common_sync | Good                                           
| 09:24:59              | 10m 40s     | 0/0       | none |
  load_sync            | Deleting based on cargotel_cargotel.metro.load 
| Mar 30, 2020 20:18:10 | 13h 17m 29s | 51/123    | 09:24:29  | 11m 10s
[postgres at dbp3 ~]$


logs on the receiving side show really no activity:

[sudo] password for cargotel:
2020-03-31 13:37:58.147 UTC [4359] bucardo at metro_sync_prod LOG: 
duration: 0.103 ms  statement: SELECT 'DBD::Pg ping test'
2020-03-31 13:37:59.135 UTC [768] bucardo at metro_sync_prod LOG: duration: 
0.113 ms  statement: SELECT 'DBD::Pg ping test'
2020-03-31 13:38:58.087 UTC [4359] bucardo at metro_sync_prod LOG: 
duration: 0.099 ms  statement: SELECT 'DBD::Pg ping test'
2020-03-31 13:38:59.208 UTC [768] bucardo at metro_sync_prod LOG: duration: 
0.120 ms  statement: SELECT 'DBD::Pg ping test'
2020-03-31 13:39:00.468 UTC [698] bucardo at metro_sync_prod LOG: duration: 
0.078 ms  statement: DEALLOCATE dbdpg_p26974_9
2020-03-31 13:39:00.516 UTC [698] bucardo at metro_sync_prod LOG: duration: 
0.029 ms  statement: begin
2020-03-31 13:39:00.564 UTC [698] bucardo at metro_sync_prod LOG: duration: 
0.067 ms  parse dbdpg_p26974_10: SELECT bucardo.bucardo_purge_delta('45 
seconds')
2020-03-31 13:39:00.612 UTC [698] bucardo at metro_sync_prod LOG: duration: 
0.045 ms  bind dbdpg_p26974_10: SELECT bucardo.bucardo_purge_delta('45 
seconds')
2020-03-31 13:39:00.634 UTC [698] bucardo at metro_sync_prod LOG: duration: 
21.780 ms  execute dbdpg_p26974_10: SELECT 
bucardo.bucardo_purge_delta('45 seconds')
2020-03-31 13:39:00.683 UTC [698] bucardo at metro_sync_prod LOG: duration: 
0.211 ms  statement: commit
2020-03-31 13:39:58.032 UTC [4359] bucardo at metro_sync_prod LOG: 
duration: 0.089 ms  statement: SELECT 'DBD::Pg ping test'
2020-03-31 13:39:59.282 UTC [768] bucardo at metro_sync_prod LOG: duration: 
0.099 ms  statement: SELECT 'DBD::Pg ping test'

This is the second time in about a week bucardo has gone down. Last time 
I ended up removing all of it and starting from scratch--hoping not to 
have to do that again.

I'd appreciate any help or suggestions on how to get going again.

Jeff Ross

-- Jeff Ross rossj at cargotel.com

-- 
The contents of this e-mail and any attachments are intended solely for the 
use of the named addressee(s) and may contain confidential and/or 
privileged information. Any unauthorized use, copying, disclosure, or 
distribution of the contents of this e-mail is strictly prohibited by the 
sender and may be unlawful. If you are not the intended recipient, please 
notify the sender immediately and delete this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://bucardo.org/pipermail/bucardo-general/attachments/20200331/d0cc8c7a/attachment.htm>


More information about the Bucardo-general mailing list