NS8-Guacamole - first testing prerelease

not sure yet if a real problem with the module or just noise (problem elsewhere)…

After adding guacamole instance to an existing backup schedule (with an app already in the backup repo), a manual run of the backup fails:

Task module/guacamole1/run-backup run failed: {‘output’: ‘’, ‘error’: ‘Job for backup3.service failed because the control process exited with error code.\nSee “systemctl --user status backup3.service” and “journalctl --user -xeu backup3.service” for details.\n’, ‘exit_code’: 1}
1

Job for backup3.service failed because the control process exited with error code.
See “systemctl --user status backup3.service” and “journalctl --user -xeu backup3.service” for details.

But don’t know where to find the backup3.service, so no further information. Maybe I’ve to check with the userid instead of the name…

Tested with 2 VM. The latter with latest core dev updates, the former I don’t recall.

On empty backup repo with no previous app schedule, it works.

Won’t be able to test again maybe till night.

EDIT (log file showed):

024-04-09T15:52:18+02:00 [1:guacamole1:backup3] Fatal: wrong password or no key found
2024-04-09T15:52:18+02:00 [1:guacamole1:backup3] Initializing repository 86d1a8ac-ef89-557a-8e19-8582ab86b7c4
2024-04-09T15:52:18+02:00 [1:guacamole1:backup3] restic init
2024-04-09T15:52:18+02:00 [1:samba1:backup3]    adding backup private/sam.ldb.d/CN=CONFIGURATION,DC=AD,DC=NS8,DC=TEST.ldb.bak-offline to tar and deleting file
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3] Fatal: create repository at rclone::webdav:/guacamole/08315f8c-a074-4963-9dfb-f035195ea138 failed: Fatal: config file already exists
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3] Traceback (most recent call last):
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3]   File "/usr/local/agent/bin/module-backup", line 105, in <module>
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3]     agent.run_restic(rdb, repository, repopath, [], ["init"]).check_returncode()
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3]   File "/usr/lib64/python3.11/subprocess.py", line 502, in check_returncode
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3]     raise CalledProcessError(self.returncode, self.args, self.stdout,
2024-04-09T15:52:19+02:00 [1:guacamole1:backup3] subprocess.CalledProcessError: Command '['podman', 'run', '-i', '--rm', '--name=restic-guacamole1-3599', '--privileged', '--network=host', '--volume=restic-cache:/var/cache/restic', '--log-driver=none', '-e', 'RESTIC_PASSWORD', '-e', 'RESTIC_CACHE_DIR', '-e', 'RESTIC_REPOSITORY', '-e', 'RCLONE_WEBDAV_URL', 'ghcr.io/nethserver/restic:2.7.0-dev.1', 'init']' returned non-zero exit status 1.
2024-04-09T15:52:19+02:00 [1:guacamole1:systemd] backup3.service: Main process exited, code=exited, status=1/FAILURE
2024-04-09T15:52:19+02:00 [1:guacamole1:systemd] backup3.service: Failed with result 'exit-code'.
2024-04-09T15:52:19+02:00 [1:guacamole1:agent@guacamole1] Job for backup3.service failed because the control process exited with error code.
2024-04-09T15:52:19+02:00 [1:guacamole1:agent@guacamole1] See "systemctl --user status backup3.service" and "journalctl --user -xeu backup3.service" for details.
3 Likes

Thanks for testing!
I can’t reproduce the issue.
I tested adding guacamole to an already scheduled backup on following setups:

  • Stable Core, Rocky, SMB
  • Testing Core, Rocky, SMB
  • Stable Core, Debian, B2
1 Like

BTW:

Guacamole (without AD in this use case) worked out of the box (once I changed the AD name from the earlier used NetBIOS name to the ad.domain.tld version in the connectiions area…

:slight_smile:

Great workl!

My 2 cents
Andy

1 Like

Thanks for testing!
I’m going to move the post to the guacamole app thread.
EDIT: Done.

1 Like