I seem to have a corrupted backup_server.db database. I tried a sqlite3 dump and restore, tried a sqlite3 “PRAGMA integrity_check”, and when I run “urbackupsrv repair-database” it fails with a segmentation fault when it calls sqlite3 “.recover” from Database.cpp CDatabase::Recover() - this is in the downloadable 2.5.33 source code, which contains sqlite3 3.43.1. I’m bewildered and confused.
I tried looking for newer source code and found
which was updated recently, but which contains an older sqlite3 3.31.1 from apparently 5 years ago.
Is the github code the current official source, or should I be looking somewhere else?
Edit to add: the service seems to be happily running again, so backups seem to be working. But there may still be database problems lurking?
Unfortunately I have seen this too, actually i ran a test on a clean instance and there it throws the exception too. I have not explained the scenario in more detail in my thread about follow_symlinks not being honored because i feel bad complaining on free software, but that was the reason i concluded i had to remove my whole backup store and start over, only to find with running that test on the clean install that it fails anyway. So that might had been for nothing. I also experienced backups were running fine anyway. The repair-database command seems broken to me and should not lead you to conclude the database is corrupt. Instead the message on the webinterface about it being corrupt is more telling (IMHO!). You will probably find that following GilesP advice, any database backup fails with the same exception, i had that too (and made me conclude i needed to start over). Im not sure what happened with the last version, but some things seem to have broken. Just a moment ago i found that the filepostbackup script is not run on my desktop, even when the backup is succesful, ill open another thread if i cancel out its not just my desktop.
I guess i just wanted to give you a fair warning not to do the same thing i did and wait for Uroni to investigate. This seems like another bug to me, its reproducable (at my end) by setting up a clean install of urbackupsrv, opening the webinterface, change a setting or two (/var/urbackup then holds the .db files), stopping urbackupsrv and running the urbackupsrv repair-database command. Every time it failed like this:
This seems like perhaps a bug in the included version of sqlite3. I’m running on an older machine without a more current sqlite3, or a version that has “.recover”. I copied the backup_server.db file to a newer machine, and sqlite3 .recover runs fine. Seems to me that things are actually “fine” except that sqlite3 has a bug that misleads us?
