Stuck on assert

[eezacque]

I had used borg backup for years, to my full satisfaction, until I had to leave my home last January. Last week, I finally got a chance to set up my nas, network and computer, only to find borg refuses to start up:

borg-daily.service - Borg daily backup service
     Loaded: loaded (/etc/xdg/systemd/user/borg-daily.service; enabled; preset: enabled)
     Active: failed (Result: timeout) since Sun 2025-11-16 13:18:43 CET; 13min ago
TriggeredBy: ● borg-daily.timer
    Process: 4667 ExecStartPre=/usr/bin/borg break-lock ssh://borg@leviathan:709/~/backup (code=exited, status=143)
        CPU: 304ms

nov 16 13:18:43 behemoth borg[4667]: Exception ignored in: <function RemoteRepository.__del__ at 0x72d97c3187c0>
nov 16 13:18:43 behemoth borg[4667]: Traceback (most recent call last):
nov 16 13:18:43 behemoth borg[4667]:   File "/usr/lib/python3/dist-packages/borg/remote.py", line 624, in __del__
nov 16 13:18:43 behemoth borg[4667]:     assert False, 'cleanup happened in Repository.__del__'
nov 16 13:18:43 behemoth borg[4667]:            ^^^^^
nov 16 13:18:43 behemoth borg[4667]: AssertionError: cleanup happened in Repository.__del__
nov 16 13:18:43 behemoth borg[4667]: Received SIGTERM
nov 16 13:18:43 behemoth systemd[2929]: borg-daily.service: Control process exited, code=exited, status=143/n/a
nov 16 13:18:43 behemoth systemd[2929]: borg-daily.service: Failed with result 'timeout'.
nov 16 13:18:43 behemoth systemd[2929]: Failed to start borg-daily.service - Borg daily backup service.

Looks like something collapsed when I prematurely shut down my nas.
Any help on how to get this into workig order is appreciated.

[ThomasWaldmann]

assert False, 'cleanup happened in Repository.del'

That is usually a secondary effect after a primary exception. The primary exception would be more interesting.

Be careful: if you unconditionally break the locks, you might damage your repo.