Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - Lidarr

Featured Replies

Just wanted to follow up - I am still getting 100% cpu usage on lidarr for any cores i give it after somewhere between 1-24 hours of uptime on the container with no errors in logs. Any suggestions?

  • Replies 193
  • Views 69.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I poked the package maintainer on aur and they bumped the version up, try the new image. Sent from my SM-G935F using Tapatalk

  • Hey, @binhex, I'm back to be "that guy" again...   Would you ask the guys at aur to update to build 281 or newer. That one takes care of a pretty ugly bug that makes working with album lists

  • Running this container via unRAID. No issues until i upgraded unRAID to latest 6.5 stable release tonight. All docker containers are fine except Lidarr. Starts with : root@localhost:# /usr/local/em

Posted Images

On 8/4/2022 at 7:07 PM, hmoney007 said:

Just wanted to follow up - I am still getting 100% cpu usage on lidarr for any cores i give it after somewhere between 1-24 hours of uptime on the container with no errors in logs. Any suggestions?

+1

  • 2 weeks later...
On 8/4/2022 at 7:07 PM, hmoney007 said:

Just wanted to follow up - I am still getting 100% cpu usage on lidarr for any cores i give it after somewhere between 1-24 hours of uptime on the container with no errors in logs. Any suggestions?

I have noticed that I have a Rescan Folders task that takes forever (hours) to run and to make it worse, multiple Rescan Folders tasks are queued up. So  once one finishes another will kick in shortly after. I suspect that this is at the heart of my issue. I did some searching and found this thread: https://github.com/lidarr/Lidarr/issues/1105
It mentions having many unmapped files, which I have a bunch of. Do you have the same behavior, I wonder? It's a tough thing to fix, as I can't manually map unmapped files until the Rescan Folders task ends, but you can't end the active scan in the UI. I am seeing if it's possible to end in the CLI, so I can map my files and see if that helps the situation out.

Anyway, just thought I would drop an update on what I have learned so far. Let me know if you have learned anything on your end.

Thanks!

Edited by UNRAID5

  • 3 months later...

