Not sure when it started happening, but for the last couple of months there’s always a failure of one or more of the apps in my nightly backup. Virtually all the time it’s just a single app that fails, but occasionally more than one do. It’s mainly Samba that is the one that fails, but I have seen others fail instead.
If I do a “Backup now” during the day, most (but not quite all) of the time it will back all the apps (7 in total) normally.
I’m backing up to an SMB share on a TrueNAS system. I’ve checked the resource usage on both the ESXi host and the TrueNAS system at the times of failure and both systems are hardly stressed at all, so I can’t see a reason for the daily failures.
The error is always:
2025-02-24T01:03:14-08:00 [1:samba1:backup5] Fatal: unable to open repository at rclone::smb:Backup/NS8Backup/samba/b9eb16a3-a126-4c92-98e9-4bebd7754b3e: error talking HTTP to rclone: Get "http://localhost/file-1789313249346347679": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Is there anything else I can check to see what’s going on to cause this many fails.
Here is a similar error, the backup destination couldn’t be reached:
Could it be that the NS8 backup of samba can’t access the NAS because the NAS can’t access samba on NS8 to check users/permissions?
Maybe test the backup on a guest writable share on the NAS?
Another idea:
Do all the timeouts occur after the same time?
Maybe we can use some timeout option like --contimeout=TIME, see also Documentation
If it was failing on all the backups, then maybe. But when 6 of the 7 backups work correctly, can’t see it being this. If it was some kind of Catch-22 in Samba, then I’d expect the issue to be always that Samba fails, but it’s not. About 5% of the time it’s a different module.
If you mean is the backup run at the same time every day, then yes. But again, normally it’s only 1 out of 7 that fail.
If you mean how long after the backup starts do I see that message, then yes it’s fairly consistent at about 2 → 3 minutes.