[Borgbackup] Exception: /root/.cache/borg/c68...81e/config does not look like a Borg cache.

Wojtek Swiatek w at swtk.info
Wed Jun 17 13:37:13 EDT 2020


Hello everyone

I realized that one of my backups is not working anymore. It is launched
together with another one which backs up to the same place (just a
different directory) though the same command - and that second one works
without problems.

When trying to list the contents of the failing backup (to know how late I
am) I see

/etc/local # borg list /services/backup/borg/srv
Local Exception
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 4529, in main
    exit_code = archiver.run(args)
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 4461, in run
    return set_ec(func(args))
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 157, in
wrapper
    assert_secure(repository, kwargs['manifest'], self.lock_wait)
  File "/usr/lib/python3/dist-packages/borg/cache.py", line 206, in
assert_secure
    sm.assert_secure(manifest, manifest.key, lock_wait=lock_wait)
  File "/usr/lib/python3/dist-packages/borg/cache.py", line 171, in
assert_secure
    with cache_config:
  File "/usr/lib/python3/dist-packages/borg/cache.py", line 238, in
__enter__
    self.open()
  File "/usr/lib/python3/dist-packages/borg/cache.py", line 262, in open
    self.load()
  File "/usr/lib/python3/dist-packages/borg/cache.py", line 268, in load
    self._check_upgrade(self.config_path)
  File "/usr/lib/python3/dist-packages/borg/cache.py", line 327, in
_check_upgrade
    raise Exception('%s does not look like a Borg cache.' % config_path)
from None
Exception:
/root/.cache/borg/c6853ce826e2c5c62c58df2ac0eabca4cf087980944b57995703bd44cceb981e/config
does not look like a Borg cache.

Platform: Linux srv 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4
14:58:26 UTC 2020 x86_64
Linux: Ubuntu 18.04 bionic
Borg: 1.1.11  Python: CPython 3.6.9 msgpack: 0.5.6
PID: 23732  CWD: /etc/local
sys.argv: ['/usr/bin/borg', 'list', '/services/backup/borg/srv']
SSH_ORIGINAL_COMMAND: None


In contrast the working command:

/etc/local # borg list /services/backup/borg/edgerouter
b44277ee-4a84-4b73-b2db-69ea511be6e4 Sat, 2020-02-29 23:20:57
[822e95d0bbf6a8cbe5be6432e5044aea46d228ac1ed56474383a9daa594e0c69]
e0f38c38-f5aa-4531-aa2c-32bfdba0856f Tue, 2020-03-31 23:21:33
[306ff5ecf2f3995b82cfbf42607b6ccf904e473966ccf480e06fac20d5b236ae]
569ad25d-11a2-48e7-8c0c-513d45c88ea5 Thu, 2020-04-30 23:21:13
[30230caabb0ade5a77fde0776b61568f7f1ec3760502aed473eac53cabfe3d74]
ac3b8f7d-41c4-4add-aff2-88619d73c6c6 Sun, 2020-05-17 23:21:49
[cbd87b9d1cbfa2c7b9aa902d15f52773eb6eb6640bc8e45d140a30c6416e32fb]
(...)


Where should I go from there so that
/root/.cache/borg/c6853ce826e2c5c62c58df2ac0eabca4cf087980944b57995703bd44cceb981e/config
starts to look like a Borg cache? (or invalidate that specific backup).
I would be keen to retain the existing backups but if recovering is tricky
I will start from scratch to have something at least
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20200617/b4e37456/attachment.html>


More information about the Borgbackup mailing list