dan91

No unraid staff reply yet? Its a pritty big issue?

Hi, Upgraded from 6.12.3 and having issues with my dockers using custom ipv6 addresses. I'm getting this error: docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. These are the settings which worked fine on 16.12.3: docker run -d --name='binhex-sabnzbd' --net='br0' --ip='192.168.93.193' --ip6='2a02:restofip' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="binhex-sabnzbd" -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8090'='9090' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png' -v '/mnt/disks/WDC_1TB_BLACK/Sab':'/land':'rw,slave' -v '/mnt/cache/appdata/sab/':'/config':'rw' 'binhex/arch-sabnzbd:latest' 366a3580aae5540d218ef2281456d083994bf8f7998a1cb51b05e378cd705ad6 docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. Am I missing something? Going to have to roll back for now. If i remove the specified IPv6 Address it works fine. Thanks, Daniel

Hi Xploit with a single IP for blizzard i get about 1-3 MB/s on initial download with the amount of IP's from my initial post I mostly max out my download speed 8MB/s. If you remove all the extra IP's and just try 1 extra IP does your cache still work? (basically are the extra IP's functioning correctly) Can you see them in ip addr on the command prompt on unraid and are you using HOST mode for the docker container? Are you downloading to spinning disks or an SSD? If spinning are you able to swap to an SSD just for testing the blizzard download? You may be hitting a limitation on disk access times which may be why increasing your slice size helped. (How you get more througput from one large file than loads of small ones)

I have managed to do this but you have to make a few changes to the setup. I use "Host" for the network setting for the docker container rather than giving it its own IP in Bridge mode. This ensures all IP's on your unraid box adapder pass through to it. Downside you cant have 80 443 or 53 listening on these. This mainly effects the unraid web ui which runs on 443 by default. To get round this move the web gui to another port (i used 444) this does mean to access the webui you will need to specify the port e.g. sdjklfhsdjfgh76786sdwe87r5sdf.unraid.net:444 Settings -> Identification -> Management Access to change port First step is to assign more IP address' to the unraid network adapter. You need to check on your router for its DHCP range and assign something outside of this range (which is not in use) or put a manual reservation in to a dummy mac address for the IP's your looking to use. (Sorry cant really help more with this so many different types of routers). For example my DHCP range runs 192.168.1.2 - 192.168.1.190 192.168.93.5 is assiged to my Unraid box as a manual reservation so its alway the same. I have decided to use 192.168.1.242 - 192.168.1.248 as the additional IP's as they are outside the DHCP range (so wont be given to something else and I know they are not in use) Now we have the list of IP's we are going to use we need to assign them to the interface. To ensure this percists through a reboot of the unraid box we need to install the User Scripts plugin made by Andrew Zawadzki (Search in the apps store) Once added go to Settings > User scripts (at the bottom under user utilities) New Script and give it a name i picked IPAddresses Click on the Cog next to the script you just made and go edit script Then in my example i entered the following into the script box; #!/bin/bash ip address add 192.168.1.243/24 dev br0 ip address add 192.168.1.244/24 dev br0 ip address add 192.168.1.245/24 dev br0 ip address add 192.168.1.246/24 dev br0 ip address add 192.168.1.247/24 dev br0 ip address add 192.168.1.248/24 dev br0 Note i left out the 192.168.1.5 as it will already be assigned automatically. Your br0 (network adapter) might be different run "ip addr" in the command prompt shell on the server and look for the network adapter that has IP address' that match your local network. Save the script Change the Schedule to First Array start (we only need to apply it once per reboot) and apply the changes. You can also manually run the script to add the ip addreses right now which you will need to do this first time (or reboot). running "ip addr" in the shell prompt should now show all these IP's also linked to that network adaper (this is important!) And you should be able to ping them from your pc! Now we need to tell the dns server in the docker container about these ip addresses. Edit LAN Cache bundle docker settings Ensure network type is Host (this will fail if you didnt move your Mangement port!) First lets just do a test and remove the IP currently in LANCACHE_IP to one of the new ones e.g. for me 192.168.1.243 Flush your dns on your PC to make sure Command prompt "ipconfig /flushdns" and then "nslookup update1.dota2.wmsj.cn" this is just an example address that should be overwritten by the steamcache dns we should get that IP address we changed too. Test your cache and make sure it sill working. If so lets put all the addresses in. Edit lancache bundle again For lancache IP put in all the IP addresses seperated by a space e.g; so i entered them all 192.168.1.5 192.168.1.243 192.168.1.244 192.168.1.245 192.168.1.246 192.168.1.247 192.168.1.248 You can leave DNS_BIND as the single IP Apply the changes. Command prompt "ipconfig /flushdns" and then On the PC in a command prompt run "nslookup update1.dota2.wmsj.cn" this is just an example address that should be overwritten by the steamcache dns. You should get a result including all your extra IP's. Make sure everything is working. Using this i get 100MB/s - 115MB/s which seems to be the limit of my Gigabit connection between unraid and my pc. When downloading ARMA 2 as an example. (I'm using spinning disks for the cache so they are likely the next limit)

Hi, are you experiencing high CPU usage after disconnecting from RDP to the VM? If so its likely a problem due to the 1903 update in windows. See link below for a work around; https://borncity.com/win/2019/08/28/windows-10-v1903-rdp-dwm-exe-causes-high-cpu-load-freezes-vms/ If thats not the issue then ignore this post. I had this issue with 3 of my VM's so just making people aware!

Hi, are they windows VM's? Just double check your not experiencing this issue; https://borncity.com/win/2019/08/28/windows-10-v1903-rdp-dwm-exe-causes-high-cpu-load-freezes-vms/

Wrong or Long? 🤣😂 After the problem I had with the 512 char limit ive shortened it now to under 260!

Hi, It doesnt do anything unfortunately it seems to just hang. tower-diagnostics-20191016-1851.zip

Hi please see diagnostics attached but that is as far as it gets it just hangs. Would it be anything to do with i'm using the second password on my LUKS volume due to the post I made in the main thread? tower-diagnostics-20191016-0642.zip

Hi, Sorry I mean the unraid web page encryption passphrase limits it to 512 characters (Or did on the old version) any extra is not included so when I created the encrypted array even though I pasted more than that it was chopped to 512 chars. Which is why I struggled to get the paste into a file and mount using the keyfile command working as I was entering the full password. I first had to mount the array normally (entering the passphrase in the web ui) and look at the keyfile it made and see what was chopped off the end. After doing that I was able to mount it fine using a copy pasted into a file and using the keyfile what I meant by 2 was something in my old passphrase stops the new way you are doing it from working. I confirmed this seems to be a problem with cryptosetup as I tried to mount one of my unassigned devices manually using the cryptsetup luksOpen command. When prompted to enter the password and I enter the password which is now correct and works fine in the keyfile it fails to load. Leaving me to think that something in my password is not supported using that method and which is why unraid fails to mount using the new method of not making a keyfile. Hopefully this makes a bit more sense? Thanks

Had an issue with the change to encryption away from the entering you passphrase makes a keyfile and mounts using that. It seems my passphrase is; 1) too long 2) has characters that dont translate into the standard password prompt luks would provide these are some characters which were in my password as an example; Ö®ëÆ This doesnt really seem to be a bug in unraid as after testing I cannot mount the drive by running it manually on the disk with this password it has to go into a keyfile first (even though i normally just paste the phrase into the webui) which would normally put it in a keyfile and mount that way up until this version which is why ive only just noticed the problem. Just spent 5 mins adding another key to all my disks and now no issues except for unassigned devices which i posted in the other thread. This is more of an info post for anyone else who may experience the issue!

