![]() ![]() qpkg from the repo (or manually downloaded) to have the right folder structure that allows auto updating. Initial versions of the QPKG had this issue, as I have reported some posts ago. Is there a way to bypass the update safety check? config back inside the app and restarted, but I'm stuck on the old version. from a recent backup and apply the database recovery process to that file then try starting Radarr with the recovered backup file. This limitation is a known pain point for many users and will maybe come in a future version. config folder while Sonarr was running, but that just breaks Sonarr and no links work. No and the reason is that Radarr is a fork of Sonarr, where every show has a folder. Seems they've introduced some protection to avoid wiping the. The logs said it wouldn't update because the. config and asked me to configure a password again.Īfter setting the password, I tried to update the app internally, but it immediately reported "Failed" in the lower left corner. config to /share/CACHEDEV1_DATA/.qpkg/SonarrV481/.config, then started Sonarr. config folder to a safe location.Ĭan you please expand on how you were able to auto update? I seem to be missing a step. ![]() config inside the app folder is deleted after automatically or manually updating the app using the built in engine as reported initially (built in updates wipes the app folder), so it is strongly suggested that you backup your settings to prevent configuration lost.ĭo use the internal System tool "Backup", but also copy the whole. Be sure you get ownership and permissions right. It will be lost if you do use the internal built in update feature and don't backup itīefore you use the internal update feature, stop the app and move the folder.Ĭode: Select all /share/CACHEDEV1_DATA/.qpkg/SonarrV481/.configĪlso, I can confirm that the old. ago You could simply move the directory where you want it and then create a symlink in the original location pointing to the new one fryfrog 3 yr. Your configuration is not lost, but it is located in a different folder that Sonarr will not read. You will need to manually move them (or backup and restore). The configuration folder will be created in a different location, so Sonarr will not be able to read the "old" settings. once a backup was done, the size was of 200M which in my opinion is a bit too large even when comparing it to other dockers I have. The question I have is related to the backup. I have successfully auto updated to 4.0.0.319 without issues. Hi, I am running Sonarr as a docker (installed yesterday) and I am monitoring 5 seasons. Hi Stephane, as mentioned in my original post, apparently the update script wipes the app folder, in consequence if the confirg subfolder is located inside it, it will be wiped as well, loosing the configuration.Ī solution could be having separate config and App folders inside the QPKG App root folder. Not sure the best way to put that here.What is the issue with auto update ? have error logs Thanks!ĮDIT: I have the logs, but they are LONG. nice new layout Successful behind Nginx reverse proxy: - backed up Sonarr 2. config/Sonarr instead (SOMEHOW)? I’m way lost here, and worried I have to start over from scratch. uninstalled Sonarr2, installed Sonar3 and restored last backup. config/nzbdrone folder, which is weird because it is set to backup EVERYTHING.Īny guidance? Do I need to actually change the default appdata directory to. Which is weird, because what is the sonarr directory for? ALSO, on backblaze there is no backup of the. BUT I did notice that in “about” my appdata directory is. config directory, deleted everything in the sonarr config directory on my hard drive, then moved the files I downloaded from backblaze into the one on my hard drive (with sonarr shut down). So, since I have backblaze I went and fetched the sonarr. This time that didn’t work it’s ALL empty. …the last time this happened, I simply reinstalled Sonarr and it kept all my configs. Everything was working for a minute before it crashed. I did the mass series update to shift it over. ![]() Already moved the files, but not the folder location setting in Sonarr. So I was shifting all my downloads to a different directory (new hard drive). ![]() If Im downloading entire seasons Ill usually put more care into things. So instead of having a Docker run command that sets the persistent volume, ports, etc it’s in one file If you do a Docker run and weeks or months later want to update the container you have to remember the exact settings you used. Basically like a config file for your docker command. :) Usually for incremental episode downloads Ill just let Sonarr copy and rename/etc the files, but only from public trackers where I generally dont seed more than 3x. Docker composer uses a YAML format to specify settings. Mono version (if Sonarr is not running on Windows): 4.6.2 The amount of bind-linking going on with my sonarr container probably doesnt help with that. ![]()
0 Comments
Leave a Reply. |