Everything posted by eranwolf
-
[Support] binhex - SABnzbd
I have been using SABnzb docker with news.newshosting.com for years with zero issues. The other day, I had to switch ISPs. In my haste, I forgot to pause my queue and simply switched out cables. Since then, SABnzb has been receiving Server address news.newshosting.com:563 is not valid. I have also tried this using port 119 with the same results. I initially thought I had too many connections because of the switch but that's not the error I was getting back for that. When I hit the wrench for status and interfaces, I get a never-ending loading status. Now as a test I loaded NZBGet docker as a test and everything connects fine and resolves. So this tells me its an issue with SABnzb docker. I also loaded the SABnzb Windows program and it connected fine as well. Does anyone have a clue? I have tested this on two separate machines on two different ISPs on two different networks with the same results. I get the resolve issue on SABnzb docker, but it works fine with NZBGet, both Windows and Linux Docker. I can also ping and do NSLookups with no issues from the machines themselves. I can also do pings and nslookups inside the docker itself with no issue as well.
-
[Plugin] Nvidia-Driver
OK swapped the current P4000 card out with a P2000 card and so far transcoded multiple movies and 3-4 simultaneous streams and they all released no problem. I am going to test it a bit further but so far it seems the Quadro P4000 card went bad and was the issue. Also, Array now stops and starts cleanly with none of the decoder.so files hanging.
-
[Plugin] Nvidia-Driver
OK thank you for the assist. No nothing has changed at all. This is the same system and config that has been running for two years now. Haven't swapped out a single part since it was built. I do have another Quadro card so I will swap it out and test and report back.
-
[Plugin] Nvidia-Driver
Attached tower-diagnostics-20241030-1729.zip
-
[Plugin] Nvidia-Driver
Also, just for reference, this is what I am getting in the Nvidia Driver plugin after the transcoding issue occurs.
-
[Plugin] Nvidia-Driver
OK got these sections from the Diag log. This occurred after the transcode stopped. Oct 28 20:47:24 Tower kernel: NVRM: GPU at PCI:0000:65:00: GPU-xxxxxx-xxxxxx-xxxxx-xxxxx Oct 28 20:47:24 Tower kernel: NVRM: GPU Board Serial Number: 1323019024289 Oct 28 20:47:24 Tower kernel: NVRM: Xid (PCI:0000:65:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus. Oct 28 20:47:24 Tower kernel: NVRM: GPU 0000:65:00.0: GPU has fallen off the bus. Oct 28 20:47:24 Tower kernel: NVRM: GPU 0000:65:00.0: GPU serial number is 1323019024289. Oct 28 20:47:24 Tower kernel: NVRM: A GPU crash dump has been created. If possible, please run Oct 28 20:47:24 Tower kernel: NVRM: nvidia-bug-report.sh as root to collect this data before Oct 28 20:47:24 Tower kernel: NVRM: the NVIDIA kernel module is unloaded. Oct 28 20:47:24 Tower kernel: NVRM: Xid (PCI:0000:65:00): 154, pid='<unknown>', name=<unknown>, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required) This is when I hit stop array: Oct 29 10:20:01 Tower root: Error response from daemon: cannot stop container: plex: tried to kill container, but did not receive an exit event Oct 29 10:20:01 Tower root: Error response from daemon: cannot stop container: EmbyServer: tried to kill container, but did not receive an exit event Oct 29 10:20:13 Tower root: stopping dockerd ... Oct 29 10:20:14 Tower root: ... Waiting to die. ### [PREVIOUS LINE REPEATED 14 TIMES] ### Oct 29 10:20:28 Tower root: Error: process will not die! Oct 29 10:20:28 Tower root: ... Killed. AND Oct 29 10:20:49 Tower emhttpd: shcmd (153): umount /mnt/cache Oct 29 10:20:49 Tower root: umount: /mnt/cache: target is busy. Oct 29 10:20:49 Tower emhttpd: shcmd (153): exit status: 32 Oct 29 10:20:49 Tower emhttpd: Retry unmounting disk share(s)... Oct 29 10:20:54 Tower emhttpd: Unmounting disks... Oct 29 10:20:54 Tower emhttpd: shcmd (154): umount /mnt/cache Oct 29 10:20:54 Tower root: umount: /mnt/cache: target is busy. Oct 29 10:20:54 Tower emhttpd: shcmd (154): exit status: 32 Oct 29 10:20:54 Tower emhttpd: Retry unmounting disk share(s)... Oct 29 10:20:59 Tower emhttpd: Unmounting disks... Oct 29 10:20:59 Tower emhttpd: shcmd (155): umount /mnt/cache Oct 29 10:20:59 Tower root: umount: /mnt/cache: target is busy. Oct 29 10:20:59 Tower emhttpd: shcmd (155): exit status: 32 Oct 29 10:20:59 Tower emhttpd: Retry unmounting disk share(s)... Oct 29 10:21:04 Tower emhttpd: Unmounting disks... Oct 29 10:21:04 Tower emhttpd: shcmd (156): umount /mnt/cache So it looks as if the cache drive is unable to be unmounted.
-
[Plugin] Nvidia-Driver
I am using linxserver.io repository: Linuxserver.io version: 1.41.1.9057-af5eaea7a-ls241 Build-date: 2024-10-24T17:32:03+00:00 ─────────────────────────────────────── Setting permissions on /transcode Server already claimed permissions for /dev/dri/renderD128 are good permissions for /dev/dri/card0 are good Docker is used for versioning skip update check [custom-init] No custom files found, skipping... Starting Plex Media Server. . . (you can ignore the libusb_init error) [ls.io-init] done. I have checked and no maintenance or tasks are running when this occurs. I am going to pull the diagnostic logs as soon as it happens again.
-
[Plugin] Nvidia-Driver
I also thought this might be the case at first. However, I used Emby as a test, and the same thing happened. Also, when I use the Stop Array command, the docker completely shuts down. However, if I restart just the Plex app, I get the Server Execution Error because of the decoder issue.
-
[Plugin] Nvidia-Driver
Hardware transcodes not releasing .so files I am currently running plex container on Unraid 6.12.13. I have an Nvidia Quadro P4000 currently using Nvidia driver version 565.57.01. I noticed this behavior about 2 weeks ago when I went to reboot my Unraid server and noticed that the Array would not shut down properly. I would receive a message stating Retry unmounting disk shares. This was preventing a clean shut down of the server. Digging in more I discovered that about two dozen various decoder.so files using Process shfs with Process ID 6454were hung and would not shut down cleanly and this was causing the issue. I dug in deeper and tested. It looks as if when an item is transcoded in plex it causes the decoder.so files not to release once it is done. In turn the Nvidia driver settings page returns - Unable to determine the device handle for GPU0000:65:00.0: Unknown Error, under the Installed GPU(s): section. Once this occurs the GPU no longer transcodes and only the CPU does at that point, pinning the CPU. Plex container log: Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] block_len_bits 5 out of range Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] prev_block_len_bits 6 out of range Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] block_len_bits 5 out of range Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] block_len_bits 5 out of range Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] overflow (129 > 116) in spectral RLE, ignoring Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] block_len_bits 6 out of range Error while decoding stream #0:0: Operation not permitted [wmav2 @ 0x151bfa885600] prev_block_len_bits 6 out of range Error while decoding stream #0:0: Operation not permitted size= 7kB time=00:05:39.19 bitrate= 0.2kbits/s speed=4.41e+03x video:0kB audio:7kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.368775% Conversion failed! 6.1.106-Unraid x86_64 Client: Version: 24.0.9 API version: 1.43 Go version: go1.20.13 Git commit: 2936816 Built: Thu Feb 1 00:47:46 2024 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 24.0.9 API version: 1.43 (minimum version 1.12) Go version: go1.20.13 Git commit: fca702d Built: Thu Feb 1 00:49:16 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.7.13 GitCommit: 7c3aca7a610df76212171d200ca3811ff6096eb8 runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0 NAME=Slackware VERSION="15.0" ID=slackware VERSION_ID=15.0 PRETTY_NAME="Slackware 15.0 x86_64 (post 15.0 -current)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:slackware:slackware_linux:15.0" HOME_URL="http://slackware.com/" SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/" BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/" VERSION_CODENAME=current What could be causing the decoder.so files to prevent being released?
-
ComiXed-Docker Support Thread
I am running the ComiXed docker v 1.1.2-1 on Unriad 6.11.0. When I try to save manual entries for comic data, such as Title etc. I receive "Failed to save changes. ERROR". The log files for the container show: 2022-09-29 13:23:14.482 WARN 12 --- [nio-7171-exec-5] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Already had POJO for id (java.lang.Long) [[ObjectId: key=40, type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator, scope=java.lang.Object]]; nested exception is com.fasterxml.jackson.databind.JsonMappingException: Already had POJO for id (java.lang.Long) [[ObjectId: key=40, type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator, scope=java.lang.Object]] (through reference chain: org.comixedproject.model.comicbooks.ComicBook["fileDetails"]->org.comixedproject.model.comicbooks.ComicFileDetails["id"])] I don't think this error has to do with it but this is the only item that is showing in the logs. Thanks.
-
[Support] Partition Pixel - Chia
Thanks, that was the trick. I did need to use the -s pool , as well.
-
[Support] Partition Pixel - Chia
What would the proper command line be to join a pool that is already active that I have the join URL for? I am assuming... chia plotnft join -u <URL> - s pool Edit: Scratch the question. The docker version is 1.2.1 dev0, the pool I am using is only on 1.2.0
-
[Support] Partition Pixel - Chia
I would love to know the answer to this as well.
-
[Support] Partition Pixel - Chia
Can you tell me what port you use to connect to your farmer? I see the setting for harverster only to be set to true but am unsure of the port to use to connect.
-
[Support] Linuxserver.io - Sonarr
Thank you for leading me down the proxy path!!! The update somehow told Sonarr to Enable Proxy. Unchecked the box, restarted the Docker and boom started working. Thanks!!
-
[Support] Linuxserver.io - Sonarr
So I do not run SABNzb through a proxy, however I do run Deluge binhex through PIA. Where would you tell Sonarr to ignore that IP? Also, I am now seeing Sonarr add shows to my activity queue but it is putting them in a Queued status and doesnt actually download anythign on SABNzb or Deluge. So it can see and my Download Clients it just cannot initiate the download.
-
[Support] Linuxserver.io - Sonarr
Using Unraid and updated my Sonarr docker to Sonarr version [v3.0.4.1131] last night. I use SABNzb and Deluge as my DL Clients. Get the same error and log entry for both clients. Radarr is working flawlessly with identical settings in both programs. I looked through the Troubleshooting Guide already but I have tried all the steps suggested. v3.0.4.1132] NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to SABnzbd, HTTP request failed: [503:ServiceUnavailable] [GET] at [http://IP Address:8080/api?mode=get_config&apikey=API Key=json] ---> NzbDrone.Common.Http.HttpException: HTTP request failed: [503:ServiceUnavailable] [GET] at [http://IP Address:8080/api?mode=get_config&apikey=7API KEY&output=json] I can post the full log if needed.
-
RADARR sees indexers but not SAB
I am hoping this gets update. I am having a similar issue. I updated Sonarr last night to version 3.0.4.1131. Radarr works absolutely fin but Sonarr cannot contact any of my download clients. I use Deluge and SABNzb. For SAB I receive the following error in the log file. [v3.0.4.1131] NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to SABnzbd, HTTP request failed: [503:ServiceUnavailable] [GET] at [http://IP Address:8080/api?mode=get_config&apikey=70919fa08ab1429cb0bb0d03cf4357e5&output=json] ---> NzbDrone.Common.Http.HttpException: HTTP request failed: [503:ServiceUnavailable] [GET] at [http://IP Address:8080/api?mode=get_config&apikey=70919fa08ab1429cb0bb0d03cf4357e5&output=json] I have verified the API keys etc and all are fine. Like I said Radarr is working flawlessly.
-
[Support] binhex - Radarr
Question, I am moving radarr from a Windows 10 box to a binhex-radarr container on UNRaid. I want to preserve the history etc. I am moving it based on the reddit article here . I have 2 NAS devices that store my movies that are currently mounted in UNRaid. I have them mapped in the binhex-Radarr container as /media/Movies/ and /media/Movies2/ . My question is simply when editing the nzbdrone.db do I change the root and media paths to /Movies/ and /Movies2/ or /media/Movies/ and /media/Movies2/?