No documentation for BackupPC

BackupPC is available via the Nethforge repository but there is no mention of it in the NS8 manual.

The main setting is for a FQDN, which if I put my NS8 instance as I only have a single Node, when I select “Open backuppc” it gives a “Bad gateway” error.

Cheers.

Indeed no official documentation as such, but maybe this helps:
https://wiki.nethserver.org/doku.php?id=ns8:applications:backuppc

Not really.

Cheers.

Salut @EddieA,

I wrote a document for BackuPC for SME in 2018 and updated it in 2019 for NethServer. I updated again it in july 2023 but never publish it since NS8 was coming out.

The idea of stephdl for the creation of the first module of BackupPC for NethServer was taken from the 2019 document:
https://www.micronator.org/affaires/produit/nethserver-101-cahier-11backuppc/.

I am still using the 2019 version for NethServer-7.9 and in last July, after a disaster, I recuperated using it (aroung 60GB). I just had to install a fresh NethServer-7.9, update it and restore with BackupPC. No need to install all the applications before the restoration.

I do not know if it will work with NS8 but the descriptions of the parameters for the configuration of BackupPC should be the same.

Michel-André

The configuration page for NS8 is fairly straightforward:
image

All I’m looking for is what to put as the FQDN. If I put my NS8 single node instance name, then when I click this:
image

I get this:
image

Or do I have to set up a BackupPC server, in which case there doesn’t seen any point in having this app on NS8.

Cheers.

Does tha fqdn is resolvable from your client and from the server

Can you catch the log after you have saving the settings

We need to understand and for this we need logs

I only have a single NS8 instance: NS8. This is reachable, via either just the hostname or the FQDN throughout my internal network:

image

