mattekure

I'm not so sure. I see a bunch of tasks with covid in the name, not starting with rb_.

it seems right when it starts. it downloads and them immediately throws the error I'll let it run for a day or two, see if it was just those particular ones and if any future ones throw errors.

I got it working, but I am noticing that in the jobs it downloads, the ones where the "Application" field is "Rosetta Mini 3.78" throw a Computation error. the ones marked Rosetta 4.08 seem to be processing fine.

Are there any instructions on how to switch over from the official boinc container to this one?

If there is anything you can do to support using the larger font sizes, it would be greatly appreciated.

I am using the White theme. I found that decreasing the font size resolved it, but it makes it harder to read. I had originally set it to Very Large (bad eyes), and by changing it to Normal, its no longer scrunched together.

I'm getting the numbers scrunched up for Encoder and Decoder Utilization

I'm getting an error trying to update to the latest version. plugin: updating: community.applications.plg Cleaning Up Old Versions plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/archive/community.applications-2020.02.06-x86_64-1.txz ... done plugin: bad file MD5: /boot/config/plugins/community.applications/community.applications-2020.02.06-x86_64-1.txz

I have noticed recently that my rutorrent web interface seems to be very unresponsive. I frequently get time out errors when trying to connect to the web interface. When it does connect, it appears to be downloading, but very slow to respond. Attached is my redacted supervisord.log, but I dont see anything that stands out to me. I have around 240 completed and inactive torrents, and 1 active torrent. The web interface seems to indicate the CPU is at 100%. But my Unraid system is not. My unraid is using a Ryzen 9 3900X 12 core CPU, so there should be plenty of computing power available. supervisord.log

Thank you very much for this, and especially for the excellent setup instructions. Everything went super easy and smooth (once I realized I accidentally forwarded port 51280 instead of 51820).

What exactly does the Health check do? what is it checking? I ran it on my entire library and they all passed, but I'm curious as to what its actually looking for.

I have a P2000 and I had no issues pushing 20 workers on it. That said, it still uses CPU for other parts of the transcoding, so you need to monitor your usage to know how it will affect your machine. Also be aware that using the P2000 or any card with the NVENC, while quick, there is a trade off in size/quality. So dont expect nearly as much of a reduction in size.

I just noticed this in my syslog. Nov 14 12:47:06 Tower kernel: ffmpeg[3783]: segfault at 150f8ba28478 ip 0000150f8de98000 sp 0000150f8ba26370 error 6 in libavcodec.so.58.35.100[150f8d6b6000+928000] Nov 14 12:47:06 Tower kernel: Code: fd 41 b8 10 00 00 00 41 54 49 89 d4 ba 10 00 00 00 55 53 48 89 f3 48 83 c6 01 48 81 ec 18 01 00 00 64 48 8b 04 25 28 00 00 00 <48> 89 84 24 08 21 00 00 31 c0 48 89 e5 48 89 ef e8 5b b7 00 00 68 Edit, I am seeing this multiple times now, especially after an encode works for a couple hours right to the end of a file, but then somehow it fails.

Would it be possible to add a Pending Tasks count to the dashboard? So i can see how many are left in the queue?

Thanks. I somehow overlooked that setting in the DHCP section of my router. I have added it there.

Quick question, I have the Pi-hole docker set up and working correctly (I think). the Dashboard shows queries being blocked and the blacklists in effect. I currently have it set up so that my Router points to pi-hole for DNS queries. On the pi-hole network overview, it show all the queries as originating from the router. I believe this is the expected behavior as the clients are passing the request to the router which then passes it to pi-hole. I just wanted to be sure that is what I should be seeing.

Thats essentially what I have done. My router uses pihole as the primary DNS, and secondary I have pointing to another one (quad9). that way even if pihole is down, it should allow DNS to continue working. Unraid of course is set to a static DNS, not getting it from the router so it works whether or not pihole is running.

Thank you, upgraded without issue.

Overnight I began receiving this error about communicating with github and being unable to download the list of blacklisted plugins. I am using the google DNS and I am able to browse github without issue from my browser. I also tested pinging github and got a response fine, so I'm not sure whats going on. I've attached diagnostics if its helpful. tower-diagnostics-20181130-0721.zip

If possible, please add hwloc for hardware locality topology generation. Thank you

Thanks for the reminder, there hasn't been a BIOS update since 2016 for my MB, but when I checked, there was one less than a month ago that specifically includes microcode vulnerability updates.

With the recent update to 6.4.0, I decided to change the dockers over to their own IPs. After some initial confusion, I have been able to get all the dockers working fine except for the Web UI of my binhex-delugevpn and binhex-sabnzbdvpn dockers. The odd thing is that I know the dockers are running. For example, with the deluge docker, I can connect to it using the deluge client on my desktop. I can use also privoxy without issue and other dockers such as radarr and sonarr report that they can connect to them fine. Its just the WebUI will now no longer come up. For all the others, the issue revolved around something in the docker trying to communicate with the unraid host, which is prohibited by macvlan. Any thoughts on what might be happening?

For the System Info plugin, would it be possible to add the capability to download the generated information as an html file?

I also noticed that whenever I log in I get the following error on the log: Tower sshd: rexec line 110: Deprecated option UsePrivilegeSeparation In the settings I have Permit Root Login set to No. the log in is still successful though, so its not affecting anything yet.