Hi, I have updated to the newiest version of Unassigned devices and on RC1 When it trys to map my unassigned devices it does the following but then does not do anything, the array does not finish mounting so none of my services start. Oct 15 19:17:36 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Oct 15 19:17:36 Tower unassigned.devices: Adding disk '/dev/mapper/Crucial_1TB'... Oct 15 19:17:36 Tower unassigned.devices: luksOpen: key file not found - using emcmd to open: 'cmdCryptsetup=luksOpen /dev/sdk1 Crucial_1TB --allow-discards'

Hi, For me I found the issue seemed to be the plugin Dynamix Cache Dirs once i removed that i was ok.

Hi all hope someone can help, having an issue where SMB stops responding. This can easily be seen on a VM which uses network drives as a seed location. It will be seeding at full speed then simply halt seeding. This also co-insides with the network shares not responding on other machines and files playing in kodi stopping. This lasts a few seconds to a few minutes then everything resumes. Ive read about some issue's being file system and XFS not supposedly having this issue however all my disks are using XFS. Also attached the diagnostics thanks. i5-3570K 32 GB Ram 14 3TB drives (2 Parity) 500GB SSD cache Couple of unassigned drives 1TB x2. pluto-diagnostics-20180521-1702.zip

@NeoDudeHi, this is required as i wish to cache requests on port 80 but simply proxy requests on SSL. (Steamcache essentialy). They do this with two different docker images one caching the requests the other running sniproxy on 443. I need to be able to assign them the same IP so things like the steam store and friends lists function but game downloads go though the cache.

