#borg backup doesn't work anymore, it did for a year, now I get:

Remote: sh: borg: command not found Connection closed by remote host. Is borg working on the server?



Any idea why this suddenly happens from multiple systems doing a backup to the same destination server?

#Linux
I found that "which borg" gave me the path to borg (remote and local), but I found that the path was different from the one of the machine that serves the backup (that I perform the backup from), which for some reason seems to be the problem. It seems that borg can't find the correct path on the Synology NAS anymore, it worked for some months.

I now did "ln -s" remotely to create a symlink for borg in the same path as the serving machines borg is in found in. That seems to have solved the problem.

I find this very strange.

Maybe I did that before already and due to an update of borg on Synology NAS that borg (script - it is a script that is the binary) binary was removed an thus the previously created symlink was removed too?
Sign in to participate in the conversation
\m/ Metalhead.club \m/

Metalhead.club is a Mastodon instance hosted in Germany and powered by 100% green energy. Mastodon is a free and decentralized alternative to well-established social microblogging platforms like Twitter. This instance is especially addressing Metal fans, but of course everybody is welcome to use metalhead.club. If you're using this Mastodon instance, please consider a single donation or monthly, recurring donations via LiberaPay to keep this instance metalling hard.
Either via LiberaPay: Donate via LiberaPay ... or other means: https://thomas-leister.de/en/donate/