Three questions. I use PIA for my VPN. How can I verify that I'm actually on the VPN when qbtvpn is running? Or won't it run at all if not connected? (currently it is running great, I just don't know if it is really on the VPN)

 

Second, if I use other VPN enabled *arr apps, is each one considered it's own computer, or are they all considered one login by PIA?  I have a limited about of 'uses' for PIA and I wouldn't want to get myself into a bind. (currently qbtvpn is the only one I'm using)

 

Third, I use port forwarding with PIA. Can I set, or does qbtvpn already, read whatever the port I'm given is and use that in it's settings?

 

  • 2 weeks later...
On 8/4/2022 at 9:07 PM, hmoney007 said:

Just wanted to follow up - I am still getting 100% cpu usage on lidarr for any cores i give it after somewhere between 1-24 hours of uptime on the container with no errors in logs. Any suggestions?

I was having same issue.

For anyone having this issue, i found what i believe to possibly be the cause, at least it was in my case.

I imported a large number of files that weren't formatted/tagged quite correctly. After importing them, i used Lidarr to rename all the files one artist at a time, this way it shows the preview of what its going to do, and allows you to proceed or cancel. I did this because sometimes it wrongly identifies the track, or uses a strange release, so i was able to verify it was all correct.

If you enter the container console and run "htop", it shows the processes and one of them was what i believe to be the audio fingerprint process. It was stuck running on the same 3 files indefinitely. I believe at some point of moving/renaming files, the files it was currently working on broke the process and it was stuck, because the path of the file it was processing didnt exist any more.

Restarting the container fixed it permanently. 

I do have a question, im looking to use the mass editor to set all of the artists metadata to "none" but its not an option. 

Is there a way to set all of the hundreds of artists to none without having to do it individually?

Edited by TurboStreetCar

On 12/8/2022 at 9:42 PM, TurboStreetCar said:

I was having same issue.

For anyone having this issue, i found what i believe to possibly be the cause, at least it was in my case.

I imported a large number of files that weren't formatted/tagged quite correctly. After importing them, i used Lidarr to rename all the files one artist at a time, this way it shows the preview of what its going to do, and allows you to proceed or cancel. I did this because sometimes it wrongly identifies the track, or uses a strange release, so i was able to verify it was all correct.

If you enter the container console and run "htop", it shows the processes and one of them was what i believe to be the audio fingerprint process. It was stuck running on the same 3 files indefinitely. I believe at some point of moving/renaming files, the files it was currently working on broke the process and it was stuck, because the path of the file it was processing didnt exist any more.

Restarting the container fixed it permanently. 

I do have a question, im looking to use the mass editor to set all of the artists metadata to "none" but its not an option. 

Is there a way to set all of the hundreds of artists to none without having to do it individually?

 

You're a legend, TurboStreetCar. The htop trick worked for me too. I nuked the files the process was choking on and so far I appear to be back to normal. Thanks!

 

As for the mass editor question, just go into Library > Mass Editor > Click on the Options button and check the Metadata Profile option then click Close. That should do the trick for you.

On 12/16/2022 at 11:19 AM, UNRAID5 said:

 

You're a legend, TurboStreetCar. The htop trick worked for me too. I nuked the files the process was choking on and so far I appear to be back to normal. Thanks!

 

As for the mass editor question, just go into Library > Mass Editor > Click on the Options button and check the Metadata Profile option then click Close. That should do the trick for you.


Glad it worked!

Yep i got the option, but there's no "none" profile. You can only change it to standard.

Also it doesn't look like my recycle bin is emptying, and i don't see the task "clean up recycle bin" in my tasks menu.

  • 3 months later...

Bump, Still looking for a way to set all albums to NONE for metadata in the mass editor. 

There's WAY too many albums to do it individually.

  • 8 months later...

New to Lidarr and been trying but struggling to find the information
I think i created a tag to exclude vinyl. However i also see the setting to score exclude vinyl, but when i look at my already owned material after changing that score it scores at that number. Is the exclude vinyl number actually mean non-vinyls score this?

My goal is to set lidarr up to only look for flacs both regular and 24 bit but am struggling to accomplish this. I also tried to delete the any profile but it won't let me delete but i can't find anything associated to it


254002960_Screenshot2024-01-03at4_30_15PM.png.0cad91ce1b277685846d079e06b856bd.png

Screenshot 2024-01-03 at 4.32.33 PM.png

  • 5 months later...

Lidarr has worked really well for the past 6 months but now the docker just refuses to start. Can you offer some guidance on troubleshooting steps? No recent changes to the system.

  • 4 months later...

Just updated the lidarrr docker - and it pulled 1 GB on the download. Is that correct?

Screenshot 2024-10-27 082615.png

  • Author
5 hours ago, grizlyadams said:

Just updated the lidarrr docker - and it pulled 1 GB on the download. Is that correct?

As you are probably picking up a new base image and the layers for the application it will be larger than normal, subsequent pulls will be smaller until a new base is republished again.

 

Edit - looks like it maybe due to cached build files, investigating further

didn't work after the update (neither did radarr or sonarr - i've rolled them all back to previous and they're working fine. FYI, the one i rolled back to for sonarr was 260MB rather than 960MB. 

This seems to concern several dockers.

Here are the container sizes on October 23 and tonight :

 

binhex-lidarr before update 2.29 GB after update 6.43 GB

binhex-sonarr before update 1.62 GB after update 3.72 GB

binhex-radarr before update 1.70 GB after update 3.44 GB

binhex-prowlarr before update 1.45 GB after update 2.86 GB

  • Author
53 minutes ago, deadnote said:

This seems to concern several dockers.

Here are the container sizes on October 23 and tonight :

 

binhex-lidarr before update 2.29 GB after update 6.43 GB

binhex-sonarr before update 1.62 GB after update 3.72 GB

binhex-radarr before update 1.70 GB after update 3.44 GB

binhex-prowlarr before update 1.45 GB after update 2.86 GB

The above images have just been rebuilt with more aggressive cache clean up, sizes are now back to expected sizes, please pull down the newly built image for lidarr (and any of the others from the above list).

  • 2 weeks later...
On 10/27/2024 at 8:56 PM, binhex said:

The above images have just been rebuilt with more aggressive cache clean up, sizes are now back to expected sizes, please pull down the newly built image for lidarr (and any of the others from the above list).

apologies for late reply - all seems good now, thanks.

  • 1 month later...

When will the latest version 2.8.2.4493-1-01 be published to dockerhub.

  • Author
1 hour ago, mr2toyou said:

When will the latest version 2.8.2.4493-1-01 be published to dockerhub.

Looks like GitHub Action had a hiccup, kicked it off again and its built, please 'force update' or 'check for updates' and apply.

  • 5 weeks later...

Ran into an odd issue today and am hoping somebody might be able to help out.

 

I'm running the binhex Lidarr container (version 2.9.6.4552) on unraid 6.12.15. I'm automatically syncing finished torrents from a remote seedbox to unraid with resilio. Lidarr is monitoring the download directory and seems to correctly see items when they arrive.

 

However, when Lidarr goes to process downloads, I see the error below in the Lidarr debug log. In the Lidarr activity queue, all torrents sit in the "Downloaded - Importing" state (purple download icon) forever, as it periodically tries to process each download:

 

2025-02-06 14:20:42.4|Debug|DownloadedTracksImportService|Processing path: /
2025-02-06 14:20:42.4|Debug|DiskScanService|Scanning '/' for music files
2025-02-06 14:20:42.4|Debug|DownloadProcessingService|Failed to process download: xxxxxxxxxxxxxxxxxx

[v2.9.6.4552] System.IO.IOException: Input/output error : '/sys/kernel/slab'
   at System.IO.Enumeration.FileSystemEnumerator`1.FindNextEntry(Byte* entryBufferPtr, Int32 bufferLength)
   at System.IO.Enumeration.FileSystemEnumerator`1.MoveNext()
   at System.Linq.Enumerable.SelectEnumerableIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at NzbDrone.Common.Disk.DiskProviderBase.GetFileInfos(String path, Boolean recursive) in ./Lidarr.Common/Disk/DiskProviderBase.cs:line 518
   at NzbDrone.Core.MediaFiles.DiskScanService.GetAudioFiles(String path, Boolean allDirectories) in ./Lidarr.Core/MediaFiles/DiskScanService.cs:line 240
   at NzbDrone.Core.MediaFiles.DownloadedTracksImportService.ProcessFolder(IDirectoryInfo directoryInfo, ImportMode importMode, Artist artist, DownloadClientItem downloadClientItem) in ./Lidarr.Core/MediaFiles/DownloadedTracksImportService.cs:line 188
   at NzbDrone.Core.MediaFiles.DownloadedTracksImportService.ProcessPath(String path, ImportMode importMode, Artist artist, DownloadClientItem downloadClientItem) in ./Lidarr.Core/MediaFiles/DownloadedTracksImportService.cs:line 93
   at NzbDrone.Core.Download.CompletedDownloadService.Import(TrackedDownload trackedDownload) in ./Lidarr.Core/Download/CompletedDownloadService.cs:line 122
   at NzbDrone.Core.Download.DownloadProcessingService.Execute(ProcessMonitoredDownloadsCommand message) in ./Lidarr.Core/Download/DownloadProcessingService.cs:line 64

 

Google doesn't return much useful info for this error.

 

Additional info:

  • /data in the docker container is mapped to /mnt/user/resilio/torrents. This where items from the seedbox are sync'd to, and where Lidarr watches for downloads.
  • /media in the docker container is mapped to /mnt/user/Music. This is a new, completely empty share. Permissions on this and the above are both currently public.
  • If I try to manually copy items from the download directory to the media folder (quasi-mimicking what Lidarr is presumably trying to do), I have no issues.
  • There is 5.8TB of free space on both of the above shares.
  • There don't appear to be any issues with any of my unraid disks. They all pass SMART tests, and I've tried isolating the /data and /media shares to various individual disks to try to rule out a hardware issue.
  • "Use Hardlinks instead of Copy" is unchecked in Lidarr -> Settings -> Media Management.
  • There are no errors at all in the unraid system log.
  • The only place I see any errors (the one pasted above) is in the Lidarr debug log (System -> Log Files -> lidarr.debug.txt).

Anyone have any ideas?

Hello! Have been using the container for over a year with no issues. Thanks for it.

 

Starting mid-January, upon sign in I would be greeted with a white screen displaying the following message.

image.png.7663ae06c4b0abc0b550b2f8a51cb17d.png

 

Checking the logs seems to indicate a malformed database. I've searched and found the tutorials for how to attempt to repair the database but they do not seem to lead to any success. Here's the error log: https://pastebin.com/gdM5wD6N

 

Restoring from a backup doesn't help, even one several weeks old that I know was working (at that time).

 

I destroyed the docker reinstalled around a week ago. Rescraped my media, reset everything, as if it was a fresh installation. It has worked fine, I updated the docker a few days ago, and sometime between then and now, everything happened again.

 

Has anyone seen this or have any ideas on where to go from here?

  • 5 months later...

Has anyone moved to the blampe docker from this one and is there any advice?

  • 2 weeks later...

The Lidarr platform is unusable at the moment and has been so since late April. They screwed up in a musicbrainz schema change and so far have little to no idea how to change their code base to support the new schema.

So it doesn't matter what docker you use, as the Lidarr server(s) aren't going to work to find artists, tracks, etc.

Yep. Pretty disappointing.

7 hours ago, Espressomatic said:

The Lidarr platform is unusable at the moment and has been so since late April. They screwed up in a musicbrainz schema change and so far have little to no idea how to change their code base to support the new schema.

So it doesn't matter what docker you use, as the Lidarr server(s) aren't going to work to find artists, tracks, etc.

Can you send me a PM with a link to where that is?

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.