raftrider

Nope, but I didn't try tbh. Everything is working now except for the plex web transcoding.

I can confirm I had a similar issue with the latest nvidia driver and reverting to v530.41.03 solved almost all issues except for the web player transcoding now just hangs no errors on the browser. Card is P2000

Well, there was a plex update 4 days ago, definitely worth checking.

So, quick update. My tests were via plex for mac(2 different macs) and plex web, these still fail. Then noticed remote users transcoding and tried in my apple tv and works fine so for some reason this appears to only be affecting plex web and plex on mac and IOS. I will start looking on the plex forums for a solution for this issue. Thank you guys for the recommendations. In the backend it looks like the transcode stream starts(I can see it with nvtop), then it stops and I get the error in the player. Also tried both h264 and hevc with the same results. Tried removing the plex app from mac and installing again, no changes. If/when I find a solution online I will post back here for reference in case other users might be experiencing the same problem UPDATE: Upgraded to the latest codec again. Now the plex for mac started transcoding but buffers every 3-4 seconds. Interestingly, the plex htpc player for mac, plays and transcodes smoothly so this is definitely an issue specifically with the desktop plex player for mac and well the web player which tbh I do not use.

I just upgraded from 6.11.5 to 6.12.3. Followed instructions from this thread to troubleshoot before posting this. Downloaded the latest driver (v535.86.05), rebooted for the upgrade. The plex GPU hw transcoding stopped working. Removed the plugin and plex. Rebooted. Reinstalled the nvidia plugin with driver v535.86.05, rebooted. Recreated plex container. Same error while transcoding, screen flashes a couple of times and get Error code: 4294967279. Switched to driver v530.41.03 and rebooted. Same error again. Diagnostics attached. Thanks in advance! Sat Jul 22 18:41:23 2023 +---------------------------------------------------------------------------------------+ | NVIDIA-SMI 530.41.03 Driver Version: 530.41.03 CUDA Version: 12.1 | |-----------------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+======================+======================| | 0 Quadro P2000 Off| 00000000:03:00.0 Off | N/A | | 51% 42C P8 7W / 75W| 2MiB / 5120MiB | 0% Default | | | | N/A | +-----------------------------------------+----------------------+----------------------+ +---------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=======================================================================================| | No running processes found | +---------------------------------------------------------------------------------------+ tower-diagnostics-20230722-1844.zip

I found the culprit. I removed atop as it kept filling up the log partition. For some reason the process was still running and prevented the file to be deleted. ps aux|grep atop root 11425 0.0 0.0 3904 1904 pts/0 S+ 18:02 0:00 grep atop root 17720 0.1 0.0 23324 18648 ? S<L Jan13 68:26 /usr/bin/atop -a -R -w /var/log/atop/atop_20220113 600 kill -9 17720 df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 384M 5.1M 379M 2% /var/log

root@Tower:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 384M 165M 220M 43% /var/log root@Tower:~# du -sh /var/log 7.2M /var/log prior to this I had to increase the size of the tmpfs ramdisk mount -o remount,size=384m /var/log tower-diagnostics-20220206-1433.zip

Is there any work being performed on a driver for Nuvoton NCT6681D/NCT6682D eSIO? I have a Thinkstation D30. Any assistance will be greatly appreciated.

Yeah, uncertain why it didn't. One container was on unraid, the other was on ubuntu 18.04 but managed via portainer, both had the same issue.

I found the issue. It was this commit https://github.com/binhex/arch-qbittorrentvpn/commit/6c1d97b14469959bcc55829607c244b95ed6781a and I was still using the PIA DNS. Solved on both containers after removing the PIA DNS addresses.

The latest: docker pull binhex/arch-qbittorrentvpn:latest latest: Pulling from binhex/arch-qbittorrentvpn Digest: sha256:2e8b46305b92feb25351f72ab264e96f094b5b8699d6bd1adac36248b93fd03f Status: Image is up to date for binhex/arch-qbittorrentvpn:latest docker.io/binhex/arch-qbittorrentvpn:latest

My container keeps doing the same thing. Funny thing is one of the hosts where this is happening is not even running unraid but both are having the same issues. Can someone point me in the right direction please? 2021-11-18 07:44:24,631 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-11-18 07:44:24,631 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-11-18 07:44:24,631 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-11-18 07:44:24,632 DEBG 'watchdog-script' stdout output: [info] qBittorrent config file already exists, skipping copy [info] Removing session lock file (if it exists)... 2021-11-18 07:44:24,637 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2021-11-18 07:44:24,642 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2021-11-18 07:44:24,649 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2021-11-18 07:44:24,656 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2021-11-18 07:44:24,661 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2021-11-18 07:44:24,666 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2021-11-18 07:44:24,673 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2021-11-18 07:44:24,680 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2021-11-18 07:45:22,988 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 12 retries left [info] Retrying in 10 secs...

I upgraded today. One instance had already failed but I didn't notice until I upgraded this one. Attached is my supervisord.log supervisord.log Wednesday, November 17, 2021 - update. I tried removing the container and recreating it and get the same error message. Did anything pop to you in the log?

This is still not working for me. both my qbittorrent containers show this error: 2021-11-16 14:10:51,651 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 12 retries left [info] Retrying in 10 secs...

@pwm read my post again. I have a unifi switch 16-150w with jumbo frames enabled(switch has terminal/ssh access to test that jumbo works). I have a proxmox server with jumbo frames enabled. The server that now has unraid previously had proxmox as well with jumbo frames enabled and worked perfectly fine. The issue is with unraid, that is just a fact. My boss has the same version of unraid on his server and jumbo frames don't work either.