gergtreble

Is iotop working for everyone? I get the following error? ~# iotop Traceback (most recent call last): File "/usr/sbin/iotop", line 17, in <module> main() File "/usr/lib64/python2.7/site-packages/iotop/ui.py", line 620, in main main_loop() File "/usr/lib64/python2.7/site-packages/iotop/ui.py", line 610, in <lambda> main_loop = lambda: run_iotop(options) File "/usr/lib64/python2.7/site-packages/iotop/ui.py", line 508, in run_iotop return curses.wrapper(run_iotop_window, options) File "/usr/lib64/python2.7/curses/wrapper.py", line 22, in wrapper stdscr = curses.initscr() File "/usr/lib64/python2.7/curses/__init__.py", line 33, in initscr fd=_sys.__stdout__.fileno()) _curses.error: setupterm: could not find terminal Uninstalled it, re installed it. On latest version of Nerd Tools. Any pointers? Is there a different way I could install this?

I have a simple Tdarr use case. Cycle through my Movies and TV shows and convert everything possible to HVEC x265 to save me some disk space. I'm running Unraid Server in Docker on my Unraid Machine. I have three nodes I can use: 1. The Quadro p1000 in my unraid sever using NVENC. 2. A remote windows micro PC with a 9th generation Intel iGPU using QSV. 3. A remote M1 Macbook Air using Videotoolbox. All these nodes are configured in the options page with the GPU type and for the GPU to take CPU tasks. I first set up to only use the Windows and Mac machines using the BOOSH QSV/Videotoolbox plugin and it worked perfectly if a little slowly churning through my movies. I then tried to add the Quadro p1000 node and I added the (standard?) Migz NVEC GPU plugin I hit issues. Nothing would transcode on the Mac, when I looked in the logs every transcode was failing when it came to the NVEC plugin and was passing the transcode job to the p1000 node. The QSV node was working fine, picking up transcodes and completing them successfully, and not displaying this behaviour. I then tried putting the BOOSH plugin before the NVEC plugin in the stack so I ended up with files being transcoded twice! First successfully by the Mac then buy the p1000 once it hit the Migz plugin. Again the QSV node was working fine I just couldn't get this configuration to work. Has anyone else? Was I configuring it wrong in some way? I'm asking this as I ended up paying for a month of Pro and currently have the p1000 churning through my Movies library and the PC/Mac working through the TV shows library. It working fine and I should have all the movies done by the end of the week (hopefully) but then I would like to have all three nodes working on the Tv Shows. Any thoughts? Am I missing something here, I would have thought that the plugin logic would skip the NVEC plugin when running on the Mac and complete the stack. Is it possible to add an IF statement to the stack in some way? So I can skip the NVEC plugin?

Well the p600 is all packed up and being shipped back. Just won an auction for a p1000. So if I get the same issues, thats my next action! Hope not to be back next weekend!

I've given up on it and started an eBay return. Spent a good 12hrs yesterday frying my brain trying to figure it out. The guy from reddit got back to me and he had no issues using the linux drivers, his got recognised first time in the same config as me with no BIOS tweaks. So I'm almost certain its a dud card. Just my luck!

Thanks for all the help, that does make perfect sense. The weird thing is I've done extensive googling around and there are several people who have seen similar issues. Most have been due to the way their systems boot. I'm wondering if I just have some kind of fundamental incompatibility with my existing hardware. I expect the supermicro server boards never expected to see a GPU in their PCIe3.0 slots. Maybe this just accelerates my planning for a new hardware upgrade.

I don't have any other way to test it TBH. I only have the one full sized PCI slot sadly. One thing I have noticed is that I get the following in my syslog: Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x31:0xffff:2465) Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x31:0xffff:2465) Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x31:0xffff:2465) Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x31:0xffff:2465) Apr 21 19:50:19 THOMPSON kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Whenever I reload the plugin page or run nvidia-smi. So yeah, I think I have enough evidence here that I have a dud card. Bummer! Thanks for the help, I'll return it and try and find another.

