I already did
chown root:root /etc/sudoers.d/borg
As mentioned here: [Borg & Borg Server] Deduplicated, encrypted and remote backups - #77 by Melchisedech
But I still get the same error logs from the service which is weird?
EDIT: had to do chown twice for it to stick, and then yunohost webadmin froze while restarting the borg service.
Apparently no action on the borg server, so I guess it’s not backing up.
Rebooted after a while. Error logs:
Could not restart the service 'borg'
Recent service logs:-- Logs begin at Wed 2022-01-05 09:35:25 WET, end at Wed 2022-01-05 10:31:35 WET. -- Jan 05 09:58:41 systemd[1]: Starting Run backup borg... Jan 05 09:58:41 sudo[2362]: borg : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/bin/backup-with-borg borg Jan 05 09:58:41 sudo[2362]: pam_unix(sudo:session): session opened for user root by (uid=0) Jan 05 09:58:41 sudo[2371]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/yunohost app setting borg last_run -v 220105_0958 Jan 05 09:58:41 sudo[2371]: pam_unix(sudo:session): session opened for user root by (uid=0) Jan 05 09:58:57 sudo[2362]: Another YunoHost command is running right now, we are waiting for it to finish before running this one Jan 05 09:59:42 sudo[2362]: Still waiting... Jan 05 10:02:43 sudo[2362]: Still waiting... Jan 05 10:14:43 sudo[2362]: Still waiting... Jan 05 10:31:35 sudo[2371]: pam_unix(sudo:session): session closed for user root Jan 05 10:31:35 sudo[2362]: pam_unix(sudo:session): session closed for user root Jan 05 10:31:35 systemd[1]: borg.service: Main process exited, code=killed, status=15/TERM Jan 05 10:31:35 systemd[1]: borg.service: Failed with result 'signal'. Jan 05 10:31:35 systemd[1]: Stopped Run backup borg.
I don’t know how to trigger the borg back up manually. The service is up but repository not created yet. Will wait until cron does his thing at midnight. Maybe pumpkin pie tomorrow?