allanp81

Did you ever get this working? I can't get it working either.

I've tried using this docker after migrating my account and for some reason it won't let me login. The username and password work fine via their webpage.

Ah, I see why, because that directory would otherwise be created under /tmp?

Why would that create a share named httpserver if you don't mind me asking?

This is the output from updating the docker: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="duplicati" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8200:8200/tcp -v "/mnt/cache/":"/tmp":rw -v "/mnt/disks/BUFFALO_External_HDD/Backup/duplicati/":"/backups":rw,slave -v "/mnt/user/P/":"/source":ro,slave -v "/mnt/cache/appdata/duplicati":"/config":rw linuxserver/duplicati a1b4a215c1f22c23e12a7d5675ab3d7f83eb0a9590e97008c63faeb2bbc3840b I'm not sure if this is what you mean by run command. If I bring up the log from the row under docker it shows me: I have about 10 other dockers and don't seem to have this issue with any others.

This docker seems to create a public share named "HttpServer" whenever it starts that the fix common errors plugin then flags up as a problem. Any one know this share is created and what its purpose is?

I figured it out eventually, I found the section in the source where SMB paths are mounted as cifs. I couldn't figure out the right syntax on my own as I was getting odd filenames appearing when mounting without the correct switches.

I had a script that ran the rc.unassigned script from the unassigned drivers plugin. The path to is something like /usr/local/plugins. This works fine if I manually kick the script off but fails when the script runs via a schedule, it claims the path doesn't exist.

Hmm, that's what I thought but I seem to get different results depending on how the script is initiated.

When running a user script manually, does it run as a different user versus being run via a schedule?

Can anyone tell me how this plugin uses smbclient to mount an smb share? I'm trying to utilise the rc.unassigned script to mount the listed share via a cs user script but it seems to fail with the path. If I can work out the smbclient syntax instead then it won't matter. I have trawled through the source on github but struggling to see how it works.

For me personally, I see massive latency spikes if I change it to anything suggested in this thread. Leaving it on cache='writeback' gives me greens the whole time.

Storage (obviously) Dockers: -cAdvisor -couchpotato -crashplan -dolphin -emby -handbrake -htpcmanager -letsencrypt -mysql -sabnzbd -sickbeard Windows 7 VM Ubuntu VM

I've tried several tuner devices and none of them have ever worked when passed through unfortunately. They all exhibit problems that manifests as dropped packets when tuning to dvb-t or dvb-t2. I've ever tried USB tuners and had the same issue, although I haven't tried using a dedicated USB controller and isolating it from Unraid.

I've tried this and like the potential but nothing I set seems to be retained for some reason and I can't see anything under any of the logs to suggest why.

Would any of this help me to get my tv tuner card working properly in a vm? While I can get the card recognised in the VM, I always have signal issues when tuning.

Still struggling to get Emby to work properly when playing back music. Bizarrely movies work fine but music and TV don't. Can anyone share their configs that work for them?

How are you configuring emby to be on http://192.168.121.10:8096/emby? I can't see any settings under emby itself to set the base path like you can in others things such as sickbeard/couch potato etc.

I'm struggling getting emby to work properly. I can access the server no problem externally but only film playback seems to work, music and TV both fail and it seems to be because it's then trying to access the necessary pages via the default port of 8096. I added this to my config: location ^~ /emby { #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.7.11:8096; } Although that allows me to access remotely and log in and play a film, it fails to play music with things like this in the emby log: HTTP Response 404 to x.x.x.x. Time: 0ms. http://myserver.com:8096/embywebsocket?deviceId=77d035c190408a514627dd623c86d962941ac660 (i've replaced IP with x.x.x.x. and changed my domain to myserver.com incase anyone points that out. Can anyone shed some light on what I might need to do to make this work? I guess part of the issue is that with emby there is no way to change the base path of the server.

latencymon: http://www.resplendence.com/latencymon dpc latency checker: http://www.thesycon.de/eng/latency_check.shtml I've done a bit of experimenting again today. If I assign the emulatorpin to a core that is shared with the rest of unraid/dockers then I get latency spikes all over the place. If I assign the emulator pin to an isolated core then for the most part it's fine, green all of the way and no issues with youtube or playing games. I still have issues trying to pass through a DVB-T2 tuner card though but that might be an issue with that particular card or drivers so I might order a different make card at some point and try that instead.

Yes I don't understand it either, but if I don't assign an isolated core to the emulator pin I see spikes of latency in the Windows VM.

I've just done it with a very simple html5 menu, works great.

I've noticed another oddity that may be just the way it's reported rather than an actual issue: When copying files within the VM locally or across the network I see sudden huges spikes in latency that stop the minute copying has finished. I've tried switching controllers from virtio to SATA, reverting to older virtio drivers and even switching between q35 and i440fx. It's strange, if I have a youtube video playing at the same time it doesn't seem to cause any issues so wonder what causes Windows to think it has massive latency spikes. *EDIT* Strangely it appears that swapping out the AMD graphics card (HD 5450) for another cheap Nvidia card (GT710) seems to have solved this. How odd!

I assigned emulatorpin to 6 and 14 with the win7 VM on 7 and 15 and that worked great. All 4 of those threads are isolated in my boot config. I then experimented and assigned emulatorpin to 6 and then 7,14 and 15 to the VM. This again seems to work great, no latency. The basic outcome of this, is that for me personally then only way I can get a VM with no latency issues is to pin the emulatorpin to isolated cores. If I assign to anything else it's generally ok but can be affected by other tasks such as things running under dockers, even if those dockers are set to not use the cores I've allocated to the VM.

Seems like I have solved this by setting the emulatorpin to isolated cores. The vm has now run all night without a single spike of latency.