Sonarr version (exact version): 2.0.0.4645
Mono version (if Sonarr is not running on Windows):4 .8.0
OS: Ubuntu Server 16.04
((Debug logs)): https://paste.ee/p/OUwJ0
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here)
Description of issue: When trying to update to the latest version I am receiving an error. It seems that the error is because a log file can’t be copied over but the processes were successfully killed
LOL, Sonarr notices it’s on different mounts and tries to do a verified copy… It goes fine, except that the source file changes coz it’s being appended to.
Tbh, I have to think about what’s the best solution. Maybe exclude .txt for verified/transactional? but that feels like a hack
This looks like the app data directory is in `/opt/NzbDrone (a child of it), which would reset the DB on update anyways, at least that’s my assumption given the backups are being backed up pre-update installation.
This sounds like the AppData location check doesn’t work if it’s a descendant of the startup directory, but it should.
You’re right, I didn’t even notice that. I thought we did a backup of the AppData, but you’re right, we only backup the db. So this is due to Bin & AppData being mixed.
–data should be in /var/opt/NzbDrone in this particular case if you want to adhere to unix FHS.
About the check EnsureAppDataSafety, could it be that the paths are just slightly different? A peek at System->Info should tell.
My guess is that there’s a symlink from ~/.config/NzbDrone to /opt/NzbDrone.
If so then we can probably improve the check by performing it twice, once for the raw path, and once via the symlinkresolver.
There was a symlink from a previous install linking /opt/NzbDrone/Nzdrone to ~/.config. I removed that it was able to be updated.
Thanks. I’m still shocked I didn’t see it before.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.