How to get Truenas to relinquish port 55414

[eewiz]

I have discovered that the truenas 12.0-U6 urbackup plugin is defective.
I have not been able to run urbackup installed into a hand made jail per the freenas urbackup install instructions.
So, I removed all jails.
I removed all concerned datasets.
I rebooted the truenas server.
I reinstalled per the freenas instructions.
Now, urbackup in the only jail in existence produces.
root@urbj:~ # urbackupsrv run
2021-10-31 00:26:29: Starting HTTP-Server on port 55414
2021-10-31 00:26:29: ERROR: HTTP: Failed binding socket to port 55414. Another instance of this application may already be active and bound to this port.
2021-10-31 00:26:29: Started UrBackup…
Backupfolder not set
2021-10-31 00:26:29: Image mounting disabled: Backupfolder not set
Backupfolder not set
2021-10-31 00:26:29: Backup destination cannot handle subvolumes and snapshots.Snapshots disabled.
2021-10-31 00:26:29: Error opening source file. errno=2
2021-10-31 00:26:29: ERROR: Binding UDP socket failed for interface epair0b
2021-10-31 00:26:29: Broadcasting on ipv4 interface epair0b addr 172.16.0.2
2021-10-31 00:26:29: UrBackup Server start up complete.
2021-10-31 00:26:29: ERROR: Failed binding SOCKET to Port 55413
2021-10-31 00:26:29: Looking for old Sessions… 0 sessions
2021-10-31 00:26:29: ERROR: Error while starting listening to ports. Stopping server.
2021-10-31 00:26:29: Exited Loop
2021-10-31 00:26:29: Deleting at…
2021-10-31 00:26:29: Deleting SelectThreads…
2021-10-31 00:26:29: Deleting lbs…
2021-10-31 00:26:29: Shutting down plugins…
2021-10-31 00:26:29: Deleting server…
root@urbj:~ #

I don’t know how to get treunas to relinquish port 55414.
Can someone help me please.

Thank You

 

[Alecmascot]

I have discovered that the truenas 12.0-U6 urbackup plugin is defective.
I have not been able to run urbackup installed into a hand made jail per the freenas urbackup install instructions.
So, I removed all jails.
I removed all concerned datasets.
I rebooted the truenas server.
I reinstalled per the freenas instructions.
Now, urbackup in the only jail in existence produces.
root@urbj:~ # urbackupsrv run
2021-10-31 00:26:29: Starting HTTP-Server on port 55414
2021-10-31 00:26:29: ERROR: HTTP: Failed binding socket to port 55414. Another instance of this application may already be active and bound to this port.
2021-10-31 00:26:29: Started UrBackup…
Backupfolder not set
2021-10-31 00:26:29: Image mounting disabled: Backupfolder not set
Backupfolder not set
2021-10-31 00:26:29: Backup destination cannot handle subvolumes and snapshots.Snapshots disabled.
2021-10-31 00:26:29: Error opening source file. errno=2
2021-10-31 00:26:29: ERROR: Binding UDP socket failed for interface epair0b
2021-10-31 00:26:29: Broadcasting on ipv4 interface epair0b addr 172.16.0.2
2021-10-31 00:26:29: UrBackup Server start up complete.
2021-10-31 00:26:29: ERROR: Failed binding SOCKET to Port 55413
2021-10-31 00:26:29: Looking for old Sessions… 0 sessions
2021-10-31 00:26:29: ERROR: Error while starting listening to ports. Stopping server.
2021-10-31 00:26:29: Exited Loop
2021-10-31 00:26:29: Deleting at…
2021-10-31 00:26:29: Deleting SelectThreads…
2021-10-31 00:26:29: Deleting lbs…
2021-10-31 00:26:29: Shutting down plugins…
2021-10-31 00:26:29: Deleting server…
root@urbj:~ #

I don’t know how to get treunas to relinquish port 55414.
Can someone help me please.

Thank You

That is not what is happening.
You are starting urbackupsrv without stopping the current running instance.
End the current instance usuing "kill processid". Get process id from "top"

 

[eewiz]

I’m sorry, I assumed that if the program was running, trying to run it again would produce some kind of output resembling “I am already running” but I appear to mistaken.
The reason I was in the console to begin with was because urbackup was not answering at 55414.
It appeared to me that the program was not running.
It could have failed to autostart on boot the same as my manual run did, all for the same port issue.

