Hi,
I’m running UrBackup Server 2.5.38 on Ubuntu 26.04, installed from the official UrBackup OBS repository:
urbackup-server 2.5.38.0-1
origin: obs://build.opensuse.org/home:uroni/xUbuntu_26.04
I’ve encountered two potentially related issues.
1. Large file backup loses progress after server restart
I’m currently running a huge file backup involving approximately 2 TB of data.
UrBackup was in the middle of the file-linking phase, which takes a considerable amount of time.
Unfortunately, on October 23, 2026, the UrBackup service was automatically restarted during Ubuntu’s unattended upgrades.
After the restart, UrBackup appeared to start the linking process from scratch, rather than continuing where it left off.
This is particularly problematic for very large backups, where repeating the linking process can waste many days of processing.
2. Crashes during system maintenance
I’ve also observed two crashes associated with automatic system maintenance.
October 15, 2026 - SIGSEGV
Ubuntu Apport captured the following crash:
ProblemType: Crash
Date: Thu Oct 15 06:29:31 2026
ExecutablePath: /usr/bin/urbackupsrv
Package: urbackup-server 2.5.38.0-1
Signal: 11
This occurred during the same time window as Ubuntu’s automatic package upgrades.
I still have the 184 MB Apport crash report if it would be useful for debugging.
October 23, 2026 - General protection fault
During unattended upgrades of zlib1g and zlib1g-dev, the following events occurred:
06:54:49 systemd: Reexecution requested
by systemctl (apt-daily-upgrade.service)
06:54:59 systemd: Stopping urbackupsrv.service
06:54:59 kernel: traps: urbackupsrv[3730188]
general protection fault
error:0 in urbackupsrv
06:55:23 systemd: urbackupsrv.service:
Deactivated successfully
06:55:23 systemd: Stopped urbackupsrv.service
06:55:23 systemd: Starting urbackupsrv.service
06:55:23 systemd: Started urbackupsrv.service
The server itself was not rebooted, and the UrBackup package was not updated.
Multiple system services were restarted during this maintenance operation.
Although the UrBackup restart was initiated by system maintenance rather than the crash, the general protection fault occurred during the shutdown sequence.
I’m wondering whether this indicates a bug in UrBackup’s shutdown handling.
Thanks!