Cairxoxo

Do I run this in a terminal window? I thought mcelog saved into the syslog directly so was in the diagnostics I downloaded.

First time I've seen this before, my regularly scheduled run of FCP threw out this error: I thankfully do have mcelog installed, and have attached my diagnostics here. I had a look through the syslog but didn't notice anything immediately. Any help would be greatly appreciated! I'm running a Dell R510 with 6 x 6TB WD60EFRX HDDs + a Samsung 850 EVO 250GB SSD for cache. tower-diagnostics-20200628-2330.zip

Don’t seed from google drive - you’ll most likely receive an API ban. Also I’ve seen most people recommend that if you do have a large amount of local storage, keep 4K content local too. It sounds like in your position, with 84TB of local storage and from the sounds of it no real need to increase that exponentially, this just isn’t for you.

I also only have 40mbps upload and it works great with my setup. Locally, content is instant and there is no difference from when content was stored physically locally. Remote users if they also a decent connection, everything direct plays just fine. After some tweaking and testing I've ended up limiting remote connections to 8mbps 1080p in Plex, which does transcode most content, but not a worry for me with GPU hardware transcoding. The initial upload of my content took a longgggg time (literally weeks) but it has been worth it a hundred times over already by how much extra content and at higher qualities I've been able to grab for my own personal use (100mbps down allows me to stream even high bitrate 1080p content with no issues. The only thing to consider is that you cannot effectively stream with that download while torrenting content at the same time unless you limit your download speed, plex will just stutter a lot. This however isn't a big problem for me as most of my downloads occur during the working day anyway due to my timezone.

Diagnostics here tower-diagnostics-20190311-1354.zip

Hi everyone, I can no longer start any VMs at all, they state "Execution Error: internal error: qemu unexpectedly closed the monitor: qemu: qemu_thread_create: Resource temporarily unavailable" when trying to start them. The VM service says it's running in the unRAID GUI, but the LibVirt log shows:: 2019-03-11 02:35:56.032+0000: 9697: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer 2019-03-11 02:35:56.032+0000: 9697: error : qemuProcessReportLogError:1928 : internal error: qemu unexpectedly closed the monitor: qemu: qemu_thread_create: Resource temporarily unavailable The VM itself that won't start has this in the log: 2019-03-11 02:35:55.841+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Hass.io,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-Hass.io/master-key.aes -machine pc-q35-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/5b510e31-5996-7354-07db-bd67fcb0c307_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2048 -realtime mlock=off -smp 24,sockets=1,cores=12,threads=2 -uuid 5b510e31-5996-7354-07db-bd67fcb0c307 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=25,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0io-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2019-03-11 02:35:55.841+0000: Domain id=3 is tainted: high-privileges 2019-03-11 02:35:55.841+0000: Domain id=3 is tainted: host-cpu 2019-03-11T02:35:55.945615Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) qemu: qemu_thread_create: Resource temporarily unavailable 2019-03-11 02:35:56.033+0000: shutting down, reason=failed I've tried rebooting multiple times, each time the VM will come up just fine with the service, then both will crash and stay that way after a period of time.

Removing network.cfg and rebooting to generate a new one seems to have done the trick - thanks for your help.

Just saw this edit - it was failing to pull any info. I can't remember the error message exactly but it wouldn't connect. This was after my first reboot, I'll try again after rebooting with a refreshed network.cfg tonight.

I had tried a reboot and it made no difference. Docker service was still enabled, though. I’ll try again tonight with a renamed network.cfg though. Just so I’m sure, that will cause the OS to generate a new network.cfg file on boot correct?

I am the OP. I assumed the issue with services is related because if my server cannot reach outside of the network none of my services/containers can either, right? I’ll try that command when I get home tonight but I assume it’ll fail - Fix Common Problems was saying it couldn’t reach github.

Hey yep I’ve got my unraid box running with googles DNS already as static. Switching to automatic and pulling DNS settings from my router appeared to make no difference. I’ve left for work now but before I did, I restarted my whole network stack again and it made no change. Still cannot ping unraid IP from outside of network, and my web server (running from letsencrypt) container is down. All services running in containers cannot be accessed (Plex, Sonarr etc) outside the network, and they have no access to the outside of the network.

Yep gateway was set to IP of router (192.168.1.1) - router and switch have both been reset multiple times. I didn’t touch the modem yet but it’s separate hardware and isn’t doing any routing at all.

Hi guys, So as the title states, my server cannot access anything outside the local network. My overall internet connection is fine, every single other device on my network is having no issues at all. I've tried switching between automatic and static IP/DNS (using Google DNS) and seems to make no difference. My diagnostics are attached, any help would be appreciated as I'm running out of ideas here. tower-diagnostics-20180822-2151.zip

Very keen to update to this for the IPS/IDS dashboard.

Yep, this did the trick with radarr. Was able to get it connected and tested successful. Radarr passed a torrent through to it no problem, but now the completed download handling isn't working. Doesn't detect a video file in the downloaded directory, even though it's definitely there.

Having trouble connecting Sonarr/Radarr to the Flood UI using this docker... any help would be appreciated. Tried a heap of different stuff and it just won't pass the Testing phase at all.