Although, I did get it working.
I nuked everything again, including the associated dataset.
I created a new dataset named urb.
To keep Urbackup from complaining about case insensitive storage, I have learned to not change the dataset’s “Share Type” to “SMB”, I leave it set on “Generic”.
I created a new jail named urbj with one crucial change.
I picked DHCP during creation instead of NAT.
I started the jail and there appeared IP .161 in my routers DHCP table.
Then a quick DHCP reservation to set urbj’s IP address from .161 DHCP to .15 reserved.
I restart the jail and it picks up the .15 address.
I shell into the jail and run the commands to install Urbackup.
I go http://…15:55414 and POW there’s Urbackup.
I transfer the security code to the client’s server_idents files and restart the clients.
By the time I get back to Urbackup all three clients are found and backing up.
That’s the way it’s supposed to work.

The only thing I have done differently now, this fifth time, is forget using plugins and make my own jail while selecting DHCP, not NAT when creating the jail.
Whether I would get a jail via installing the plugin which defaults to “NAT” or create a jail directly with “NAT” selected, the main log would start pouring out this kind of ooze.
Oct 31 01:54:56 plum kernel: epair0a: Ethernet address: 02:45:7e:94:54:0a
Oct 31 01:54:56 plum kernel: epair0b: Ethernet address: 02:45:7e:94:54:0b
Oct 31 01:54:56 plum kernel: epair0a: link state changed to UP
Oct 31 01:54:56 plum kernel: epair0b: link state changed to UP
Oct 31 01:54:56 plum kernel: epair0a: changing name to ‘vnet0.1’
Oct 31 01:55:00 plum kernel: em0: link state changed to DOWN
Oct 31 01:55:03 plum kernel: em0: link state changed to UP
Oct 31 01:55:06 plum kernel: lo0: link state changed to UP


Oct 31 02:05:55 plum kernel: vnet0.1: link state changed to DOWN
Oct 31 02:05:55 plum kernel: epair0b: link state changed to DOWN
Oct 31 02:05:55 plum kernel: in6_purgeaddr: err=65, destination address delete failed


Oct 31 02:06:53 plum kernel: epair0a: Ethernet address: 02:94:ca:9f:80:0a
Oct 31 02:06:53 plum kernel: epair0b: Ethernet address: 02:94:ca:9f:80:0b
Oct 31 02:06:53 plum kernel: epair0a: link state changed to UP
Oct 31 02:06:53 plum kernel: epair0b: link state changed to UP
Oct 31 02:06:53 plum kernel: epair0a: changing name to ‘vnet0.2’
Oct 31 02:06:53 plum kernel: lo0: link state changed to UP
Oct 31 02:08:16 plum kernel: vnet0.2: link state changed to DOWN
Oct 31 02:08:16 plum kernel: epair0b: link state changed to DOWN
Oct 31 02:08:17 plum kernel: in6_purgeaddr: err=65, destination address delete failed


Oct 31 02:08:35 plum kernel: epair0a: Ethernet address: 02:66:9d:2e:58:0a
Oct 31 02:08:35 plum kernel: epair0b: Ethernet address: 02:66:9d:2e:58:0b
Oct 31 02:08:35 plum kernel: epair0a: link state changed to UP
Oct 31 02:08:35 plum kernel: epair0b: link state changed to UP
Oct 31 02:08:35 plum kernel: epair0a: changing name to ‘vnet0.3’
Oct 31 02:08:35 plum kernel: lo0: link state changed to UP
Oct 31 02:09:21 plum kernel: vnet0.3: link state changed to DOWN
Oct 31 02:09:21 plum kernel: epair0b: link state changed to DOWN
Oct 31 02:09:40 plum kernel: in6_purgeaddr: err=65, destination address delete failed


Now that I have nuked it all and created a first jail with DHCP selected, the log is quiet, no more ooze.
So far, Urbackup works like it should at the expense of one local IP address.
I guess NAT just doesn't work for me.

All for now

 

[Alecmascot]

NAT is definitely not required.
you do not need to share the urbackup dataset in any way.
It is mounted inside the jail to /mnt/yourname and referenced like that in Urbackup Settings:Backup storage path.

 

[eewiz]

The choice of NAT or DHCP is for the jail urbackup runs in not the urbackup dataset.
Without NAT or DHCP so the jail can get an IP address, urbackup will sit in a black hole with no way to reach clients on the outside.
I understand all of the protocols involved and how they should work.
What I don't understand is how to troubleshoot a linux/unix type system when those protocols don't work.
Or when the urbackup plugin just stops working after a few days.
Also to be clear.
The urbackup dataset may be shared by any or multiple protocols at the same time.
The dataset has to be created "Generic" because urbackup expects case sensitive storage.
Aside from that, you may share that dataset with any of the sharing tools available.
The dataset may be shared via NFS for some clients as well as shared via SMB for the windows folks.
Although, the windows folks may get confused because the share will be case sensitive.

All for now