duplicity-team team mailing list archive

[edso <question284756@xxxxxxxxxxxxxxxxxxxxx>]

Question #284756 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/284756

    Status: Open => Answered

edso proposed the following answer:
On 07.02.2016 22:32, Jonathan Elchison wrote:
> New question #284756 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/284756
> 
> Hi folks, long-time fan of Duplicity.  Thanks for the great product!
> 
> Today I've become stumped, as a backup that had been working for years started reliably segfaulting mid-backup this month.  Full (sanitized) dump is below.
> 
> Sadly, I have no stack trace, and VERBOSE=9 produces nothing more then messages while searching/selecting.  No hints as to the segfault.
> 
> When running duplicity without duply, same result:  no stack trace.
> 
> I have duplicity installed via brew, so it's feasible that today was my first attempt running v0.7.06 on OS X.
> 
> What can I try/provide to help diagnose?
> 

looks like python is segfaulting

1. try w/o --progress´, it makes weird things sometimes

2. find where OSX logs it's segfaults. they should end up in a kernel
log or such.

3. have duply generate the command line for you via --preview switch..
run the command line manually and see if it now print the whole segfault
info, for you to take and web search for a solution

4. try to downgrade python, to a version that worked before


..ede/duply.net

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.