Cessquill

Whilst it's great 6.7.0 is on the horizon, it would be nice to suppress impossible notifications. Whether updates for a version higher than installed are ignored, or updates for a non-released version are ignored, I don't know. (in the first case, where an update is available for a later release, perhaps not a notification raised, but an icon on the Apps page stating that an update is available if you update your OS.)

Anybody know if something's up with Ombi? It's weekly email has just sent out details of stuff that's been on my machine for years. Not everything, just a seemingly random selection across various libraries. I've made no changes to Ombi or Plex AFAIK.

I'd love to help, since I recently switched routers and had similar issues (went from D-Link to a pfSense box). However, I had similar issues to you, and then it just seemed to work late at night also. Trying to remember what I did... Set up NAT for port 21 and 60000-60100 on pfSense. In the config file added... PassivePorts 60000 60100 MasqueradeAddress domainname.duckdns.org <IfModule mod_dynmasq.c> DynMasqRefresh 28800 </IfModule> Internal connections worked, but when I tried to connect externally, Filezilla gave an error (not the same error as I was getting before I configured passive ports). Then, I can't remember what happened, but it works now...

Might help to up your game, buddy and ask nicely.

All your settings are stored in your appdata share, which is separate to the docker image (and likely on your cache drive). The configuration of each docker (eg, the ports and shares it can access) are remembered by unraid as templates. Theoretically, the only thing in the docker image file are the dockers themselves, and once installed should only change when new versions are downloaded - everything else that changes is in appdata* * not always the case - log files can be in docker containers, as can data if a docker's been misconfigured. Came here looking for the best way to shrink your image file (after I raised it whilst tracking down a problem). Didn't know you could batch install with Community Applications. Result!

Hi - just checking it's still the best way to spin down an unassigned device is with the CLI command hdparm -y /dev/sdx ? Long story short, I've got four drives unformatted and end of life that are only in there for now for airflow - I don't currently have dummy drives for my Supermicro case, so filling the gaps with old drives. There's no point in them being spun up, so I'm running the above on all four manually at boot. Alternatively, could the -Y option be better to turn the drive off altogether? Or is there now a better way?

Well, deleting the docker and its settings seems to have solved it. Appdata's storage has gone down from 11GB to 183MB, and it scans without a memory catastrophe. Will keep an eye on it. Took a while to figure how to use the template defaults. Using "previous apps" in CA automatically selects your previous template, and there's no way to revert. Had to search for it in CA and install it that way. Thanks for your time - now to try and replicate the myriad of settings...

Yep, I'll do that. One of the players is a radio, so it's encouragement to get on with it - hate waking up to the stock alarm song! Just noticed my artwork.db file in cache folder is 10.9GB - is that normal? It's not a huge library (quite large - about 19,000 tracks).

Yeah. Makemkv and Krusader seem to run quite large, so I average around 14/15GB and trigger warnings

Cheers, yes - appreciate that. Was going to increase it at next boot anyway as it was just running quite full under normal circumstances. I've had this installed for a long while too, which is why I'm confused. The only thing I've changed is adding more media. And repointing my playlists to Appdata today when I realised my old folder was full of broken playlists). It might need a rebuild, as it was originally ported from a Windows Home Server when it was first available as a docker on Unraid, then patched when the BBC changed their streaming system, then ported to this version. Hmm.

Thanks again. Just started the container and rescanned the library. Both server and scanner logs finished 7 minutes ago, but the container is increasing its RAM by 1% every couple of seconds. Had to stop the container when it got to 70%, as other dockers were being used. Will look into the logs shortly - nothing looked major at first glance, but I'll look in more detail when I next spark it up.

Thanks. I'm increasing the size of my docker image (if that's what you meant?) and have force updated LMS. Also turned on docker log rotation. It happened at least once more today, with LMS using RAM. I'll see how I get on.

I had an out of memory error last night at about 3.15AM (Dec 2), which required a restart of the docker system to resolve. Looking at the syslog from 3.13am it *looks* like LMS was taking up a lot of memory and killed off. The dashboard registered at 100% RAM use, but the docker tab, advanced view listed nothing strange on the RAM graph (although it could have dropped before I got there - late in the night and lucky to be up). I'm no expert here - just hunches and blind guesses. If LMS is periodically eating my RAM, could it be the above setting? Diagnostics attached. EDIT: Happened again as typing this. Docker tab took a long time to load, and when it did, LMS was at 68% RAM usage, with everything else around 1%. Newer file attached, removed old one. unraid1-diagnostics-20181202-1135.zip

Ahh, thank you! Trying to tweak Radarr so that it happens less, but things will always slip through.

This is more of an Ombi usage question, but searching has confused me further, so checking here first in case anybody's solved this issue... Suppose a request goes in, and Radarr goes an gets a bad version. I remove, rescan Plex & Radarr and mark the request in Ombi as not available. However, it still gets sent out in the weekly email. Is it possible to solve the last bit?