Spritzup

According to the Sonarr dev, the only time it will scan the media (and thus update it) is when the filename changes. I've now confirmed with multiple shows that this is indeed the case. The only shows that were updated were ones where the extension changed (for example, mp4 to mkv) and therefore Sonarr reads it as a filename change. Apparently the only way to have Sonarr rescan everything is to delete and re-add the library, which sort of renders Unmanic less useful for a large number of people... which is unfortunate ~Spritz

Do you happen to know how often these scheduled library changes run? I have some shows from a few days ago now that still haven't updated. ~Spritz

Compliments to @Josh.5, this thing is a beast! Testing it out right now on a smaller library, but it's averaging a 40-50% reduction in file size. The only issue that I'm running into is how to let Sonarrv3 know that the file has been changed to 265? I read the thread and didn't see a solution ~Spritz

So I'm an idiot, and forgot to delete the container after utilizing it. It was fine for a couple of months, and then somehow it started and ran again (just prior to the update to fix this issue) and overwrote my disks. Now the thing is, I edited the xml to install everything on an nvme drive I have... So my question is, how do I get it to boot off the proper drive, rather than the newly created drive? ~Spritz EDIT - I may have resolved it by removing the install disk that is created, and simply leaving the clover image and then the physical disk. Anything wrong with my solution?

Evening all, I'm having an intermittent problem with my containers becoming inaccessible, in that I attempt to access the webpage, but it simply endlessly spins. The after a random amount of time, everything is accessible until it happens again. When this happens, the unRaid GUI is fully accessible, as well as any containers that are not bridged (eg - have a dedicated IP). The only thing I see the in log (though I've attached my full log) is that what I assume are the container ports become disabled. Curiously, I also see it trying to get an IPv6 address, despite the fact that it should be disabled... May 23 14:46:16 Dyson emhttpd: Starting services... May 23 14:46:17 Dyson emhttpd: shcmd (22523): /etc/rc.d/rc.samba restart May 23 14:46:19 Dyson root: Starting Samba: /usr/sbin/smbd -D May 23 14:46:19 Dyson root: /usr/sbin/nmbd -D May 23 14:46:19 Dyson root: /usr/sbin/wsdd May 23 14:46:19 Dyson root: /usr/sbin/winbindd -D May 23 14:46:19 Dyson wsdd[109770]: set_multicast: Failed to set IPv4 multicast May 23 14:46:19 Dyson wsdd[109770]: Failed to add multicast for WSDD: Address already in use May 23 14:46:19 Dyson wsdd[109770]: set_multicast: Failed to set IPv4 multicast May 23 14:46:49 Dyson kernel: veth1bd4b6a: renamed from eth0 May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state May 23 14:46:49 Dyson kernel: device vethdc56c05 left promiscuous mode May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state May 23 14:46:53 Dyson kernel: veth188f45b: renamed from eth0 May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state May 23 14:46:53 Dyson kernel: device vethc70e6f9 left promiscuous mode May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state May 23 14:46:57 Dyson kernel: veth0f85da6: renamed from eth0 May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state May 23 14:46:57 Dyson kernel: device veth9b57cdc left promiscuous mode May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered disabled state May 23 14:59:19 Dyson kernel: device veth79fed20 entered promiscuous mode May 23 14:59:19 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth79fed20: link is not ready May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered forwarding state May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered disabled state May 23 14:59:20 Dyson kernel: eth0: renamed from veth9fce0fd May 23 14:59:20 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth79fed20: link becomes ready May 23 14:59:20 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state May 23 14:59:20 Dyson kernel: docker0: port 4(veth79fed20) entered forwarding state May 23 14:59:46 Dyson kernel: docker0: port 9(veth4bfae45) entered blocking state May 23 14:59:46 Dyson kernel: docker0: port 9(veth4bfae45) entered disabled state May 23 14:59:46 Dyson kernel: device veth4bfae45 entered promiscuous mode May 23 14:59:46 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth4bfae45: link is not ready May 23 14:59:47 Dyson kernel: eth0: renamed from vethc1dbbde May 23 14:59:47 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4bfae45: link becomes ready May 23 14:59:47 Dyson kernel: docker0: port 9(veth4bfae45) entered blocking state May 23 14:59:47 Dyson kernel: docker0: port 9(veth4bfae45) entered forwarding state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered disabled state May 23 15:00:11 Dyson kernel: device veth9a9edae entered promiscuous mode May 23 15:00:11 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth9a9edae: link is not ready May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered forwarding state May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered disabled state May 23 15:00:12 Dyson kernel: eth0: renamed from vethff20ae0 May 23 15:00:12 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9a9edae: link becomes ready May 23 15:00:12 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state Any assistance would be appreciated! ~Spritz dyson-syslog-20200523-2207.zip

