“sudo: borg: command not found”

petesim · August 25, 2025, 1:26pm

What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.0.17
What app is this about: Borg

Describe your issue

I used to invoke it with a following command, but now am getting “sudo: borg: command not found” and have no idea how to remediate. Reading <apps/borg/operations> didn’t help me with this.

$ sudo BORG_RSH="ssh -i /root/.ssh/id_borg_ed25519 -oStrictHostKeyChecking=yes" borg list ssh://...

Share relevant logs or error messages

Quite recently the app was updated to “Installed version: 1.4.1~ynh1”.

fflorent · August 25, 2025, 1:38pm

Hi @petesim,

That’s because the borg binary is not included in your $PATH.

Take a look at the admin documentation to understand how to use the borg command:

github.com/YunoHost-Apps/borg_ynh

doc/ADMIN.md

02913291e

## Reminder regarding the passphrase

The passphrase is the only way to decrypt your backups. You should make sure to keep it safe in some place "outside" your server to cover the scenario where your server is destroyed for some reason.

## Testing that backup work as expected

At this step your backup should run at the scheduled time. Note that the first backup can take very long, as much data has to be copied through ssh. Following backups are incremental: only newly generated data since last backup will be copied.

If you want to test correct Borg Apps setup before scheduled time, you can start a backup manually from the command line:

```bash
systemctl start borg
```

Once the backup completes, you can check that a backup is listed in the webadmin > Applications > Borg > 'Last backups list'.

## Manually running `borg` commands

The config panel has a "Last backup list" that allow to have quick look at the recently created backup archives.

This file has been truncated. show original

petesim · August 25, 2025, 1:43pm

Thank you for such a swift reply! I’m trying not to manually modify Ynh settings since it tends to hit back later when an upgrade assumes something. X) I liked how it worked more smoothly before. =(

Meanwhile I got pretty same binary path </var/www/borg/venv/bin/borg> from the logs (even more concrete than the notes) to use in the command as the workaround.

fflorent · August 25, 2025, 1:47pm

You don’t have to. The commands mentioned in the paragraph “Manually running borg commands” are meant to be executed in a bash CLI prompt, and these will not change your settings.

That’s basically equivalent, yes!

petesim · August 25, 2025, 1:53pm

Oh, that’s what I started with. (“Reading <apps/borg/operations> didn’t help me with this.”) I tried to just feed each line but no luck.
Now I thought that you meant exporting it to the file permanently. X)

system · September 9, 2025, 1:54pm

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