I am running a UrBackup server as an app on TrueNAS. I found the log file! It show this:
2025-03-25 12:24:18: WARNING: Upgrading database to version 68
2025-03-25 12:24:18: WARNING: Done.
2025-03-25 12:24:18: Deleting database journal...
2025-03-25 12:24:18: Copying/reflinking database...
2025-03-25 12:24:18: Reflink ioctl failed. errno=11
2025-03-25 12:24:18: WARNING: Creating file entry index. This might take a while
...
2025-03-25 12:24:18: Getting number of files...
2025-03-25 12:24:18: Dropping index...
2025-03-25 12:24:18: Starting creating files index...
2025-03-25 12:24:18: Creating backupid index...
2025-03-25 12:24:18: Syncing...
2025-03-25 12:24:18: Renaming back result...
2025-03-25 12:24:18: SQLite: recovered 1 frames from WAL file /var/urbackup/back
up_server.db-wal code: 283
2025-03-25 12:24:18: SQLite: recovered 2 frames from WAL file /var/urbackup/back
up_server_settings.db-wal code: 283
2025-03-25 12:24:18: Started UrBackup...
2025-03-25 12:24:18: Removing temporary files...
2025-03-25 12:24:18: Recreating temporary folder...
2025-03-25 12:24:18: Image mounting disabled: Cannot become root user
2025-03-25 12:24:18: Backup destination cannot handle subvolumes and snapshots.
Snapshots disabled.
2025-03-25 12:24:18: Reflink ioctl failed. errno=11
2025-03-25 12:24:18: Broadcasting on ipv4 interface eth0 addr 172.16.1.2
2025-03-25 12:24:19: InternetService: Server started up successfully!
There are more problems here, although I don’t know how serious they are. Cannot become root user? Is this the reason my backups don’t start?
I am staggering around a pitch-black room right now and am willing to start with the smallest of a hint of light.
I know nothing about TrueNAS so I can not be of much help but…
The app installation determined the 172.16.1.2 address and UrBackup then broadcasts on the address it has been given.
UrBackup seems to be running on a VM under some form of virtualisation, KVM, docker or whatever TrueNAS uses. I expect eth0 is a virtual interface to an internal bridge network that connects to the physical network via NAT. This method of connection blocks much of the network traffic used by UrBackup and requires ports to be opened to work. I think this is why broadcasts are blocked as they are local to the internal bridge network.
The network setup is a function of the TrueNAS VM settings rather than a function of UrBackup. I had a quick look at the TrueNAS documentation for UrBackup and saw nothing useful. They do have information on networking in general.
This is all determined by the networking setup configured during installation. I did a quick forum search and found Install UrBackup Server on Truenas Scale ElectricEel-24.10.0.2. Following this would create the kind of setup I suspect you have.
Another post, Install UrBackup Server on Truenas Scale, seems closer to what you expect.
The current setup treats your LAN as a WAN and you would use an internet setup for UrBackup. This should work provided you have opened the ports needed by UrBackup as given by the first post.
The second posts gives UrBackup a direct connection to your LAN and allow the server to detect local clients.
To get something better than my guesswork you would need to post more of your app installation details.
1 Like
Thanks very much! This does look like it is the answer. I am totally new to containerized virtualization. I will try this working on this again, when I have a chance.