Dear developers, I wish you a happy new year 2024! and at the same time I'd like to share with you the problem I recently encountered.
After running the urbackup_api_test.py script, the global parameters of my Urbackup instance ended up with numerous json arrays instead of the expected valid data.
I described the problem on the Urbackup user forum. The valid data had been replaced by json tables, like this:
Default directories to back up: /etc; /root; /home
instead of:
Default directories to back up: {'value': '/etc;/home;/root'}
What's unusual is that the problem was propagated to all Internet clients (and not to clients on the local network). For example, one client's group authentication key became internet_authkey.group={'value': 'Fg5YCmMtyV'} instead of internet_authkey.group='Fg5YCmMtyV'.
Is it possible that it was really the script that caused the damage? if so, it needs to be corrected urgently...
For my part, I've completely reinstalled the Urbackup Server instance.
subsidiary question: would restoring the settings table in the backup_server_settings.db database have made it possible to go back?
Dear developers, I wish you a happy new year 2024! and at the same time I'd like to share with you the problem I recently encountered.
After running the urbackup_api_test.py script, the global parameters of my Urbackup instance ended up with numerous json arrays instead of the expected valid data.
I described the problem on the Urbackup user forum. The valid data had been replaced by json tables, like this:
Default directories to back up:
/etc; /root; /home
instead of: Default directories to back up:{'value': '/etc;/home;/root'}
What's unusual is that the problem was propagated to all Internet clients (and not to clients on the local network). For example, one client's group authentication key became
internet_authkey.group={'value': 'Fg5YCmMtyV'}
instead ofinternet_authkey.group='Fg5YCmMtyV'
.Here’s a pastebin link where you’ll find a trace of the API test script execution a few days ago. :roll_eyes:
Is it possible that it was really the script that caused the damage? if so, it needs to be corrected urgently... For my part, I've completely reinstalled the Urbackup Server instance.
subsidiary question: would restoring the settings table in the backup_server_settings.db database have made it possible to go back?
Thanks in advance for your feedback.
Ernest.