Backup Issue (GPG Error)

Help with Setup/Upgrade
1

Backups on a fresh MIAB install are failing with the following error:

GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: Note: ‘–force-mdc’ is not considered an option
gpg: Note: ‘–symmetric’ is not considered an option
gpg: WARNING: no command supplied. Trying to guess what you mean …
usage: gpg [options] [filename]
===== End GnuPG log =====

Traceback (most recent call last):
File “/root/mailinabox/management/backup.py”, line 655, in
perform_backup(full_backup)
File “/root/mailinabox/management/backup.py”, line 322, in perform_backup
shell(‘check_call’, [
File “/root/mailinabox/management/utils.py”, line 127, in shell
ret = getattr(subprocess, method)(cmd_args, **kwargs)
File “/usr/lib/python3.10/subprocess.py”, line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[’/usr/bin/duplicity’, ‘full’, ‘–verbosity’, ‘warning’, ‘–no-print-statistics’, ‘–archive-dir’, ‘/home/user-data/backup/cache’, ‘–exclude’, ‘/home/user-data/backup’, ‘–exclude’, ‘/home/user-data/owncloud-backup’, ‘–volsize’, ‘250’, ‘–gpg-options’, “‘–cipher-algo=AES256’”, ‘–allow-source-mismatch’, ‘/home/user-data’, ‘file:///home/user-data/backup/encrypted’]’ returned non-zero exit status 31.
root@box:~# nano mailinabox/management/backup.py

Anyone know how I can resolve this?

2

There are currently issues with duplicity, the tool that is used to perform the backup. However, it might be something else. What version of Mail-in-a-Box are you running? And what version of duplicity is installed? (duplicity --version). Also, are you running on Amd64 or ARM?

3

Hi,

same error there, after removed it and then installed snap version of duplicity --cliassic (due to the current issue Something is wrong with the backup: - #16 by dfowlkes)

the snap version is 3.0.5.

4

Sorry to hear you are having the same error. I have install the snap version of duplicity --classic on two AWS Ubuntu servers, the duplicity version is also 3.0.5. Both are now doing backups on schedule correctly via rsync to a third remote server.

5

Me too, I’m having backup issues since the last MIAB upgrade:

Traceback (most recent call last):
File “/usr/bin/duplicity”, line 5, in
from duplicity.main import dup_run
ModuleNotFoundError: No module named ‘duplicity.main’
Something is wrong with the backup:

6

It appears Duplicity 3.0.5.1 is released and it works

do:

sudo apt-mark unhold duplicity
sudo apt update
sudo apt upgrade
sudo apt-mark hold duplicity

results in…
Get:1 Index of /duplicity-team/duplicity-release-git/ubuntu jammy/main amd64 duplicity amd64 3.0.5.1-ppa202506251611~ubuntu22.04.1 [404 kB]
Fetched 404 kB in 3s (150 kB/s)
(Reading database … 145817 files and directories currently installed.)
Preparing to unpack …/duplicity_3.0.5.1-ppa202506251611~ubuntu22.04.1_amd64.deb …
Unpacking duplicity (3.0.5.1-ppa202506251611~ubuntu22.04.1) over (3.0.4-ppa202502081832~ubuntu22.04.1) …
Setting up duplicity (3.0.5.1-ppa202506251611~ubuntu22.04.1) …

I have run backups and they work fine now, however I will be putting a hold on future updates however as this is second time in 1 year backups have broken

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.