Hi Martin,
I upgraded the server from a beta 1.3 version to the newly released 1.3 and for whatever reason the server identity changed. I replaced the identity in the server_idents.txt file on the clients but they still don’t see the new server. If I completely uninstall the client and reinstall, the clients never receive the configuration from the server either. The last relevant line from the log are:
2013-12-12 15:45:23: WARNING: Upgrading…
2013-12-12 15:45:23: WARNING: Converting database to journal mode…
2013-12-12 15:45:23: WARNING: Upgrading database to version 26
2013-12-12 15:45:23: WARNING: Upgrading database to version 27
2013-12-12 15:45:23: WARNING: Upgrading database to version 28
2013-12-12 15:45:23: WARNING: Done.
Can you switch the server into debug log level http://www.urbackup.org/Administration_Manual.php#x1-530008.2 and have another look at the log?
What OS are you using for client and server? Does the server and/or client have multiple network interfaces? Can you disable the firewall (if it is enabled) for testing purposes?
Does the server show the client on the detailed status screen?
I had since reinstalled the server and everything started working again. I think something must have gotten hung up in the upgrade considering the server ID changed. The server is a VM of Windows 2012 with 2 NICs, One is the network and one is for ISCSI connected to a SAN that holds the actual backup location. A server upgrade should keep the previous server identity, correct? Thanks for a really nice product by the way.
I used the Nullsoft installer. Funny enough I upgraded to the 1.3.1 today. The exe installer failed to stop the services (is it supposed too?) and the installation errored out. I manually stopped the 2 urbackup services that were running and restarted the upgrade and it finished. The Server Ident stayed the same this time but it seems to be doing the same thing as before now. The reason now I believe is one of the services is failing. I reinstalled over the top again this time now noticing the “urbackup server” service that calls UrBackupServer.exe is starting and stopping itself. The “urbackup windows server” service that calls urbackup_srv.exe is running. If I uninstall everything which files do I need to copy back in so the server has the same identity to present to the clients?
I found out the reason for the 2 services is the first installation for the beta i had used a msi installer and on this newest one I used the exe. The MSI installs a different service name and this is the reason the upgrade failed. I uninstalled urbackup with the msi and it removed the other service. Unfortunately with the reinstall I am still having the same problem of the clients not being recognized by the server. I have copied the 2 database files back in as well as the server_ident.key. I have uninstalled and reinstalled the client on a test machine but it still never gets the initial config from the server. TCPview shows urbackup sending UDP broadcast packets on 35623 and listening on 55414. The new client shows it listening for UDP on 35622 and TCP on 35623 and 35621.
Just keeping you updated, I uninstalled again and reinstalled a beta msi of server 1.3.1 I had downloaded on October 17. It immediately found all my clients (although they all said server rejected because of the server_ident key change). So something has changed in the newest version.
Hi.
Smth definitely changed. After upgrading to latest 1.3-1 version from 2013-12-15, i had to turn off network card responsible for one ISCSI path. It was in 192.168.144.X network. Some clients tried to respond to this address and they are configured in 192.168.2.X. There’s no communication between those two networks in my environment. I didn’t have this problem earlier. Client’s always responded to Communication network card of the server which is in 192.168.2.X address pool. On this 192.168.144.X network card only the IPv4 protocol is enabled, with unchecked “Register this connection’s addresses in DNS” option.
Hi. I’ve send you the “dmp” file.
And from what i see, i think that after I’ve updated clients to the latest version i got much more errors in server logs with "Sending settings to client failed’. Can this be somehow correlated? Maybe You’ve changed some timeouts in client?
I did now notice that although the clients are backing up I am getting errors reported in the backup notifications. For all of the clients they are reporting “(error): Sending settings to client failed” and I’m seeing:
13.01.14 16:00 DEBUG Connecting Channel to ClientService failed - CONNECT error -55
13.01.14 16:00 DEBUG Connecting Channel to ClientService failed - CONNECT error -55
It seems that the backups do finish though although it doesn’t look like the client tray icons get updated to show a backup was done.
These are using the newest 1.3 clients as well.