FalconX

Can confirm - had this happened to me today. Clicked the "Update All" button, it updated the containers and got stuck in a loop where it would keep trying every single one again. Refreshing didn't solve it either, as the logs still kept telling me containers were getting updated. Had to do a complete restart of the server. I'm on Version: 6.11.1

I use the SSD Plex (metadeta, config etc), nzbget unpacking and I have one VM disk on there which is not currently being utilized.

As requested. Thanks!

Every since a few updates ago, I've been getting the following errors in my logs every now and then regarding my UD ssd. The SSD is about 2 years old with a lot of writes but I don't see any other issues with it, SMART reports are all ok. Should I look at replacing it? Thoughts?

Is there an option within UD to keep the drives spinning 100% of the time? I have a few drives that I write to periodically and they spin down after a period of time, and when my application goes to write to it, it gets a write error because the drive takes a bit to spin up.

Well either, or both of those solutions appears to have fixed my issue. Much appreciated @AnnabellaRenee87 @1812 !

I've added append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot to my syslinux.cfg Unfortunately my diagnostics do not say anything since unraid crashes and won't dump a diagnostics file. The last thing that shows up on the log is this: php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it Plex,Sonarr,Radarr,LetsEncrypt,Organizr,Nextcloud,Pihole,rtorrentvpn,tautulli,unifi,unms,ddclient,jackett,mariadb,netdata are all running on the server. System usually sits at 10% cpu load and memory at 24% I've enabled MSI interrupts (it was off) Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ I will let it run overnight again and try shutting down tomorrow. Thanks for the suggestions!

Posting here as I didn't get much luck in General support. Hey Everyone, So recently I've started having issues with my Windows 10 VM. Every time I send a shutdown signal from the VM list to shutdown the VM (or even if I go and shutdown from the windowsitself) it completely crashes unRaid. The webgui becomes unresponsive and I cannot ssh into my tower. I have to force shutdown the server by holding down the power button. This started happening shortly after I setup the GPU pass-through (nvidia GT 710) to the windows VM. Before this, I could shut it down no problem. Not sure if this is related or not. Things I have tried: Assign more RAM to the VM (8GB currently) (non gaming VM, just running Blue Iris and a screen capture) Increase vdisk size Increase core count (5 cores assigned, 10 threads) Change initial memory to match max memory (8GB) Turned off Hyper - V Used a GT 710 Graphics ROM BIOS (The GPU was working fine without this) Changed: Disk Cache 'vm.dirty_background_ratio' (%): 1 Disk Cache 'vm.dirty_ratio' (%): 2 The VM task manager shows 2GB used out of 8GB assigned to it, this can't be a memory issue can it? For the life of me I cannot figure this out. I can't capture any syslog because everything crashes before anything is able to be written. The only thing that will occasionally show up in the syslog when shutting the VM down is the following: php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it The VM will boot normally and if I shut it down within a few minutes, it shuts down no problem. This only happens when I try to shut it down the following day or when it has been up and running for awhile. System: Supermicro - X8DTL Dual L5640's 40GB RAM Windows 10 VM xml Any help would be greatly appreciated. Thank you! Update: I spun a new Win10 VM install with the Nvdia GT 710 pass through (4 cores, 4GB ram). The GPU shows up fine on device manager once windows installed the drivers for it. No issues there. Left it running overnight again. Logged into the VM this morning, shutdown the VM and unraid webGUI slowly starts to hang, then completely becomes unresponsive. No SSH no GUI. I had the syslog window open, the only message that came up again: php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it Tried to log in through IPMI and execute a graceful shutdown but it just froze after this message: gracefully shutting down php-fpm.................................................failed force quitting and then it just hung there for 15 minutes before I forcefully shut it off. I don't know if I'm leaking memory somewhere, I'm almost certain it has something to do with the GPU passthrough. I also tried using Fix Common Problems troubleshooting mode but when it crashes, it doesn't even up dumping a syslog or a tail log at all. Not sure where to go from here...

I am constantly getting these messages in the log. It doesn't lock up or anything, Plex still runs fine, but I do have the occasional hiccup where I have to restart the stream on my nvidia Shield. /mnt/user/media/ Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 Starting Avahi daemon Daemon already running on PID 276 and also this at the beginning of docker startup dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

This worked for me but I am having permission issues with Sonarr/Radarr when importing the extracted file. The extracted file reverts back to a umask of 0600 and therefore is unable to read and move the file across. I tried incorporating "chmod -R 777 %R" in the syntax but it keeps breaking it everytime. Maybe I'm just not formatting it right: unrar x "%F/*.r*" "%F/" chmod -R 775 "%R" Any suggestions? Thanks.

Having the autodl config externally is great. Works perfect now thanks!

Would you be able to share how you set this up? I would like to also implement Geo blocking. Thanks.

Is it safe to upgrade again or should I wait until your next release? Thank you.

Something definitely went awry. I cleared the autodl-issri completely and added the tracker info manually for the one that was having problems. The second I put in the tracker information below through the webgui as per the format I had before (uid=XXXX; pass=XXXXX) [options] gui-server-port = 12345 gui-server-password = autodl-irssi [tracker XXXX] cookie = uid=XXXXX; pass=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX force-ssl = true ...is when I started getting the errors below. This is the same setup I had before, I just manually inputted the information through the webgui instead of loading a config file. 2017/11/02 18:44:25 [error] 122#122: *740 FastCGI sent in stderr: "PHP message: PHP Warning: syntax error, unexpected '=' in /home/nobody/.autodl/autodl.cfg on line 6 in /usr/share/webapps/rutorrent/plugins/autodl-irssi/getConf.php on line 54" while reading response header from upstream, client: 192.168.1.2, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=400278392&_=1509662415529 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.10:9080", referrer: "http://192.168.1.10:9080/" It seems there is an extra syntax somewhere and it's throwing off the config file. I'm not sure. I will keep troubleshooting. Thanks for the help! edit: if there is a way I can rollback to 0.9.6-3-146 build please advise how to. edit2: I've managed to rollback to 0.9.6-3-146 and autodl.cfg file is working properly now. I will wait to see if other uses experience similar issues before trying to upgrade again.

I just did it now and I am getting a syntax error. This was a fresh pull about 5 minutes ago. 2017/11/02 18:13:24 [error] 105#105: *1 FastCGI sent in stderr: "PHP message: PHP Warning: syntax error, unexpected '=' in /home/nobody/.autodl/autodl.cfg on line 29 Edit: This error occurred only after loading my autodl.cfg backup file for my filters/trackers.