duplicity-team team mailing list archive

[Jonathan Elchison <question284756@xxxxxxxxxxxxxxxxxxxxx>]

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?

Thanks!

--

```
$ sudo duply Computer_External bkp+purge+purgeFull_cleanup_status --force
Start duply v1.10.1, time is 2016-02-07 15:27:59.
Using profile '/Users/user/.duply/Computer_External'.
Using installed duplicity version 0.7.06, python 2.7.11, gpg: unsafe (Home: ~/.gnupg), awk 'awk version 20070501', grep 'grep (BSD grep) 2.5.1-FreeBSD', bash '3.2.57(1)-release (x86_64-apple-darwin15)'.
Checking TEMP_DIR '/tmp' is a folder (OK)
Checking TEMP_DIR '/tmp' is writable (OK)
Test - En/Decryption skipped. (Testing disabled)

--- Start running command BKP at 15:28:00.000 ---
Reading globbing filelist /Users/user/.duply/Computer_External/exclude
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted session
Last full backup date: Sun Dec 20 00:28:02 2015
Reading globbing filelist /Users/user/.duply/Computer_External/exclude
<snip>
0.0KB 00:13:58 [0.0B/s] [>                                        ] 0% ETA Stalled!
/usr/local/bin/duply: line 1151:  1643 Segmentation fault: 11  TMPDIR='/tmp' PASSPHRASE=‘enckeypass’ SIGN_PASSPHRASE=‘signkeypass’ duplicity --name duply_Computer_External --encrypt-key enckey1 --encrypt-key enckey2 --sign-key signkey1 --verbosity '4' --full-if-older-than 1Y --progress --asynchronous-upload --file-prefix-archive 'archive-' --allow-source-mismatch --force --exclude-filelist '/Users/user/.duply/Computer_External/exclude' '/Users/otheruser’ 'file:///Volumes/External/bak/machines/Computer/'
16:00:24.000 Task 'BKP' failed with exit code '139'.
--- Finished state FAILED 'code 139' at 16:00:24.000 - Runtime 00:32:24.000 ---

--- Skipping command PURGE ! ---

--- Skipping command PURGEFULL ! ---

--- Start running command CLEANUP at 16:00:24.000 ---
Another instance is already running with this archive directory
If you are sure that this is the  only instance running you may delete
the following lockfile and run the command again :
	/Users/user/.cache/duplicity/duply_Computer_External/lockfile.lock
16:00:34.000 Task 'CLEANUP' failed with exit code '23'.
--- Finished state FAILED 'code 23' at 16:00:34.000 - Runtime 00:00:10.000 ---

--- Start running command STATUS at 16:00:34.000 ---
Another instance is already running with this archive directory
If you are sure that this is the  only instance running you may delete
the following lockfile and run the command again :
	/Users/user/.cache/duplicity/duply_Computer_External/lockfile.lock
16:00:34.000 Task 'STATUS' failed with exit code '23'.
--- Finished state FAILED 'code 23' at 16:00:34.000 - Runtime 00:00:00.000 ---
```

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