musicking

Anyone else seeing this since the upgrade? 551 nobody 20 0 723776 52780 32616 R 99.9 0.1 12:27.18 qbittorrent-nox High CPU usage on Unraid 7.2.6 with the latest qbittorrent 5.2 Update Apparently it's a bug related to RSS refresh interval introduced in #22448 . When RSS reader is enabled but no feed is configured, it enters a busy infinite loop. Workaround: You can disable RSS or add a feed to resolve this.

Even after deleting the lockfile to get things running, it seems to consume more CPU than usual. It has one of my cores pinned. Might roll back until this gets sorted.

Thank you. I have applied the update and your suggestions

I've tried all this and I can't get it working. I just get: The application URL has been now updated. Reload the page or click here to proceed. And I can't get past this page. I was able to fix this with NGINX config tweaking.

Well, after way too many hours, I think my card is failing. Purchased an Intel ARC a380 for transcoding and hopefully won't see anymore issues with "no devices found".

You added port 8181 in the Unraid template and then went to https://IP:8181 and it was still an issue? You can update your webURL in the template as well to reflect HTTPS and port 8181

Make sure you add port 8181 in your docker template for HTTPS to start working/be accessible Make sure you add port 8181 in your docker template for HTTPS to start working/be accessible

Still showing problems :(

Errors are still showing up. What I've done since: Upgraded my BIOS (Had to use a BETA to get C.A.M) Factory reset BIOS Disabled CSM Enabled Above 4G Decoding Enabled C.A.M (Clever Access Memory) -- Also known as Resizable Bar I will give it a few more days to see if the logs are clean.

So far, logs are clear for 24 hours after changing: Boot > CSM to Disable. Will report back after a couple days.

I'm glad I'm not alone with these errors as I keep on having them. Card works perfectly for awhile and then keeps "disconnecting" and stopping docker containers that use the card (Plex and TDARR) and starting them back up seems to stable things out for a bit. It's almost like too many requests to the card causes it to lock up :(

Well, errors returned in logs and device vanishes off and on :( Thought I fixed it. I will try a new flash drive at some point.

At least you are up and running. So far removing the GPU statistics plug-in seems to have helped my situation.

Pretty sure I'm having the same issue. Someone else started from scratch on 7.1.3 and it fixed the issue. I don't want to do that. You ever upgrade and find a fix?

This gives me hope, but I rather not completely restore. I can rebuild the flash, but I would be restoring my backup and might not help. Would be nice to know what on the flash is causing it. UPDATE - Without GPU statistics installed, system is faster and no more error messages. I will wait and see what happens.

Hello, Lately I have been getting this: Jun 24 11:57:43 MediaTank kernel: NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x51:884) Jun 24 11:57:43 MediaTank kernel: NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0 Unraid version 7.1.4 Nvidia Info: Nvidia Driver Version: 575.51.02 Open Source Kernel Module: No Installed GPU(s): 0: NVIDIA GeForce GTX 1650 SUPER 02:00.0 The error happens frequently and when erroring the card doesn't seem responsive. Sometimes restarting the TDARR docker helps release the card and fix the issue. Any suggestions on what to try? I'm starting to think my card is dying :( Thanks UPDATE - I have upgraded the nvidia driver to 575.65 and removed the GPU statistics plugin, then rebooted. So far, no logs indicate issues, but it's too early to tell. Any other troubleshooting steps would be greatly appreciated.

The update went fine for me. Hopefully fixed my crashing issues. FIXES: (Auto Update) Custom install paths are not respected when auto-updating on 64 bit Windows. (PM-1143) (CreditsDetection) Retry detection only a limited amount of times on failures (PM-1093) (DB Optimize) Server could become unresponsive during a DB optimize in certain circumstances (PM-1129) (Loudness Analysis) Some files could cause errors when preforming Loudness Analysis. (PM-627) (Push Notifications) Used expensive DB query during playback progress notifications (PM-1166) -- This could have been my issue (Thumbnails) Thumbnails were not properly updated when underlying file changed (PM-1162) (Transcoder) On Windows, headless (no display attached) Nvidia cards were not recognized (PM-962) (Transcoder) On Windows, the first Intel device was used for transcoding regardless of which Intel device was selected (PM-962)

Removed the user that was using the Roku client and so far, my Plex has remained stable.

F, my Plex is still crashing and the only pattern I see is when someone with an old Roku client connects it crashes. Was fine a few days and then the Roku client connects and it crashes.

I suspect there are some Plex bugs in the last couple of builds that need to be worked out. I have had 0 issues with Plex and this docker for years. The last time I had issues, it was Plex related and was fixed in an update.

I did run the PlexDBRepair tool and all seemed OK. I can dig into that a bit more, just in case. *edit* Having the repair right in the docker is slick, thank you for pointing that out. Gave that a go, but all looked good.

I'm experiencing the same issues and I'm going crazy trying to figure it out. I don't see any errors in the logs and it seems completely random when it stops responding. The only errors I was able to find were: - HTTP error requesting GET https://*****.plex.direct:443/identity (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name '****.plex.direct') - Unknown metadata type: folder - Some errors related to the DVR feature and I completely disabled the Plex Tuner Service for now I have updated my wildcard cert, verified DNS settings and even bypassed my adguard home dns servers. I enabled "Strict TLS configuration" in hopes it was some old clients causing the issue. Any suggestions would be appreciated as I'm having issues troubleshooting when the logs show nothing and it doesn't crash completely (no crash dump). Thanks

I am also experiencing this, but a reboot temporarily fixes the problem. I think I had some "files in use" or "mover" issues that caused it to hang?

The above is not working for me. It won't even let me disable listening on 443 (HTTPS) for SABNZBD, it keeps enabling on reboot. There is really no need for me to listen via HTTPS as I use SWAG for reverse proxy. All my *arr applications talk to SABNZBD via HTTP and not HTTPS locally.

So glad it's not just me with this problem. Any fix yet?