Server 2.4.2 beta/Client 2.4.0 beta

Here are some initial FreeBSD ports/packages for the server-2.4.2 and client-2.4.1.0 betas. They both launch in a 12.0-RELEASE jail that has both ipv4 and ipv6 addresses, and I can reach the web interface for the server via both the ipv4 and ipv6 addresses.

Server Port: https://github.com/kcoombs/archivers-urbackup-server/archive/2.4.2-beta.zip
Server Package: https://github.com/kcoombs/archivers-urbackup-server/releases/download/2.4.2-beta/urbackup-server-2.4.2.txz

Client Port: https://github.com/kcoombs/archivers-urbackup-client/archive/2.4.1.0-beta.zip
Client Package (no GUI): https://github.com/kcoombs/archivers-urbackup-client/releases/download/2.4.1.0-beta/urbackup-client-2.4.1.0.txz

IPv6 is more functional, but not completely yet. I think a client issue.

I can use the administration interface over IPv6 and add hosts and everything. The URL and hostname-checks do not allow IPv6-addresses yet.

When installing a client with and internet hostname via /etc/hosts with only an IPv6 address, the client is unable to connect, although the server is listening on the IPv6 socket.

2019-06-17 11:33:29: SQLite: recovered 25 frames from WAL file /usr/local/var/urbackup/backup_client.db-wal code: 283
2019-06-17 11:33:29: urbackupserver: Server started up successfully!
2019-06-17 11:33:29: FileSrv: Server started up successfully
2019-06-17 11:33:29: Started UrBackupClient Backend...
2019-06-17 11:33:30: Looking for old Sessions... 0 sessions
2019-06-17 11:33:30: Final path: /tmp
2019-06-17 11:33:31: Trying to connect to internet server "urbackuptest.tuxis.net" at port 55415
2019-06-17 11:33:31: Socket has error: 111
2019-06-17 11:33:31: Connecting failed.
2019-06-17 11:38:30: Trying to connect to internet server "urbackuptest.tuxis.net" at port 55415
2019-06-17 11:38:31: Socket has error: 111
2019-06-17 11:38:31: Connecting failed. 

Telnet does work

# telnet urbackuptest.tuxis.net 55415
Trying 2a03:7900:1:1:6c2c:2529:bd2:4afe...
Connected to urbackuptest.tuxis.net.
Escape character is '^]'.
Zs2� etc etc etc

So something seems to be wrong with the client?

Have tried through 2.4.2 update but still getting timeout (2) errors preventing file and image backups on several sets, so have rolled back to 2.3.8 and backups running well again, even with 2.4.0 clients. Will try again later in development cycle.

Windows Server 2008 r2 with Windows 7 Pro clients on AD domain.

Tried 2.4.2 server again on FreeNAS. Compiled fine. Backups from clients work fine but GUI is not accessible through usual IPV4 address. Again : any clue ?

Error log :
Starting HTTP-Server on port 55414
ERROR: HTTP: Failed binding socket to port 55414. Another instance of this application may already be active and bound to this port.

No other instance is running when looking at '‘top’.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.