We noted that the nightly cleanup hangs every night since we’ve upgraded to the Linux version 2.0.38. We have to stop UrBackup and restart each morning. In an effort to get to the bottom of these I ran urbackupsrv remove-unknown (after shutting down UrBackup) and see the following:
urbackupsrv remove-unknown
2017-01-21 15:56:17: Going to remove all unknown files and directories in the urbackup storage directory. Waiting 20 seconds…
2017-01-21 15:56:37: Shutting down all database instances…
2017-01-21 15:56:37: Opening urbackup server database…
2017-01-21 15:56:37: Testing if backup destination can handle subvolumes and snapshots…
Backupfolder not set
2017-01-21 15:56:37: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2017-01-21 15:56:37: Transitioning urbackup server database to different journaling mode…
2017-01-21 15:56:37: Cleaning up 0 percent
2017-01-21 15:56:37: Cleaning up 0 bytes on backup storage
2017-01-21 15:56:37: Database cache size is 400 MB
2017-01-21 15:56:37: Starting cleanup…
2017-01-21 15:56:37: Freeing database connections…
2017-01-21 15:56:37: Enough free space now.
2017-01-21 15:56:38: Deleting incomplete file backup ( id=86823, backuptime=2017-01-13 08:10:28, path=170113-0837 ) from client “cook” ( id=305 ) …
2017-01-21 15:56:47: Could not open WAL file urbackup/backup_server_link_journal.db-wal (wal checkpoint thread)
2017-01-21 15:56:47: Could not open WAL file urbackup/backup_server_links.db-wal (wal checkpoint thread)
What’s interesting is that when UrBackup is started and stopped those two WAL files are present in the /usr/local/var/urbackup directory. As soon as you start the remove-unknown, those files are deleted and the remove-unknown process just hangs for hours. I end up killing the process.
Any insight on how to resolve this?
Thanks.
Pete