Sorry to bump this but anyone have any input?

Hi all hope someone can maybe point me in the right direction. I can see you can assign a specific IP to a docker image however you cannot then use this same ip on another for a different port. I have groups of 2 docker images that need to be on the same IP but different IP's between groups. Example Docker 1 - 192.168.0.4:80 Docker 2 - 192.168.0.4:443 Docker 3 - 192.168.0.5:80 Docker 4 - 192.168.0.5:443 I thought maybe assigning these IP addresses to unraid then choosing to bridge to them rather than the default IP of unraid. Although honestly i'm kind of stumped on Unraid. On a general Linux system you can add extra IP's to interfaces and then pass them through to docker. e.g. doing this on the host iface eth0 inet static address 192.168.0.4 netmask 255.255.255.0 gateway 192.168.0.1 iface eth0:0 inet static address 192.168.0.5 netmask 255.255.255.0 Then starting the dockers like so docker run (whatever it is your running) -p 192.168.0.4:80:80 docker run (whatever it is your running) -p 192.168.0.4:443:443 docker run (whatever it is your running) -p 192.168.0.5:80:80 docker run (whatever it is your running) -p 192.168.0.5:443:443 Is it possible to do something like this on Unraid? Anyone point me in the right direction, Thanks!

Moving my appdata / config folders from an unattached device to the cache ssd seems to have solved the issue. Although i'm unsure why it would be an issue? Thanks for your help

Hi thanks for the reply hope this helps pluto-diagnostics-20180404-0021.zip

Hi currently on the trial dont know if that matters? Dockers start up ok and run ok but restarting or stopping them they hang forever with this in the logs. Any ideas what would be causing them to be so unresponsive to shutdowns / restarts. All my images and / configs are on an Unassigned SSD to rule out the array or anything else. PLUTO nginx: 2018/04/04 00:31:28 [error] 23399#23399: *487933 upstream timed out (110: Connection timed out) while reading upstream Looking at a log of a docker shutting down they seem to hang on the syncing disks? 2018-04-04 00:39:51,729 INFO - NZBHydra2 wrapper shutdown request. Terminating main process gracefully [cont-finish.d] executing container finish scripts... 2018-04-04 00:39:51.735 INFO --- [ Thread-5] org.nzbhydra.NzbHydra : Shutting down [cont-finish.d] done. [s6-finish] syncing disks.