lespaul

I am having a similar issue. Googling the dmesg entries brought me here, as my syslog had similar messages. This all started when I upgraded from 6.12.8 to 6.12.14. After upgrading, I could not mount any unraid exported NFS shares no matter what I tried. I downgraded to 6.12.9 and NFS seemed to work fine for about half a day then I started getting those syslog messages and NFS became unresponsive. I have now downgraded back to 6.12.8 and NFS is working fine for now.

Having the same issue myself. emby is running very slow. Unfortunately I don't have a solution yet.

Count me among the dead. My ISP blocks port 80 so httpval doesn't seem to work. Not really sure what to do?

I upgraded to 6.4 and it screwed up my reverse proxy setup after adding the new cert to unraid itself. I saw earlier in this thread the suggestion to give the letsencrypt docker its own IP and to forward 443 to the new IP. This fixed it not loading, but I still couldn't access some of my dockers (emby, ubooquity, etc) via my duckdns reverse proxy. I then found that giving each docker its own IP address and updating the "nginx\site-confs\default" file with the new addresses fixed the issue. Is this the "correct" way of doing things or is there a better way?

edit: installed update. working great now. thanks! Still getting this error with the latest version. Has the update not been pushed out yet?

Is there a way to change the autowatch frequency? It seems to be random in how long it will take to grab a torrent from my watch folder. Sometimes it's a few minutes, and other times it's 10 minutes or more.. edit: answered my own question. first: docker exec -i -t rutorrent bash then vi /var/www/localhost/rutorrent/plugins/autotools/conf.php Change $autowatch_interval = 300; to whatever you want. I changed mine to 30 seconds. Type :wq to save. This setting will survive a container restart, but it will revert back to 300 seconds anytime the container is updated or if you edit container settings so you'll need to do these steps again in those situations.

I am getting this as well. I'm on 6.2rc4

Just updated to 6.2rc4. I was running 6.1.9. I previously had my docker.img and appdata on an SSD mounted with the unassigned devices plugin. The docker.img is not recognized now. I tried deleting it and recreating but it would not create a docker.img on the ssd. I put in the path to the ssd, click apply, and nothing happens. I tried creating a docker.img on the cache drive and it was successful. I deleted that image and tried again on the ssd, but no luck. I'd rather use the SSD for dockers, otherwise the cache drive stays spun up all the time because of the dockers I use. edit: I'm just going to use the SSD as a cache drive and add the former cache drive to the array.