Squid

Reboot If that doesn't fix it, then delete /config/plugins/community.applications and /config/plugins/community.applications.plg on the flash drive and reinstall

Million errors about your cache pool Sep 28 17:45:30 Highlander kernel: BTRFS warning (device sdd1): lost page write due to IO error on /dev/sdf1 Sep 28 17:45:30 Highlander kernel: BTRFS error (device sdd1): error writing primary super block to device 3

A PR I put in to unRaid (6.6.2) was approved, and when it is released it will break CA. Got my update out now in advance.

Just to remove a variable from the equation, can you take the flash drive into another computer, edit /config/go and remove the duplicated /usr/sbin/emhttp & line from it, try it again and then post diagnostics again if there's still trouble.

Your screenshot shows that unRaid (and docker) will NOT utilize cores 0, 1, 10, 11. It will use everything else. Isolating = Isolating them from the OS (ie: OS won't use them)

If you want a VM to have exclusive access to the cores then you isolate those cores and pin the VM to them

unRaid will still potentially use those cores (along with any docker apps that aren't also pinned)

If you isolate cores via the cpu pinning page, and then tell Plex to execute on more than one of those cores via cpu pinning, it will only execute on one of them. Isolating cores is usually used to reserve the core for exclusive use of a VM. Sent from my LG-D852 using Tapatalk

Put it this way, it was the fastest plugin I've banged together ever. It shouldn't install on anything but 6.6.0 but mistakes are possible when I'm getting ready to leave the house for a couple of days, and will rethink the logic for the actual security routine at another time.

Actually, go to plugins / install plugin and paste this url in instead: https://raw.githubusercontent.com/Squidly271/misc-stuff/master/unRaid6.6.Hot.Fix.plg Very quick and dirty, FCP will complain about it, but it should do the trick for you.

ok. Bug in unRaid (my fault actually). Logic error in how its looking for a bash command, and it's picking up the semi-colon wrongly (due to the nested quotes). I won't be able to issue a PR for a couple of days to fix this issue, but in the meantime on unRaid 6.6 you can execute this command via user scripts (run once at array start) to bypass it sed -i 's/function dockerRunSecurity($command) {/function dockerRunSecurity($command) {return false;/g' /usr/local/emhttp/plugins/dynamix.docker.manager/include/Helpers.php

Because in the extra parameters or something you are attempting to run a bash command and/or redirect the output of the docker run command somewhere else. (and it's not related to an update of the container, but rather its a 6.6 thing) It is a security violation, and can potentially trash the host OS. Edit the container, switch to advanced mode and post up a screenshot.

If UD allowed you to set a mount point of /mnt/docker, then your UD version is extremely out of date. For the longest time it has only allowed mount points of /mnt/disks/... (an annoyance to me for my use case / muscle memory, but I completely understand why)

It should work. There's at least no code that prevents installation on 6.3 (or even 6.1/6.2) CA though does require 6.4 nowadays

Either your flashdrive is read-only, or has dropped offline You didn't enable get more results from dockerHub in CA settings You didn't search

Click the whale Sent from my LG-D852 using Tapatalk

@ljm42 Went one better. CA will default to displaying http is https isn't available, but if you wear a tin-foil hat then if https isn't available then it won't display the icon. Switchable in settings.

What I'll do is have CA automatically adjust every icon to be https. If it fails to load that, then it'll try and display the http (because not all of the Icons present in CA are available via https). If it then fails to download that, then it'll display the standard question mark. The site "lock" should stay normal until it hits an image that isn't available via https

The template does not exist in /config/plugins/dockerMan/templates-user on the flash drive. You've either deleted it, or your flash drive has some corruption. Only recourse is to make a note of your path mappings and then remove the container, re-add it and enter back in your mappings

NAME="Mr.Mulse" Sep 22 12:40:00 Mr emhttpd: Starting services... Apparently Not (or it's been tightened down in the Kernel since then)

The id of the computer IS Mr.Mulse However due to the period it is getting truncated to Mr Get rid of the period (name the server instead MrMulse) and probably half the problems will go away

Yes, and the linked post explains why it didn't.

Sep 21 00:56:09 undou root: Fix Common Problems: Warning: Docker Application nzbget has CPU cores pinned via the extra parameters (--cpuset-cpus) Sep 21 00:56:09 undou root: Fix Common Problems: Warning: Docker Application radarr has CPU cores pinned via the extra parameters (--cpuset-cpus) Sep 21 00:56:09 undou root: Fix Common Problems: Warning: Docker Application sonarr has CPU cores pinned via the extra parameters (--cpuset-cpus) Those 3 containers all have the entry in extra parameters Additionally, Radarr also has cores pinned via the GUI Sep 21 00:56:09 undou root: Fix Common Problems: Error: Docker Application radarr has duplicated entries for CPU pinning One of the side effects of having the duplicated entries is that on the CPU pinning page, any changes you make to a container that has something already in extra parameters will appear to not take effect at all. (and they will appear to not save). unRaid's GUI does not add anything to the extra parameters line for pinning, but rather uses a completely different tag. Are you positive that the template you're adding the app from does not already contain the cpu pinning in extra parameters?

https://forums.unraid.net/topic/74260-unraid-os-version-660-available/?page=4&tab=comments#comment-684650