Error Backup to NAS via SMB

Support
1

good morning, friends,

we created backup-to-NAS (SMB-Share) some month ago and it was all OK, but:

… since days we get a message that all backups are failed ! That’s why we tried to repair the backup config → no succes. Now we deleted backup config and reconfigured it, and we get this mystery message:

Error: no container with name or ID “rclone-gateway” found: no such container

node 6: no_read_permission on destination fb17dc53-b435-5b15-af13-26c381f70d07 (code=125)

What does this mean ?? What should we do ??

2

Please check if the rclone-gateway container is running:

[root@node1 ~]# podman ps
CONTAINER ID  IMAGE                                               COMMAND               CREATED             STATUS             PORTS       NAMES
...
936aedfef7be  ghcr.io/nethserver/rclone:3.20.0                                          About a minute ago  Up About a minute              rclone-gateway
...

If it’s not running you could try to start it:

systemctl start rclone-gateway
3

OK!

That’s the results:

[root@NETH tux]# podman ps
CONTAINER ID  IMAGE                                               COMMAND               CREATED       STATUS       PORTS       NAMES
0f814c893925  docker.io/crowdsecurity/crowdsec:v1.7.8-debian                            2 days ago    Up 2 days                crowdsec4
015bc99a8683  ghcr.io/nethserver/crowdsec-firewall-bouncer:1.1.7  /usr/local/bin/cr...  2 days ago    Up 2 days                crowdsec4-firewall-bouncer
64d2a2e7d265  ghcr.io/nethserver/redis:3.20.0                     redis-server /dat...  10 hours ago  Up 10 hours  6379/tcp    redis
55d97a3ab340  quay.io/prometheus/node-exporter:v1.10.2            --collector.cpu.i...  10 hours ago  Up 10 hours  9100/tcp    node_exporter
b21e6b54c6bc  docker.io/grafana/alloy:v1.11.3                     run /etc/alloy/co...  10 hours ago  Up 10 hours              promtail
[root@NETH tux]# systemctl start rclone-gateway
Job for rclone-gateway.service failed because the control process exited with error code.
See "systemctl status rclone-gateway.service" and "journalctl -xeu rclone-gateway.service" for details.
[root@NETH tux]# systemctl status rclone-gateway
× rclone-gateway.service - Rclone Gateway server
     Loaded: loaded (/etc/systemd/system/rclone-gateway.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Tue 2026-06-30 11:34:20 CEST; 22s ago
    Process: 2322215 ExecStartPre=/bin/rm -f /run/rclone-gateway.pid /run/rclone-gateway.cid (code=>
    Process: 2322216 ExecStartPre=mkdir -vp rclone haproxy (code=exited, status=0/SUCCESS)
    Process: 2322217 ExecStartPre=runagent -m node rclonegwctl write-configuration --rclonedir=rclo>
    Process: 2322218 ExecStart=/usr/bin/podman run --conmon-pidfile=/run/rclone-gateway.pid --cidfi>
    Process: 2322234 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/rclone-gateway.cid >
        CPU: 551ms

Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Scheduled restart job, restart counter is >
Jun 30 11:34:20 NETH systemd[1]: Stopped Rclone Gateway server.
Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Start request repeated too quickly.
Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Failed with result 'exit-code'.
Jun 30 11:34:20 NETH systemd[1]: Failed to start Rclone Gateway server.
lines 1-15/15 (END)
[root@NETH tux]# 

journalctl -xeu rclone-gateway.service

Support: https://wiki.rockylinux.org/rocky/support
░░ 
░░ Automatic restarting of the unit rclone-gateway.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 30 11:34:20 NETH systemd[1]: Stopped Rclone Gateway server.
░░ Subject: A stop job for unit rclone-gateway.service has finished
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░ 
░░ A stop job for unit rclone-gateway.service has finished.
░░ 
░░ The job identifier is 25829 and the job result is done.
Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Start request repeated too quickly.
Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░ 
░░ The unit rclone-gateway.service has entered the 'failed' state with result 'exit-code'.
Jun 30 11:34:20 NETH systemd[1]: Failed to start Rclone Gateway server.
░░ Subject: A start job for unit rclone-gateway.service has failed
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░ 
░░ A start job for unit rclone-gateway.service has finished with a failure.
░░ 
░░ The job identifier is 25829 and the job result is failed.
4

It seems some of the lines are not fully displayed, there’s just a “>”.

Please use the following command to show the full output:

systemctl status rclone-gateway --no-pager

Please also check the logs for errors.

5

OK That’s it says:

[root@NETH tux]# systemctl status rclone-gateway --no-pager -l
× rclone-gateway.service - Rclone Gateway server
     Loaded: loaded (/etc/systemd/system/rclone-gateway.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Tue 2026-06-30 11:34:20 CEST; 51min ago
    Process: 2322215 ExecStartPre=/bin/rm -f /run/rclone-gateway.pid /run/rclone-gateway.cid (code=exited, status=0/SUCCESS)
    Process: 2322216 ExecStartPre=mkdir -vp rclone haproxy (code=exited, status=0/SUCCESS)
    Process: 2322217 ExecStartPre=runagent -m node rclonegwctl write-configuration --rclonedir=rclone --haproxydir=haproxy (code=exited, status=0/SUCCESS)
    Process: 2322218 ExecStart=/usr/bin/podman run --conmon-pidfile=/run/rclone-gateway.pid --cidfile=/run/rclone-gateway.cid --cgroups=no-conmon --detach --init --log-opt=tag=rclone-gateway --replace --name=rclone-gateway --network=host --volume=./rclone:/etc/rclone:ro,Z --volume=./haproxy:/etc/haproxy:ro,Z --volume=${BACKUP_VOLUME}:/srv/repo:z --volume=/dev/log:/dev/log --volume=rclone-cache:/var/cache/rclone:z --entrypoint=rclone-gateway-entrypoint.sh --env-file=rclone-gateway.env ${RCLONE_IMAGE} (code=exited, status=126)
    Process: 2322234 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/rclone-gateway.cid (code=exited, status=0/SUCCESS)
        CPU: 551ms

Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Scheduled restart job, restart counter is at 3.
Jun 30 11:34:20 NETH systemd[1]: Stopped Rclone Gateway server.
Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Start request repeated too quickly.
Jun 30 11:34:20 NETH systemd[1]: rclone-gateway.service: Failed with result 'exit-code'.
Jun 30 11:34:20 NETH systemd[1]: Failed to start Rclone Gateway server.
6

This seems to be the error:

Is there still a customized volume from local storage backup?

cat /var/lib/nethserver/node/state/rclone-webdav.env

If yes, please remove it and try to start the service again.

7

That was It !! Problem solved !

Before backup to NAS we backed up to USB-HD - that’s why exists rclone-webdav.env

But this was long time ago - why NOW the problems ??

Thank you very much - mrmarkuz !!

Just another question: Why is there no email from BACKUP-Tool possible ? - no one see the backup-problems - only if admin login Nethserver-site ….

But this is a new theme for new topic I think

1 Like
8

Core 3.20.0 introduced the new rclone-gateway, see Releases · NethServer/ns8-core · GitHub

There are existing feature requests and an issue (including a notification script) is already opened:

1 Like
9

Thanks Markus for the detailed response! Just to add a third option: to receive failed backup alerts, configure email notifications as described in Metrics and alerts | NethServer 8 documentation.

1 Like