I’m having the exact same issue as marveltec
As I can see seems like the download directory here http://beta.urbackup.org/Client/2.2.3%20beta/update/ does not contain the .sig and sig2 files.
Maybe if they where added and I could download them it would correct the issue?
Hi, Also another thing i picked up in the web portal if i select to show IP Addresses its not displaying correct ip addresses
Sorry, the signature files were missing. They are generated and uploaded now.
Thnx Uroni with the Sig files auto updates and download of client from web portal is working again. any reason why the web portal keeps showing incorrect IP address for clients as well as incorrect file backup status?
Hi
Using beta client and stable server at the office. the restore gets stuck on my test script https://github.com/ptempier/check_backups :
2017-11-20 16:55:50: Restoring file “/tmp/filetests/test33”…
2017-11-20 16:55:50: Restoring file “/tmp/filetests/test35_éèçàùù=±ç-()61aze¨£€#,x az~”…
2017-11-20 16:55:50: Restoring file “/tmp/filetests/test36_?”…
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘*’ at pos 0. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ’
’ at pos 1. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘:’ at pos 2. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘&’ at pos 3. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘s’ at pos 4. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘h’ at pos 5. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘a’ at pos 6. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘r’ at pos 7. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘e’ at pos 8. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘’ at pos 9. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘p’ at pos 10. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘a’ at pos 11. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘t’ at pos 12. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘h’ at pos 13. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘=’ at pos 14. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: Restoring file "/tmp/filetests/test37’^&@{}[]$!%"…
2017-11-20 16:55:50: Restoring file “/tmp/filetests/test38_aaaa”…
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ’ ’ at pos 0. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘b’ at pos 1. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘b’ at pos 2. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘b’ at pos 3. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ’
’ at pos 4. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ’ ’ at pos 5. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘c’ at pos 6. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘c’ at pos 7. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘c’ at pos 8. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘c’ at pos 9. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘c’ at pos 10. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘&’ at pos 11. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘s’ at pos 12. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘h’ at pos 13. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘a’ at pos 14. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘r’ at pos 15. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘e’ at pos 16. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘_’ at pos 17. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘p’ at pos 18. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘a’ at pos 19. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘t’ at pos 20. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘h’ at pos 21. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: ERROR: Error parsing file BackupServerGet::getNextEntry - 1. Unexpected char ‘=’ at pos 22. Expected ‘f’, ‘d’ or ‘u’.
2017-11-20 16:55:50: Restoring file “/tmp/filetests/test39_éèçàùù=±ç-()61aze¨£€#,x az~”…
Could you post some details (e.g. what it shows as IP address and what would be the correct one…) as well as have a look at the log file if there are any errors?
auto update of clients… for macOS, they seem to update to 2.2.3 beta fine without issues (from 2.2.2 beta) … but when windows clients attempt to update, they lose connection and have to be removed and reinstalled. I’d like a way to update them on my own (without urbackup server, preferably installing over the top of the current AND keeping settings), but just running the installer when its already installed doesn’t work. The only method that seems to work for me is removing and reinstalling with the python script.
Similar experience here, automatically updating Windows client from 2.1.16 to 2.2.3 beta for Internet connected systems lost the Internet settings and thus connection. Most fields on Internet tab in Client settings were blank, including Internet server name/IP and server password. Fortunately I had already transitioned to group settings on the server so was able to download a pre-configured client, uninstall the empty one, and install the new, properly configured client.
As far as I can tell, the local systems updated successfully without manual intervention.
Could you have a look at "C:\Program Files\UrBackup\urbackup\data\settings.cfg" after it looses connectivity?
I’d like to test it, but “autoupdate clients” is a server setting, so it’d have to be turned on for all clients, which I don’t want to do and have to fix a bunch, which is another reason I’d rather just update them from alternative methods anyways, that way you can use a test group and manually push it when you feel like it, to just the clients you want.
@orogor
Thanks for the test script! Newlines in file names are evil, but that should also be fixed now.
Now what’s not working for me is hard links (expected and documented limitation) and test 40 (first test_bincopy).
for me it fails because /bin also contains hardlinks.
Hi Uroni,
ok so my setup is internet only clients to a windows server 2012 urbackup server and all their IP addresses are showing up as the gateway (of the servers local network) ip address in the web portal. also even though Incremental file backups are finishing without error since i upgraded from server 2.1.19 the status in the web portal shows as “No recent backup” even if a backup has just completed without error.
Are there any errors/warnings in the server log file?
Hi Uroni,
I do get these errors in the log on server startup
2017-12-04 16:20:09: ERROR: Loading luaplugin.dll failed
2017-12-04 16:20:09: WARNING: Lua plugin missing. Alerts won’t work.
2017-12-04 16:20:21: WARNING: File clientlist_b_9247.ub is missing/cannot be accessed
2017-12-04 16:20:21: WARNING: File clientlist_b_9251.ub is missing/cannot be accessed
but not too much after this apart from the normal errors/warnings from time to time during file backups
That’s the cause of the status problem. Which installer did you use and is the luaplugin.dll file present?
I used the “UrBackup Server 2.2.5 beta.exe” installer and no i don’t see the luaplugin.dll file in the install directory. i also just browsed inside the install package and it doesn’t seem to be there either.
i extracted it form the MSI install package and its working now
Hey Uroni, just started testing out this new beta and it looks great! One suggestion for the alerts- please allow us to customize the tag on the alerts as well as the “Send OK mail” so that we can parse that with a PSA or RMM tool. It’s easy to create a filter from subject line tags in other software.
That’s one reason it is scriptable. You can modify the script. If you post it and enough others think it is a useful change we can make it official.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.