I'm now running the most up to date BIOS. Its not helped. I really don't know. But alt least one other person has got it working (I'm gonna reach out to him). The fan is spinning on it, if thats any indication? Enabled the Above 4G support. Didn't change the outcome. Could not find any way to enable Resizable BAR in the BIOS. Oh dear, I don't know or have anyway to tell! I picked this card up cheap on Ebay. Maybe it's time to return it. Any other ideas? Thanks for your help.

Hi Been trying to get my Quadro p600 to be recognised by the driver plugin without any success. Just get the message "No devices were found". The card appears in the hardware profile. Ive used the latest and the production drivers and neither recognise the card. Thought it might be my ancient BIOS. So I updated that to latest, no dice. Ive attached some screenshots and a diagnostics file. Any assistance is gratefully received. thompson-diagnostics-20230421-1802.zip

I know its been asked for a few times already but can we please have SOCAT included in nerdtools. It was in nerdpack and I just noticed its gone. Thanks!

This has affected me too. Upgraded to 6.10 and all my lights stopped working! Currently downgrading. Following topic in eager anticipation of a fix.

In the meantime I've spun up your rutorrentvpn docker and spent the afternoon migrating that specific trackers torrents on to that. So at least I'm seeding again.

Sadly we still have the same behaviour. I'd love to know how they are determining that its not an allowed client. Maybe the Deluge and Libtorrent versions don't match or they expect different version? Either way appreciate the effort here Binhex, think you also improved my sed!

Ah gotcha! I'm all out of ideas then! They must be identifying the version in some other way.

Same issue still, seems they are grepping the first few characters of the peerID for the -D string and using it to indicate its a dev build? Anyone know what the peerID for the latest non dev build is? (Or can help me find out how to find that?)

Well they have not banned me yet! But I'm still being flagged as a dev build by the peerID. Looks like the "-D" string is triggering it. (D for dev?)

Thanks Binhex! I was not implicitly calling the :latest flag in my docker config. I just set that and refreshed. No packages changed so I guess I was already on latest. I'm still not able to seed and looking at the message in the tracker (attached) it seems they are seeing it as a 2.0.3 release, so the user agent switch is working. But they are still somehow able to notice its a dev version. Looks like they are using the 'peerid' to determine this?

Hey Binhex have you made any progress on a non dev deluge build? I could really do with being able to seed on my private tracker!

Thanks Binhex! I'd really appreciate that. Just sent you a beer from the UK. Happy new year!

Sadly, I think you are correct. I tried to downgrade to the last 2.0.3 tag in the repo and the VPN broke immediately. I guess any build with the next-gen config included would be a 'dev' release. Interested to hear what Binhex has to add though.

Quick question. Is there a version of binhex-delugevpn that supports the next-gen PIA network that is not a "development version" of deluge i.e. matches the official release version (2.0.3?). One of my (quite niche) trackers does not support dev versions and as such I'm not able to use them. I'm currently on Deluge 2.0.4.dev38. Maybe the question should be what is the earliest release that supports next-gen PIA?

Aha! Got it working. There is an updated version for Deluge 2.0.3 here: https://github.com/d8ahazard/deluge-extractor Built the egg, renamed it to cover the correct python version (3.8) and its loaded and appears to kind of work. Although it appears to be extracting into the appdata folder right now.

Thanks, I can see the "Extactor" plugin in the UI but this wont work for me as I have to move the completed torrents to a seeding location AFAIK this breaks the functionality. Thats why I am hoping to use the Simple-Extractor plugin I linked to. But I cant get it to show up in the UI at all. I'll see if I can had around with the config file though. Cheers.

Hello, I'm banging my head against a wall here trying to install the simple extractor plugin. I cant get it to show up in the UI at all. I've tried adding the egg via the UI and also by placing it in the plugin folder neither enables it. Any thoughts? Is it unsupported? Runnning binhex/arch-delugevpn:2.0.3-2-01 and trying to add the latest plugin from here: https://github.com/cvarta/deluge-extractor If it isn't possible to use this plugin what methods are you guys using to automatically extract rar/zip files for Sonarr?

Thank you. This really helped. I've managed to successfully downgrade. Just re-checking all my torrents now. This might take a while! If anyone else need to do this. The extra string at the end of Bugster's Repo name is a git tag. You can find the right one by going to the binhex-delugeVPN github page: https://github.com/binhex/arch-delugevpn Then change the tag to whatever Deluge version you want: Then just stop your container and add that string to the end of your repo (with a colon) and hit apply.

Is there a reason why a dev build of Deluge is packaged in this docker? One of my trackers wont accept dev builds of deluge, and only support up to the official latest release (2.0.3). Is there any way I can downgrade the version or do I need to wait till 2.0.4 is an official release? Thanks in advance.