-
-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | Sonarr: Migrate to v3 #4292
Conversation
+ DietPi-Arr_to_RAM | Add support for Sonarr v3 and Radarr v3 + DietPi-Arr_to_RAM | On first link to RAM, create a script in the programs data dir to update the linked database backups, as v3 do not support arguments to pass to custom scripts anymore and do not allow to start scripts from within /boot.
+ CHANGELOG | DietPi-Arr_to_RAM: Support for Sonarr v3 and Radarr v3 has been added. On first link to RAM, a script "/mnt/dietpi_userdata/(sonarr|radarr|lidarr)/dietpi-arr_to_RAM.sh" is created, which allows updating the linked database backups via the programs "Custom Script" feature. Since v3, it is not possible anymore to pass arguments to custom script or call scripts inside the /boot directory at all, which broke the previous "/boot/dietpi/misc/dietpi-arr_to_RAM 2 (sonarr|radarr|lidarr)" calls in two ways. + CHANGELOG | Sonarr: Support for and migration to v3 has been implemented. Existing installs won't be migrated automatically, run "dietpi-software reinstall 144" to upgrade your Sonarr to v3. On DietPi update, Sonarr v2 users will receive a related notification.
+ DietPi-Arr_to_RAM | Use safer approach to create database backups: The -shm and -wal files do sometimes not exist, e.g. when the connection is closed temporarily. In theory the should never exist when the program is not running, but in practice it does at least with Sonarr and Lidarr, which obviously do not close connections gracefully or use certain SQLite flags to keep those files intentionally. However, havoc can happen when those files do not exist while the database is linked to RAM or stored back to disk: In the first case, if the program then crashes, up-to-date -shm + -wal files will be mixed with a backup database file, in the second case, the -shm and -wal symlinks will stay on disk, breaking program start as the RAM dir is removed. Especially in combination with the automatic backup restoring, mixing of old and new files can happen, corrupting the database. At least when linking to RAM and for backup creation, SQLite is used now to read and store the database to the backup location, which includes -shm and -wal, so that a single consistent database file is present for the program to start with.
Hello, I dont know how to use github very well. I just wanted to point out that there seems to be an issue in this script /dietpi/misc/dietpi-arr_to_RAM at line 79. When parsing arguments the if statements checks for sonarr instead of radarr. I also wanted to point out that in the last update (7.1.2) the scripts created by the dietpi-arr_to_ram 2 command (when migrating sonarr or radarr) have a typo that wont let the command run. I believe I've explained myself if not get back to me. |
Yes we know and already fixed it. |
Ok, is the patch up right now? edit: thanks for the fast answer ! |
If you already created the script, it would need to be changed manually Edit |
Ok, I'll do those manually then. What about the other problem on the argument check. Is that something that is known ? here: https://github.com/MichaIng/DietPi/blob/master/dietpi/misc/dietpi-arr_to_RAM |
Not yet 😃 DietPi/dietpi/misc/dietpi-arr_to_RAM Line 79 in 86c5e37
|
True, another typo. |
@MichaIng |
Done: 4b171a1 |
Wow, you sure work fast guys! I cannot be happier with dietpi! |
What happens when you call it manually?
|
This are the results. |
Just to be sure, you don't have Radarr installed? Correct? |
i have both sonarr and radarr installed, sorry if i didn't address this earlier. I thought the fix would apply to both radarr and sonarr |
There is one more issue for detecting Radarr correctly. It would require correction on line 79 DietPi/dietpi/misc/dietpi-arr_to_RAM Line 79 in 86c5e37
|
i'm a newbie with coding and this stuff, so i'm not sure i can figure a way how to correct that line. Would there be a patch that i can just run in the command line that would fixed both radarr and sonarr with dietpi to ram script? |
Do you have MOTD in the DietPi banner enabled? If so, can you paste the output of:
|
Just adding to this that until I manually ran dietpi-banner the fix did not happen. So it might help running it. |
But it runs on any login, doesn't it? |
That's a very old MOTD which should have been replaced long ago 🤔. Can you please paste the following:
|
Okay... I don't know how it got wrong.. this is the output for the journalctl command
|
I think I found the issue. The following file does not exist, does it?
The MOTD is only updated daily, if MOTD is actually enabled in the banner: https://github.com/MichaIng/DietPi/blob/master/rootfs/etc/cron.daily/dietpi#L38-L43 And I was wondering why still so many users suffer from issues that should be fixed already 😄. In you case:
|
okay so should i just wait till tomorrow and use the fix the MOTD offer or am i missing something? again really appreciate your time and effort in answering my questions😁 |
Run the commands I edited into my post 🙂. |
Awesome! the fix works wonderfully! thank you so much for the time and effort! You're amazing 😁 |
Thanks for your kind feedback and responsiveness here as well. Great that we finally found the reason for users seeing outdated banner messages (and not receiving fixes we hack inside). I hope I find time for next release to add a dedicated transparent live-patch feature that allows to interactively apply such fixes, like "A patch is available for issue X, run dietpi-live-patches to apply it to your system" or so. So we can do fixes for issues that can be safely resolved with a single |
Very happy to help 😊! |
The banner does show whenever I ssh into it but I manually had to nano in to the arr to ram script to fix it. |
@Tooloco |
Same reason, I guess: #4292 (comment) |
Yes, and I had manually configured the banner, adding all options but vpn status. |
Ah, you mean the when you reported the issue here? #4292 (comment) |
|
OK just making sure everything is OK its running smoothly now, I've added the script to sonarr and radarr and it's working flawlessly. |
Perfect, many thanks for validating. |
Status: Ready
Commit list/description: