Job timed out — running for over 24 hours with no recent progress.

[petrhud]

Hello,

I have a backup that is large and takes more than 24 hours. The backup is interrupted with the message: Job timed out — running for over 24 hours with no recent progress.
Is there any way to resolve this situation?

Thank you, Petr

[marcpope]

Hi @petrhud,

The 24-hour limit isn't a hard wall — it's a safety net that catches "zombie" jobs. A job is only auto-failed when both conditions are true:

1. The job has been in the system for over 24 hours
2. No progress has been reported in the last 60 minutes

So a backup that runs for 30+ hours but keeps sending progress updates will not be killed. The agent sends progress updates to the server every ~10 seconds during
a borg backup.

A few things to check:

• Agent version — Make sure your agent is on the latest version (v2.17.6). Older versions may not send progress updates correctly. You can check in the web UI on
  the client detail page, or trigger an update from Settings → Updates.
• Single large files — If your backup includes very large individual files (e.g., database dumps, VM images), borg may not emit progress events while processing a
  single file. If one file takes over 60 minutes to transfer, the server thinks the job is stalled.
• Network issues — If progress reports can't reach the server (intermittent connectivity), the server won't see activity even though the backup is running fine.

If the issue is that your backup legitimately runs for a long time with periods of no progress, let me know — I can look into making the timeout configurable in
Settings.

[petrhud]

Everything is up to date. The agents on the servers are running the latest version. About 200,000 JPEG, DOCX, and XLSX files are being copied. Mostly office files. I can see the progress of the copy. The information about the files being copied keeps changing. But as soon as the job runs for more than 24 hours, it terminates with an error.

[petrhud]

I tried again, but again after 24 hours the backup was turned off. I am attaching screenshots of the operation. It can be seen that the data is still increasing. I tried to start the job that crashed again. But it still stops and does nothing. I tried restarting both the server and the client, but nothing helps.

[marcpope]

@petrhud This has been identified as a timezone bug and fixed — see #51 for details. The fix will be in v2.18.0. Your backups should no longer be killed at the 24-hour mark.

[marcpope]

@petrhud The pip3 error on FreeBSD is fixed — the borg updater now supports FreeBSD's pkg package manager (pkg install borgbackup) and falls back from pip3 to pip when pip3 doesn't exist. Fix will be in v2.18.0.

In the meantime, you can install borg manually: pkg install borgbackup