binhex Posted April 1, 2021 Author Share Posted April 1, 2021 On 3/31/2021 at 5:14 PM, MothyTim said: Is this docker going to be updated anymore? As I see there has been a new version of Lidarr available for a while now? Cheers, Tim the image is up to date, it will be updated when there is a new release from lidarr:- https://github.com/lidarr/Lidarr/releases/tag/v0.7.2.1878 Quote Link to comment
MothyTim Posted April 2, 2021 Share Posted April 2, 2021 20 hours ago, binhex said: the image is up to date, it will be updated when there is a new release from lidarr:- https://github.com/lidarr/Lidarr/releases/tag/v0.7.2.1878 Oh, strange because I’m seeing this in Lidarr settings? Quote Link to comment
MothyTim Posted April 2, 2021 Share Posted April 2, 2021 20 hours ago, binhex said: the image is up to date, it will be updated when there is a new release from lidarr:- https://github.com/lidarr/Lidarr/releases/tag/v0.7.2.1878 It’s also showing here? So a bit puzzled! Quote Link to comment
binhex Posted April 2, 2021 Author Share Posted April 2, 2021 4 hours ago, MothyTim said: It’s also showing here? So a bit puzzled! The 'latest release' is still currently 0.7.2.1878, the other more recent releases are still not marked as latest and should be considered unstable, screenshot showing 'latest release':- Quote Link to comment
MothyTim Posted April 3, 2021 Share Posted April 3, 2021 14 hours ago, binhex said: The 'latest release' is still currently 0.7.2.1878, the other more recent releases are still not marked as latest and should be considered unstable, screenshot showing 'latest release':- Oh ok, thanks for clarifying! Also thanks for all you do, providing these excellent containers! Quote Link to comment
questionbot Posted April 14, 2021 Share Posted April 14, 2021 (edited) when I search apps in unraid for "Lidarr" I can only find a BETA binhex version... is that this version? Or is there another one I should be using? Edited April 14, 2021 by questionbot Quote Link to comment
binhex Posted April 14, 2021 Author Share Posted April 14, 2021 when I search apps in unraid for "Lidarr" I can only find a BETA binhex version... is that this version? Or is there another one I should be using?This is it yes, it's marked as beta for the application, not the packaging as a docker image.Sent from my CLT-L09 using Tapatalk 1 Quote Link to comment
saifster Posted April 18, 2021 Share Posted April 18, 2021 Hi All, Just discovered lidarr, I was able to install and configure it last night, and it worked great. This morning, there was an update available, after updating, the app will no longer load. If this helps anyone.. here is my log: 2021-04-18 13:29:53.978324 [info] Host is running unRAID 2021-04-18 13:29:54.005206 [info] System information Linux 9c4458b65e49 5.10.21-Unraid #1 SMP Sun Mar 7 13:39:02 PST 2021 x86_64 GNU/Linux 2021-04-18 13:29:54.042859 [info] OS_ARCH defined as 'x86-64' 2021-04-18 13:29:54.142068 [info] PUID defined as '99' 2021-04-18 13:29:54.217478 [info] PGID defined as '100' 2021-04-18 13:29:54.334392 [info] UMASK defined as '000' 2021-04-18 13:29:54.366554 [info] Permissions already set for volume mappings 2021-04-18 13:29:54.409620 [info] Deleting files in /tmp (non recursive)... 2021-04-18 13:29:54.515643 [info] Starting Supervisor... 2021-04-18 13:29:54,992 INFO Included extra file "/etc/supervisor/conf.d/lidarr.conf" during parsing 2021-04-18 13:29:54,992 INFO Set uid to user 0 succeeded 2021-04-18 13:29:55,000 INFO supervisord started with pid 6 2021-04-18 13:29:56,001 INFO spawned: 'lidarr' with pid 56 2021-04-18 13:29:56,003 INFO spawned: 'shutdown-script' with pid 57 2021-04-18 13:29:56,004 INFO reaped unknown pid 7 (exit status 0) 2021-04-18 13:29:56,018 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:29:56,018 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-04-18 13:29:56,023 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247292520384 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:29:56,024 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23247293014992 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:29:56,024 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:29:56,024 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:29:57,026 INFO spawned: 'lidarr' with pid 62 2021-04-18 13:29:57,039 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:29:57,049 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247292567408 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:29:57,049 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247292567456 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:29:57,049 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:29:57,050 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:29:59,054 INFO spawned: 'lidarr' with pid 66 2021-04-18 13:29:59,069 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:29:59,076 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247292567216 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:29:59,077 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247293016240 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:29:59,077 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:29:59,077 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:30:02,081 INFO spawned: 'lidarr' with pid 70 2021-04-18 13:30:02,097 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:30:02,105 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247292567312 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:30:02,105 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247292567264 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:30:02,105 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:30:02,105 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:30:03,107 INFO gave up: lidarr entered FATAL state, too many start retries too quickly 2021-04-18 13:33:20,307 WARN received SIGTERM indicating exit request 2021-04-18 13:33:20,321 DEBG killing shutdown-script (pid 57) with signal SIGTERM 2021-04-18 13:33:20,321 INFO waiting for shutdown-script to die 2021-04-18 13:33:20,364 DEBG 'shutdown-script' stdout output: [info] Initialising shutdown of process(es) 'lidarr' ... 2021-04-18 13:33:21,366 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23247292567504 for <Subprocess at 23247292520480 with name shutdown-script in state STOPPING> (stdout)> 2021-04-18 13:33:21,366 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23247292641440 for <Subprocess at 23247292520480 with name shutdown-script in state STOPPING> (stderr)> 2021-04-18 13:33:21,366 INFO stopped: shutdown-script (exit status 0) 2021-04-18 13:33:21,366 DEBG received SIGCHLD indicating a child quit Quote Link to comment
PR. Posted April 18, 2021 Share Posted April 18, 2021 Getting the same error and been using it for a while now. Quote Link to comment
saifster Posted April 19, 2021 Share Posted April 19, 2021 6 hours ago, PR. said: Getting the same error and been using it for a while now. I tried everything and couldn't fix it, so, I ended up switching to a different version of lidarr. Looked up an alternative on the Apps page, installed it and set it back up in a few mins. The sucky part was, the saved configs couldn't be saved, but, since I also have Sonarr/Radarr, I just copied/pasted the indexer/download client info from there... Once pointed to the root folder I let it search and add all my organized media automatically. Took a little bit, but, it's automated, just requires patience. Quote Link to comment
deadnote Posted April 19, 2021 Share Posted April 19, 2021 Same error Edit the image and set the repository to binhex/arch-lidarr:0.7.1.1381-1-01 make it works again. Waiting for a new update now Quote Link to comment
versa Posted April 19, 2021 Share Posted April 19, 2021 (edited) Confirm, manual roll-back to "binhex/arch-lidarr:0.7.2.1878-1-02" required or it wont start. Console prompt when I try to manually start :latest with "mono --debug Lidarr" "Cannot open assembly './Lidarr': File does not contain a valid CIL image." Seems to be the same bug as when Radarr / Sonarr switched to the new mono build approach: Edited April 19, 2021 by versa Quote Link to comment
binhex Posted April 19, 2021 Author Share Posted April 19, 2021 Hi guys, the image has now been fixed up, please pull down latest. 2 Quote Link to comment
saifster Posted April 19, 2021 Share Posted April 19, 2021 4 hours ago, binhex said: Hi guys, the image has now been fixed up, please pull down latest. Thank you! I downloaded this and it is working perfectly! Quote Link to comment
GeekMajic Posted April 19, 2021 Share Posted April 19, 2021 It's up and running again, but my queue can't be loaded. Quote Link to comment
saifster Posted April 19, 2021 Share Posted April 19, 2021 2 hours ago, saifster said: Thank you! I downloaded this and it is working perfectly! I second this. Works perfectly for me as well Quote Link to comment
deadnote Posted May 4, 2021 Share Posted May 4, 2021 (edited) Hello I have this message in status : Could not connect to SignalR, UI won't update How can I solve it ? Edit : after deluge and lidarr reboot, message disappears Edited May 4, 2021 by deadnote update Quote Link to comment
Deeya Posted June 21, 2021 Share Posted June 21, 2021 Hello, I seem to have an issue with the binhex lidarr container. I mostly use binhex for everything else, they connect to the web ui without issue. However the lidarr container, I am unable to connect. I've tried to change port numbers, etc.. and sill cannot connect. Quote Link to comment
deadnote Posted June 22, 2021 Share Posted June 22, 2021 @DeeyaAny erros in logs ? Quote Link to comment
Judd35472 Posted February 14, 2022 Share Posted February 14, 2022 (edited) Any chance of an update thats allows choice of build fork? Nightly, etc? Thx Edited February 14, 2022 by Judd35472 Quote Link to comment
tjb_altf4 Posted February 14, 2022 Share Posted February 14, 2022 1 hour ago, Judd35472 said: Any chance of an update thats allows choice of build fork? Nightly, etc? Hotio's Lidarr template lets you pick if you're after something right now. Quote Link to comment
ZosoPage1963 Posted March 8, 2022 Share Posted March 8, 2022 Recently, I had some issues so I am re-instlling the app, but the root folder is never found. I see Lidarr scanning, but it never adds the library. I also notice that this has not been updated in about a year. Anyone else seeing this issue if they have reinstalled? I have deleted data in appdata/binhex lidarr but the issue still occurs. Quote Link to comment
MegaBlindy Posted June 30, 2022 Share Posted June 30, 2022 Im experiencing this issue, that lidarr is pinning my cpu to 100%, but not showing of doing anything in the webapp. This is what it looks like on htop Quote Link to comment
tjb_altf4 Posted June 30, 2022 Share Posted June 30, 2022 (edited) 56 minutes ago, MegaBlindy said: Im experiencing this issue, that lidarr is pinning my cpu to 100%, but not showing of doing anything in the webapp. This is what it looks like on htop fpcalc is a fingerprinting app, so I think Lidarr is scanning your library trying to identify music. I would use cpu pinning options in the docker template (toggle advanced) and give it 2-4 vcores, that way it won't cripple your server Edited June 30, 2022 by tjb_altf4 1 Quote Link to comment
hmoney007 Posted July 15, 2022 Share Posted July 15, 2022 On 6/30/2022 at 6:40 PM, tjb_altf4 said: fpcalc is a fingerprinting app, so I think Lidarr is scanning your library trying to identify music. I would use cpu pinning options in the docker template (toggle advanced) and give it 2-4 vcores, that way it won't cripple your server yea this puts any cores i give it at 100%... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.