[Technology] Duplicity, DejaDup, and monitoring output

Due to another bug in DejaDup, you can only watch progress if you manually start a back-up.  If DejaDup beats you to the punch and automatically starts, you can't follow the progress.



Today, I figured out a way to watch:




$ ps aux | grep duplicity
username  12345 97.2  4.9 878235 345123 ?       Rsl  02:21  15:02 python2 /usr/bin/duplicity --exclude=/run/media/..... --tempdir=/home/username/.cache/deja-dup/tmp --log-fd=18

A-ha, a log fd. 

Go to /proc/PID/fd (/proc/12345/fd) and use cat or grep.

$ cat 18

This shows way too much info for me.  90% of it are my exclude globs. 

$ grep "examining path" 18

works well for seeing which file is being examined.  If you look at the output, you can also focus on when it finds files match (and don't need backing up) or when they're different.

deja-dup 35.5 and difficulty finding drive volumes

At some point, my version of Deja Dup upgraded to 35, and with it came a couple problems.



First, the command deja-dup-preferences is replaced with just deja-dup.  That's fine. 



Second, it could no longer detect my LUKS volume.  It gave me the option of using the partition that the LUKS volume is on, but even after I mounted and decrypted it as usual, I could not see the encrypted LUKS volume from deja-dup.  Normally under "Storage Location" (Speicherort) on mine, I have a drop down where I can select a few different options, Nextcloud, a Network Server, my volumes, or a local directory.  For some reason, it just wouldn't register this time, even after restarting deja-dup or remounting my volume.



I ended up using dconf-editor to manually set it up. 



Path: /org/gnome/deja-dup/drive/



I changed the name to the familiar drive name, and I also had to change the UUID.  I used the command 'blkid' as root to get the correct UUID.  I then restarted deja-dup and it now found it.



Weird.  I should file a bug soon.