"Error running configuration file" #429
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#429
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
While crating backup or prunning or something else I have error, but I can list archives and restore. I have run sudo validate-borgmatic-config with no errors. I have left my system with no maintanance for more than half an year, so it difficult to guess where the problem could be. I have new source PC and new borgmatic install and I have same server with the same borg system for more than an year that previously worked fine. I have tryed now to update borg in server side after I find out tha something doesnt work, before posting in here.
Steps to reproduce (if a bug)
are@workstation2:~/extract> sudo borgmatic --verbosity 2 --files
Actual behavior (if a bug)
are@workstation2:~/extract> sudo borgmatic --verbosity 2 --files
Ensuring legacy configuration is upgraded
/etc/borgmatic/config.yaml: No commands to run for pre-everything hook
/etc/borgmatic/config.yaml: Calling healthchecks hook function initialize_monitor
/etc/borgmatic/config.yaml: Running command for pre-prune hook
echo "Starting pruning."
Starting pruning.
/etc/borgmatic/config.yaml: Running command for pre-backup hook
echo "Starting a backup."
Starting a backup.
/etc/borgmatic/config.yaml: Running command for pre-check hook
echo "Starting consistency checks."
Starting consistency checks.
/etc/borgmatic/config.yaml: Calling healthchecks hook function ping_monitor
/etc/borgmatic/config.yaml: Pinging Healthchecks start
/etc/borgmatic/config.yaml: Using Healthchecks ping URL https://hc-ping.com/748
borgas@backupnas.are.lab:/export/backups/workstation/: Pruning archives
borg prune --keep-weekly 4 --keep-monthly 9 --prefix {hostname}- --list --debug --show-rc borgas@backupnas.are.lab:/export/backups/workstation/
using builtin fallback logging configuration
35 self tests completed in 0.05 seconds
SSH command line: ['ssh', '-i', '/home/are/.ssh/are_ecdsa', 'borgas@backupnas.are.lab', 'borg', 'serve', '--umask=077', '--debug']
Remote: using builtin fallback logging configuration
Remote: 35 self tests completed in 0.45 seconds
Remote: using builtin fallback logging configuration
Remote: Initialized logging system for JSON-based protocol
Remote: Resolving repository path b'/export/backups/workstation'
Remote: Resolved repository path to '/export/backups/workstation'
Remote: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/borg/remote.py", line 247, in serve
res = f(**args)
File "/usr/lib/python3/dist-packages/borg/remote.py", line 375, in open
self.repository.enter() # clean exit handled by serve() method
File "/usr/lib/python3/dist-packages/borg/repository.py", line 190, in enter
self.open(self.path, bool(self.exclusive), lock_wait=self.lock_wait, lock=self.do_lock)
File "/usr/lib/python3/dist-packages/borg/repository.py", line 421, in open
self.lock = Lock(os.path.join(path, 'lock'), exclusive, timeout=lock_wait, kill_stale_locks=hostname_is_unique()).acquire()
File "/usr/lib/python3/dist-packages/borg/locking.py", line 350, in acquire
self._wait_for_readers_finishing(remove, sleep)
File "/usr/lib/python3/dist-packages/borg/locking.py", line 379, in _wait_for_readers_finishing
raise LockTimeout(self.path)
borg.locking.LockTimeout: Failed to create/acquire the lock /export/backups/workstation/lock (timeout).
Failed to create/acquire the lock /export/backups/workstation/lock (timeout).
Borg server: Platform: Linux backupnas 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64
borgas@backupnas.are.lab:/export/backups/workstation/: Error running actions for repository
Command 'borg prune --keep-weekly 4 --keep-monthly 9 --prefix {hostname}- --list --debug --show-rc borgas@backupnas.are.lab:/export/backups/workstation/' returned non-zero exit status 2.
/etc/borgmatic/config.yaml: Running command for on-error hook
echo "Error during prune or create or check."
Error during prune or create or check.
/etc/borgmatic/config.yaml: Calling healthchecks hook function ping_monitor
/etc/borgmatic/config.yaml: Pinging Healthchecks fail
/etc/borgmatic/config.yaml: Using Healthchecks ping URL https://hc-ping.com/7481
/etc/borgmatic/config.yaml: Calling healthchecks hook function destroy_monitor
/etc/borgmatic/config.yaml: Error running configuration file
/etc/borgmatic/config.yaml: No commands to run for post-everything hook
summary:
/etc/borgmatic/config.yaml: Error running configuration file
borgas@backupnas.are.lab:/export/backups/workstation/: Error running actions for repository
...
using builtin fallback logging configuration
35 self tests completed in 0.05 seconds
SSH command line: ['ssh', '-i', '/home/are/.ssh/are_ecdsa', 'borgas@backupnas.are.lab', 'borg', 'serve', '--umask=077', '--debug']
Remote: using builtin fallback logging configuration
Remote: 35 self tests completed in 0.45 seconds
Remote: using builtin fallback logging configuration
Remote: Initialized logging system for JSON-based protocol
Remote: Resolving repository path b'/export/backups/workstation'
Remote: Resolved repository path to '/export/backups/workstation'
Remote: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/borg/remote.py", line 247, in serve
res = f(**args)
File "/usr/lib/python3/dist-packages/borg/remote.py", line 375, in open
self.repository.enter() # clean exit handled by serve() method
File "/usr/lib/python3/dist-packages/borg/repository.py", line 190, in enter
self.open(self.path, bool(self.exclusive), lock_wait=self.lock_wait, lock=self.do_lock)
File "/usr/lib/python3/dist-packages/borg/repository.py", line 421, in open
self.lock = Lock(os.path.join(path, 'lock'), exclusive, timeout=lock_wait, kill_stale_locks=hostname_is_unique()).acquire()
File "/usr/lib/python3/dist-packages/borg/locking.py", line 350, in acquire
self._wait_for_readers_finishing(remove, sleep)
File "/usr/lib/python3/dist-packages/borg/locking.py", line 379, in _wait_for_readers_finishing
raise LockTimeout(self.path)
borg.locking.LockTimeout: Failed to create/acquire the lock /export/backups/workstation/lock (timeout).
Failed to create/acquire the lock /export/backups/workstation/lock (timeout).
Borg server: Platform: Linux backupnas 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64
Command 'borg prune --keep-weekly 4 --keep-monthly 9 --prefix {hostname}- --list --debug --show-rc borgas@backupnas.are.lab:/export/backups/workstation/' returned non-zero exit status 2.
Need some help? https://torsion.org/borgmatic/#issues
Expected behavior (if a bug)
Other notes / implementation ideas
Server side is Openmediavault taht originaly used with plugin for borg, it did worked previuosly as I mentioned.
Environment
borgmatic version: [borgmatic --version
1.5.15]
borgmatic installation method: [pip] on suse thumbleweed
Borg version: [borg 1.1.16]
Python version: [Python 3.8.10]
operating system and version: [OpenSUSE Thumbleweed] client side. And [Debian GNU/Linux 10 (buster) 5.10.0-0.bpo.3-amd64]
Thank you
Let's call this case closed. After all updates reboots it worked. It can also be the client's hostname not the same as per archived machine's name.
Thank your borgmatic.