2024-09-25T13:30:49-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/4f0c0c2b-8764-4595-b270-95766ce3c613: get-name/50get_name is starting
2024-09-25T13:30:49-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/6cc8712e-fa37-420d-a99c-36b20d42a2cb: get-configuration/20read is starting
2024-09-25T13:30:49-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/0ac26b9a-2dd2-4a1c-8372-8786e84307e4: get-status/20read is starting
2024-09-25T13:30:50-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/4f0c0c2b-8764-4595-b270-95766ce3c613: action “get-name” status is “completed” (0) at step 50get_name
2024-09-25T13:30:51-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/6cc8712e-fa37-420d-a99c-36b20d42a2cb: action “get-configuration” status is “completed” (0) at step validate-output.json
2024-09-25T13:30:51-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/0ac26b9a-2dd2-4a1c-8372-8786e84307e4: action “get-status” status is “completed” (0) at step validate-output.json
2024-09-25T13:30:51-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/59c94cf6-d5e1-4e48-8630-98fa3c170ccc: get-configuration/20read is starting
2024-09-25T13:30:52-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/59c94cf6-d5e1-4e48-8630-98fa3c170ccc: action “get-configuration” status is “completed” (0) at step validate-output.json
2024-09-25T13:30:55-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/7507becd-8d2d-471f-87de-b5720c6aaa48: configure-module/01Hostname_validation is starting
2024-09-25T13:30:55-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/7507becd-8d2d-471f-87de-b5720c6aaa48: configure-module/10configure_environment_vars is starting
2024-09-25T13:30:56-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/7507becd-8d2d-471f-87de-b5720c6aaa48: configure-module/20configure_traefik is starting
2024-09-25T13:30:56-07:00 [1:backuppc1:agent@backuppc1] dump_env() is deprecated and implemented as a no-op
2024-09-25T13:30:59-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/7507becd-8d2d-471f-87de-b5720c6aaa48: configure-module/80start_services is starting
2024-09-25T13:30:59-07:00 [1:backuppc1:systemd] Reloading.
2024-09-25T13:30:59-07:00 [1:backuppc1:systemd] Stopping Podman backuppc-app.service…
2024-09-25T13:31:02-07:00 [1:backuppc1:systemd] libpod-5c5746a6841891409447af05587141543d54ef4b02e7c83a7e13b7aa58cfba93.scope: Consumed 1min 1.987s CPU time.
2024-09-25T13:31:03-07:00 [1:backuppc1:backuppc1] 5c5746a6841891409447af05587141543d54ef4b02e7c83a7e13b7aa58cfba93
2024-09-25T13:31:03-07:00 [1:backuppc1:backuppc1] 5c5746a6841891409447af05587141543d54ef4b02e7c83a7e13b7aa58cfba93
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Stopped Podman backuppc-app.service.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] backuppc-app.service: Consumed 1.755s CPU time.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Stopping Podman backuppc.service…
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Removed slice cgroup user-libpod_pod_9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5.slice.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] user-libpod_pod_9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5.slice: Consumed 1min 2.000s CPU time.
2024-09-25T13:31:03-07:00 [1:backuppc1:podman] 9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] user-libpod_pod_9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5.slice: Failed to open /run/user/1007/systemd/transient/user-libpod_pod_9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5.slice: No such file or directory
2024-09-25T13:31:03-07:00 [1:backuppc1:podman] Error: removing pod 9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5 cgroup: removing pod 9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5 cgroup: Unit user-libpod_pod_9971e43116f50fd815bab63c2aefc69dce07929c3dbfb628df54f86db4df79f5.slice not loaded.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] backuppc.service: Control process exited, code=exited, status=125/n/a
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] backuppc.service: Failed with result ‘exit-code’.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Stopped Podman backuppc.service.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] backuppc.service: Consumed 23.598s CPU time.
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Starting Podman backuppc.service…
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Created slice cgroup user-libpod_pod_d38d74ae995bf42cfd9d3aeb30d37cbe3455554ff57ff033dcf0a5f6dd2fef41.slice.
2024-09-25T13:31:03-07:00 [1:backuppc1:podman] d38d74ae995bf42cfd9d3aeb30d37cbe3455554ff57ff033dcf0a5f6dd2fef41
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Started libcrun container.
2024-09-25T13:31:03-07:00 [1:backuppc1:podman] d38d74ae995bf42cfd9d3aeb30d37cbe3455554ff57ff033dcf0a5f6dd2fef41
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Started Podman backuppc.service.
2024-09-25T13:31:03-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/7507becd-8d2d-471f-87de-b5720c6aaa48: action “configure-module” status is “completed” (0) at step 80start_services
2024-09-25T13:31:03-07:00 [1:backuppc1:systemd] Starting Podman backuppc-app.service…
2024-09-25T13:31:03-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/6447b24c-92cb-47fa-bb83-8ebabdc9bccc: get-configuration/20read is starting
2024-09-25T13:31:04-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/6447b24c-92cb-47fa-bb83-8ebabdc9bccc: action “get-configuration” status is “completed” (0) at step validate-output.json
2024-09-25T13:31:05-07:00 [1:backuppc1:systemd] Started libcrun container.
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc1] 538fd12b8e81921fb5c3ae69c6d1e454bb389fd5d3fb1e2f1d1f9fb450e7f17c
2024-09-25T13:31:05-07:00 [1:backuppc1:systemd] Started Podman backuppc-app.service.
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] ,—.
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] ,--------.,–. ,–. ,—. ,–. ,--------.| |
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] ‘–. .–’--',--.--. ,---. ,-| | ,---. / .-' | | '--. .--'| .' 2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] | | ,--.| .--'| .-. :' .-. | | .-. || -, | | | | | |
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] | | | || | \ --.\ -' | ' '-' '| .-' | |.--.| | –’
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] --' –‘--' ----’ ---' —’ --' –‘’–‘`–’ .–.
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] ‘–’
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] Image: tiredofit/backuppc | Version 6.0.4 Type ‘image_changelog’ for details
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] Repository/Documentation: GitHub - tiredofit/docker-backuppc: Docker web based enterprise backup software
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app]
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] If this image provides you value - Consider sponsoring my work for continued
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] development, timely updates, and feature requests. Commercial support available.
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app]
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] More Info: https://www.tiredofit.ca
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app]
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:05 e[100m[NOTICE]e[49m ** [monitoring] Container configured for monitoring with ‘zabbix modern’
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:05 e[100m[NOTICE]e[49m ** [scheduling] Container configured for scheduled tasks with ‘cron’
2024-09-25T13:31:05-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:05 e[100m[NOTICE]e[49m ** [messaging] Container configured to route mail via SMTP to ‘cleanmail’
2024-09-25T13:31:07-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:07 e[42m[INFO]e[49m ** [backuppc] BackupPC 4.4.0 initialization complete, now starting web server on port 80
2024-09-25T13:31:07-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:07 e[42m[STARTING]e[49m ** [nginx] [1] Starting nginx 1.26.0
2024-09-25T13:31:07-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:07 e[42m[STARTING]e[49m ** [fcgiwrap] [1] Starting fcgiwrap
2024-09-25T13:31:07-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:07 e[42m[STARTING]e[49m ** [monitoring] [1] Starting Zabbix Agent (modern) 6.4.15
2024-09-25T13:31:07-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:07 e[42m[STARTING]e[49m ** [scheduling] [1] Starting cron
2024-09-25T13:31:08-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:08 e[42m[STARTING]e[49m ** [backuppc] [1] Starting BackupPC 4.4.0
2024-09-25T13:31:10-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/9e9b6b0e-77ed-4428-a143-f24f02d6d891: get-status/20read is starting
2024-09-25T13:31:10-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/6364e062-c7c4-4f54-9478-5189c99d0e41: get-configuration/20read is starting
2024-09-25T13:31:11-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/6364e062-c7c4-4f54-9478-5189c99d0e41: action “get-configuration” status is “completed” (0) at step validate-output.json
2024-09-25T13:31:11-07:00 [1:backuppc1:agent@backuppc1] task/module/backuppc1/9e9b6b0e-77ed-4428-a143-f24f02d6d891: action “get-status” status is “completed” (0) at step validate-output.json

I see this in the log:

2024-09-25T13:31:07-07:00 [1:backuppc1:backuppc-app] 2024-09-25.20:31:07 e[42m[INFO]e[49m ** [backuppc] BackupPC 4.4.0 initialization complete, now starting web server on port 80

How does that work when the URL used to open BackupPC from the Status page is https. Changing the URL to http, I do get a sign-in box, but again, that leads me to the “Bad gateway” error.

I’ll also admit to not knowing anything about how traefik routes the request, as the Cluster Admin is also using port 80 (and 443).

Cheers.

Have you tried just using a different virtual host name (backuppc.bogolinux.net, bpc.ns8.bogolinux.net…) with proper DNS settings (resolvable), instead of your server’s main FQDN ?

2 Likes

That looks like it’s worked.

Cheers.

1 Like

I think this requirement (for most apps if not all) should be stated more clealy in the Nethserver documentation.

The differene/requirement (for an app) between the MAIN FQDN e.g. “mydomain.org” and a sub-domain e.g. “myapp.mydomain.org
Clearly one could argue that this could be considered basic knowledge, but as always, ‘assumption is the mother of all F***ups’.

Proven once again. Just saying… :wink:

2 Likes