Hey @hotio, I just wanted to say that I'm really happy with your Containers. At least for me, the configuration just seems to make sense. That said, I'm running into an issue with your Plex container (likely something I'm doing), where it shows that remote access is not enabled. Likely because it thinks its local IP is on the docker private network (172.x.x.x), while the port forward is obviously to the unRaid IP. Yup, as expected, I'm just an idiot. I had been doing some testing with other Plex containers and had changed my standard port forwarding rule to a random IP... and I forgot to change it back. My apologies. Any thoughts? EDIT2 - Just a thought, because it's not clear. It may be an idea to put in an example of what the format of the "Advertise_IP" variable should be. I had originally put in there the IP, but according to Plex it should be "http://<hostIPAddress>:32400/", which isn't really clear. Thanks! ~Spritz

So in theory, I could delete the variable from the container and simply use path mapping... assuming I configured it correctly from the Web UI? As you said though, this is currently untested. ~Spritz

@binhex just a quick question regarding how you've set your container up for transcoding. What is the purpose of having the "TRANS_DIR" variable, vs just having a path mapping and putting the transcode directory properly in the Plex settings? Thanks you! ~Spritz

Yeah, that looks awesome! Thanks a bunch! ~Spritz

Try changing your NIC to e1000-82545em. ~Spritz

Apologies about a second post prior to getting an answer to my first post, but I've just been thinking. Is it possible to do further tweaking to maximize performance once the VM is built? @SpaceInvaderOne perhaps similar to the windows VM tweaking video you did, but using the assumption that people are building the Mac VM based upon this docker? ~Spritz

Hey all, So I just got finished setting up this docker/VM for the wife and everything is going swimmingly (so far!). I've passed through a Radeon 570, as well as a USB controller without issue. However I have the disk hosted on a NVMe drive and am not seeing the performance I'm expecting. For comparison I'm seeing nearly 4 times the performance on an equivalent Windows 10 VM. I suspect the limiting factor is having to use the SATA interface for the drive... is their anyway to change it so that it's still picked up by Catalina? Thanks in advance! ~Spritz

Great idea, why I didn't think of that! @matto2494, any chance you can modify the banner?

I don't have the skills for this, but would anybody be willing to upgrade these for the new style banner of Unraid? My thoughts were remove the unraid logo, and center up the icons. If one wanted to get real fancy, we could have one banner for Intel, and one for Ryzen. Thanks in advance! ~Spritz

I suspect I know what the issue is, but my CrashPlanPro is stuck at "Waiting for Connection". I'm also running the "LetsEncrypt" container on my box which has port 443 forward to it. I'm guessing it' some sort of conflict? Thanks for any help. ~Spritz

I am using the example that was created, and followed the instructions that were located within. ~Spritz

Hey All, I'm having issue's using Nextcloud with the LetsEncrypt proxy. Basically I can hit the login page to nextcloud without issue, but when I go to login in, I keep getting "504 Gateway Time-out, nginx/1.14.0". Any thoughts on where I should be looking? This was working before. Thanks in advance! ~Spritz

Thanks Squid. This is basically a fresh install, so it was the latest version installed. That said, I double checked and it is up to day --> 2018.01.20b

I just moved to version 6.4 and seem to be having an issue with CA... CA just hangs when trying to update the application list. I've tried setting a static DNS to googles servers, but no such luck. I am seeing the following error in the log and want to rule out CA as the culprit before tearing my network apart. Thanks! Jan 22 08:35:13 SERVERNAME nginx: 2018/01/22 08:35:13 [error] 9096#9096: *61358 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.151, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "SERVERNAME", referrer: "http://SERVERNAME/Apps"

Sonarr keeps just crashing (have to restart to get it to work again) and I see the following error --> at <unknown> <0xffffffff> at (wrapper managed-to-native) object.__icall_wrapper_mono_gc_alloc_vector (intptr,intptr,intptr) [0x00009] in <77c9551943624fd18301ba6f78a841e5>:0 at (wrapper alloc) object.AllocVector (intptr,intptr) [0x000bf] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Xml.XmlEncodedRawTextWriter..ctor (System.IO.TextWriter,System.Xml.XmlWriterSettings) [0x00036] in <d94dcfabccbf4e35a08e6fe5b3f74a7e>:0 at System.Xml.XmlWriterSettings.CreateWriter (System.IO.TextWriter) [0x00041] in <d94dcfabccbf4e35a08e6fe5b3f74a7e>:0 at System.Xml.XmlWriter.Create (System.Text.StringBuilder,System.Xml.XmlWriterSettings) [0x00024] in <d94dcfabccbf4e35a08e6fe5b3f74a7e>:0 at NzbDrone.Core.Extras.Metadata.Consumers.Xbmc.XbmcMetadata.EpisodeMetadata (NzbDrone.Core.Tv.Series,NzbDrone.Core.MediaFiles.EpisodeFile) [0x0006d] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Extras\Metadata\Consumers\Xbmc\XbmcMetadata.cs:210 at NzbDrone.Core.Extras.Metadata.MetadataService.ProcessEpisodeMetadata (NzbDrone.Core.Extras.Metadata.IMetadata,NzbDrone.Core.Tv.Series,NzbDrone.Core.MediaFiles.EpisodeFile,System.Collections.Generic.List`1<NzbDrone.Core.Extras.Metadata.Files.MetadataFile>) [0x0000d] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Extras\Metadata\MetadataService.cs:229 at NzbDrone.Core.Extras.Metadata.MetadataService.CreateAfterSeriesScan (NzbDrone.Core.Tv.Series,System.Collections.Generic.List`1<NzbDrone.Core.MediaFiles.EpisodeFile>) [0x000b8] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Extras\Metadata\MetadataService.cs:75 at NzbDrone.Core.Extras.ExtraService.Handle (NzbDrone.Core.MediaCover.MediaCoversUpdatedEvent) [0x00029] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Extras\ExtraService.cs:112 at NzbDrone.Core.Messaging.Events.EventAggregator.PublishEvent<TEvent_REF> (TEvent_REF) [0x000c3] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Messaging\Events\EventAggregator.cs:56 at NzbDrone.Core.MediaCover.MediaCoverService.HandleAsync (NzbDrone.Core.Tv.Events.SeriesUpdatedEvent) [0x0000c] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\MediaCover\MediaCoverService.cs:169 at NzbDrone.Core.Messaging.Events.EventAggregator/<>c__DisplayClass4_2`1<TEvent_REF>.<PublishEvent>b__1 () [0x00035] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Messaging\Events\EventAggregator.cs:83

So it doesn't matter if I use the same DHCP range that my router is using, since I will be manually forcing an IP? That makes sense... and it won't impact my other containers, unless I use the appropriate switch (--network). Thanks! ~Spritz

So I'm considering doing this to get PiHole working properly. However, I'm concerned with conflicts on with my network DHCP server... is it possible to just assign a static IP and not use a range? Thanks. ~Spritz

So I'm seeing the following error with the plugin "Possibly out of inotify watches". However, I don't have any of the 'problem' plugins installed... the only thing that I can think of causing the problem would be Plex monitoring for file changes, as that seems to use inotify. Here is a list of the plugins I have installed --> CA Auto Update Applications CA Backup/Restore Appdata CA Cleanup Appdata Community Applications Dynamix Cache Directories Dynamix Local Master Dynamix SSD Trim Dynamix System Statistics Dynamix WebGui Fix Common Problems IPMI Support Nerd Tools Open Files Preclear Disks Recycle Bin Tips and Tweaks Unassigned Devices unBalance unRaid Server OS Thanks in advance! ~Spritz

So I'm not sure if this is a Plex Docker issue, or if Plex is just displaying a symptom. It seems though that randomly the media I'm watching will pause for upwards of 30 seconds, and then usually resume without issue. I'm using Rasplex running on a Pi2, with everything hardwired across a gigabit network. My unraid box is a dual 2670 with 128gb of ram, with the transcode directory sitting in memory (though this is for direct play items, so moot point). I've examined the logs, and do not see anything that stands out. Has anybody else had this issue, or can offer some advice? Thanks in advance! ~Spritz