-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Borg not found on the remote host. #166
Comments
I try to add userA in the borg group :
It helps, userA can now launch borg. I can check the last backup :
But it doesn't allow me to do a backup. I try to change the command in authorized_keys :
On serverA, I start borg service : $ sudo systemctl start borg & It doesn't fail directly : $ sudo systemctl status borg
● borg.service - Run backup borg
Loaded: loaded (/etc/systemd/system/borg.service; static)
Active: activating (start) since Wed 2024-07-24 08:04:55 UTC; 14min ago
(...) On serverB, I can't do a borg list because there is a lock : $ $borg list /home/userA/backup/
Failed to create/acquire the lock /home/userA/backup/lock.exclusive (timeout). Seems good 👍 ? I am waiting to be sure... |
It works. Backup seems good since the last message. But I am afraid it will break again at the next backup... |
After upgrade of borgserver app, I think I had a similar issue https://paste.yunohost.org/raw/tiguxemobu ping @zamentur @Salamandar |
Describe the bug
I have two servers with Yunohost.
ServerA : Apps and data
ServerB : Backups
There are a user "userA" on "ServerB" to use borg serve and receive backups. This user can't use borg so the backup failed.
Context
Steps to reproduce
For example, if I try to see if I am concerned by CVE-2023-36811 :
But it's the same if I am connected on serverB with userA and try to execute "borg" :
Expected behavior
userA on serverB must access to borg.
Logs
Logs said :
I also write about this problem on the forum : https://forum.yunohost.org/t/borg-borg-pas-dans-le-path/30520
Thanks in advance.
The text was updated successfully, but these errors were encountered: