doubleopinter

Just updated Unraid to 6.12.8 from 6.11.5 and update frigate to 0.13.2 from 0.12.x. Cannot start. I've been using my RTX 2060 for frigate, seems like something around that is broken right now. Trying to start gives me this text error warn system array login s6-rc: info: service nginx-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service go2rtc-healthcheck successfully stopped s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service nginx-log successfully stopped 2024-02-20 16:01:18.482511101 [INFO] Preparing Frigate... 2024-02-20 16:01:18.484724421 [INFO] Preparing new go2rtc config... 2024-02-20 16:01:18.487565996 [INFO] Starting NGINX... 2024-02-20 16:01:18.507874744 [INFO] Starting Frigate... 2024-02-20 16:01:18.874916467 [INFO] Starting go2rtc... 2024-02-20 16:01:18.970936212 16:01:18.970 INF go2rtc version 1.8.4 linux/amd64 2024-02-20 16:01:18.971461057 16:01:18.971 INF [rtsp] listen addr=:8554 2024-02-20 16:01:18.971507921 16:01:18.971 INF [api] listen addr=:1984 2024-02-20 16:01:18.971725449 16:01:18.971 INF [webrtc] listen addr=:8555 2024-02-20 16:01:19.961878556 [2024-02-20 16:01:19] frigate.app INFO : Starting Frigate (0.13.2-6476f8a) 2024-02-20 16:01:22.205178677 2024/02/20 16:01:22 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.195, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.101.198:5001" 2024-02-20 16:01:27.203162963 2024/02/20 16:01:27 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.195, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.101.198:5001" 2024-02-20 16:01:28.483323782 [INFO] Starting go2rtc healthcheck service... 2024-02-20 16:01:30.735092299 [2024-02-20 16:01:30] peewee_migrate.logs INFO : Starting migrations 2024-02-20 16:01:30.744011537 [2024-02-20 16:01:30] peewee_migrate.logs INFO : There is nothing to migrate 2024-02-20 16:01:30.754203654 [2024-02-20 16:01:30] frigate.app INFO : Recording process started: 619 2024-02-20 16:01:30.756668686 [2024-02-20 16:01:30] frigate.app INFO : go2rtc process pid: 98 2024-02-20 16:01:30.787144780 [2024-02-20 16:01:30] detector.tensorrt INFO : Starting detection process: 629 2024-02-20 16:01:30.798494557 [2024-02-20 16:01:30] frigate.app INFO : Output process started: 632 2024-02-20 16:01:30.916849564 [2024-02-20 16:01:30] frigate.detectors.plugins.tensorrt INFO : Loaded engine size: 13 MiB 2024-02-20 16:01:31.052494849 [2024-02-20 16:01:31] frigate.detectors.plugins.tensorrt ERROR : 1: [stdArchiveReader.cpp::StdArchiveReader::42] Error Code 1: Serialization (Serialization assertion stdVersionRead == serializationVersion failed.Version tag does not match. Note: Current Version: 232, Serialized Engine Version: 213) 2024-02-20 16:01:31.063680272 [2024-02-20 16:01:31] frigate.detectors.plugins.tensorrt ERROR : 4: [runtime.cpp::deserializeCudaEngine::66] Error Code 4: Internal Error (Engine deserialization failed.) 2024-02-20 16:01:31.065394010 Process detector:tensorrt: 2024-02-20 16:01:31.066177617 Traceback (most recent call last): 2024-02-20 16:01:31.066202689 File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap 2024-02-20 16:01:31.066204469 self.run() 2024-02-20 16:01:31.066205639 File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run 2024-02-20 16:01:31.066206650 self._target(*self._args, **self._kwargs) 2024-02-20 16:01:31.066213860 File "/opt/frigate/frigate/object_detection.py", line 102, in run_detector 2024-02-20 16:01:31.066214970 object_detector = LocalObjectDetector(detector_config=detector_config) 2024-02-20 16:01:31.066216010 File "/opt/frigate/frigate/object_detection.py", line 53, in __init__ 2024-02-20 16:01:31.066216930 self.detect_api = create_detector(detector_config) 2024-02-20 16:01:31.066218891 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector 2024-02-20 16:01:31.066221911 return api(detector_config) 2024-02-20 16:01:31.066222911 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 221, in __init__ 2024-02-20 16:01:31.066241333 self.input_shape = self._get_input_shape() 2024-02-20 16:01:31.066251093 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 93, in _get_input_shape 2024-02-20 16:01:31.066252314 binding = self.engine[0] 2024-02-20 16:01:31.066253474 TypeError: 'NoneType' object is not subscriptable 2024-02-20 16:01:31.066282416 Exception ignored in: <function TensorRtDetector.__del__ at 0x147c26336c10> 2024-02-20 16:01:31.066292897 Traceback (most recent call last): 2024-02-20 16:01:31.066294367 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 239, in __del__ 2024-02-20 16:01:31.066439730 if self.outputs is not None: 2024-02-20 16:01:31.066535718 AttributeError: 'TensorRtDetector' object has no attribute 'outputs' 2024-02-20 16:01:31.075520771 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for driveway: 654 2024-02-20 16:01:31.089611724 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for shedsouth: 656 2024-02-20 16:01:31.101789522 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for shedwest: 664 2024-02-20 16:01:31.113922867 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for doorbell: 666 2024-02-20 16:01:31.123676776 2024/02/20 16:01:31 [error] 155#155: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", upstream: "http://127.0.0.1:5001version", host: "127.0.0.1:5000" 2024-02-20 16:01:31.128786856 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for driveway: 669 2024-02-20 16:01:31.141811307 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for shedsouth: 673 2024-02-20 16:01:31.152635609 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for shedwest: 676 2024-02-20 16:01:31.166414685 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for doorbell: 684 2024-02-20 16:01:51.338649529 [2024-02-20 16:01:51] frigate.watchdog INFO : Detection appears to have stopped. Exiting Frigate... 2024-02-20 16:01:51.353163748 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) 2024-02-20 16:01:51.390329037 [INFO] Service NGINX exited with code 0 (by signal 0) 2024-02-20 16:01:51.392743125 [2024-02-20 16:01:51] frigate.app INFO : Stopping... 2024-02-20 16:01:51.393062562 [2024-02-20 16:01:51] frigate.events.cleanup INFO : Exiting event cleanup... 2024-02-20 16:01:51.393342556 [2024-02-20 16:01:51] frigate.record.cleanup INFO : Exiting recording cleanup... 2024-02-20 16:01:51.393893554 [2024-02-20 16:01:51] frigate.storage INFO : Exiting storage maintainer... 2024-02-20 16:01:51.394247894 [2024-02-20 16:01:51] frigate.stats INFO : Exiting stats emitter... 2024-02-20 16:01:51.404968067 [2024-02-20 16:01:51] frigate.ptz.autotrack INFO : Exiting autotracker... 2024-02-20 16:01:51.412022154 [2024-02-20 16:01:51] frigate.watchdog INFO : Exiting watchdog... 2024-02-20 16:01:51.412285637 [2024-02-20 16:01:51] frigate.object_processing INFO : Exiting object processor... 2024-02-20 16:01:51.621805971 [2024-02-20 16:01:51] frigate.events.maintainer INFO : Exiting event processor... 2024-02-20 16:01:51.783135497 [2024-02-20 16:01:51] frigate.comms.ws INFO : Exiting websocket client... 2024-02-20 16:01:52.767713382 [2024-02-20 16:01:52] peewee.sqliteq INFO : writer received shutdown request, exiting. 2024-02-20 16:01:52.774181768 [2024-02-20 16:01:52] watchdog.doorbell INFO : Terminating the existing ffmpeg process...

Hey all. I’ve been running Unraid for a few years and I need some help troubleshooting stability issues. Short version is that occasionally over the last 6 months, all my RAM gets used and the system freaks out, pinning the CPUs. Luckily it is still able to properly reboot, but it takes a really long time to do so. I have some containers running and I think that’s probably where the issues are. I have a few questions 1. Can I setup a notification somehow to alert me when ram usage is high. If I catch it early enough it should be easier to sort out. 2. What should I be looking for when it’s in this state? Is there any type of logging or anything I can enable? Thanks

Just wanted to follow up on this real quick. I moved some stuff around, I put the gpu into the port which becomes 2x when using one of the x1 ports and the disk controller into where the gpu was. The gpu is only used for frigate acceleration and transcoding plex so I figure to pcie lanes is probably enough for it. After I did that I'm able to use the nic, the controller and the gpu. Thanks for the insight! Now I'm on the hunt for a cheap x470 board or maybe a newer cpu and board, but that's low priority for now.

Got ya. Guess I'm kind of hosed. I'll see if there's any kind of BIOS update or anything which might change it. Thanks for the input.

Hmmmm... Interesting. Is there any way to tell which lanes it allocates for itself? Not the first time I've run into PCIe issues with this damn board. Might be time to scour ebay for some new hardware. Those two PCI slots sure aren't doing much for me.

Diags attached. No I am not running VMs. I have a couple configured but they haven't been run in a long time. Could you tell me what specifically you're looking for in the logs? pinter-diagnostics-20230810-0944.zip

Hey all, I was wondering if I could get some help troubleshooting an issue. I have an older AMD based system that runs unraid, I think the board is a B350. Everything runs great. I use a 5 port pcie based disk controller to extend my sata capacity. Works great, probably a bit slow but for me it's perfect. I wanted to install a 2.5gb nic so I bought an RTL based pcie card. When I plug in the card and boot, the pcie disk controller seems to be missing. Unplug the card, pcie controller is back. It may be the case I've run out of pcie lanes or something, as I also have an RTX 2060 in the box, but I was wondering if there's anything I could do to troubleshoot. Under system devices I see this when the nic is not plugged in (the RTL card is the onboard) [10ec:8168] 21:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) [197b:0585] 22:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller [9:0:0:0] disk ATA INTEL SSDSA2CW12 0362 /dev/sdd 120GB [10:0:0:0] disk ATA WDC WD20EFRX-68E 0A80 /dev/sde 2.00TB [11:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdf 6.00TB [12:0:0:0] disk ATA WDC WD20EFRX-68A 0A80 /dev/sdg 2.00TB [13:0:0:0] disk ATA WDC WD60EFAX-68J 0A83 /dev/sdh 6.00TB With the pcie nic installed, the SATA Controller is missing and the nic is at address 24:00.0. Thanks!

Is it possible to somehow allow other containers to use this container as their interface? ie I'd like to have some containers on my zerotier network.

I just wanted to ask if abysmal UI performance is expected from Nextcloud haha? My unraid is on a decent machine, older Ryzen, 32GB RAM, I have a cache SSD. I installed it with MariaDB. Using the UI via the browser is horrendous. It's unusable. Is there something I can troubleshoot? Edit: Turns out if I wasn't an idiot and set my cache drive to my NVR drive things work a lot better

Just found this thread on google. I'm seeing this on my system, 6.11.5, planning on staying on this version for a while still.

Hey I just came here to discuss the same thing, I don't think it's TCP vs uTP cause I changed it to TCP only right away. I am on Mullvad as well. Using Wireguard. I'm running all of this in docker myself. I have the same host with both rTorretnVPN and qBitTorrentVPN. I have wireguard configs to the same place for both of them. rTorrentVPN maxes out my full 100Mbit connection. qBit maxes out at 10 and then fluctuates. I also have qbit at home and it's been really slow vs when I ran rtorrentvpn, which would almost max out my 1gb connection. I'm going to set qbit up on unraid and try it that way to rule out weirdness.

You curl to wherever you expect qbitorrent to be running. Wherever you expect that :8080 to be. It mimics your browser accessing it and it should say a bunch of stuff which you can post here. I guess you're using 8089 for your webui so :8089.

curl -v yourhost:8080

Is there anything obvious to check or change when I see speeds fluctuating like crazy? I already changed the protocol to TCP only. Seeing speeds 100Mbit/s - 0 - 100 constantly.

Edit: So much time wasted Creating this docker from scratch via the cli vs using portainer solved everything it seems Hi, I hope it’s ok to post here about this. I’m running these containers just on Linux, not unraid (although I do have unraid and did run it on there before). I have one host, Ubuntu running in a vm, where this container runs perfectly. I have another host, this time it’s a physical Debian machine, on which I get an error starting up - permission denied on key "net.ipv4.conf.all.src_valid_mark" Oddly enough, this same host is where I’ve been running rtorrentvpn, using the image on docker hub, for over a year without issue. I’m trying to move over to qbitorrentvpn. Any ideas? I guess the only major function difference is rtorrentvpn is running out of my home directory while I put this under opt. I configured this one using portainer, haven’t tried just running it manually via docker cmd, will do so today. It is set to run privileged. I basically duplicates the rtorrent config and made the necessary changes. What does that error even mean? It can’t read it? Edit: If I shell into the container, it cannot set that sysctl however it's already set to 1.

Makes sense, and again, thanks for all the work. I understand the frustration when something is flaky and just won't cooperate. I guess I don't use it that way cause I've had it running for 2 years now and it rarely ever crashes on me. It's been really good to me. Going to move over to one of these other projects

Oh I’m an idiot. I’m a refugee now from rtorrentvpn, didn’t even realize these alternatives existed Are you aware of any issues with rtorrentvpn which are really problematic? I’ve never really had any issues running the image from docker hub, everything works great and stable. Thanks for all the work! Might be time to migrate rtorrent to one of these. Just gotta make sure my trackers accept the client.

Does this project get any love anymore?

Tried building the latest code on Ubuntu and managed to get a different error now. Except that I can even ping that github ip from the host building this. #0 83.73 Successfully installed wheel-0.37.1 #0 84.09 Getting pyrobase... #0 84.09 Cloning into 'pyrobase'... #0 213.4 fatal: unable to connect to github.com: #0 213.4 github.com[0: 140.82.113.3]: errno=Connection timed out #0 213.4 ------ Dockerfile:27 -------------------- 26 | # make executable and run bash scripts to install app 27 | >>> RUN chmod +x /root/*.sh /home/nobody/*.sh && \ 28 | >>> /bin/bash /root/install.sh "${release_tag_name}" 29 | -------------------- ERROR: failed to solve: process "/bin/sh -c chmod +x /root/*.sh /home/nobody/*.sh && \t/bin/bash /root/install.sh \"${release_tag_name}\"" did not complete successfully: exit code: 128

Ok I managed to build the latest release. I'm getting errors when I try to start, 2023-01-30 23:29:58,623 INFO spawnerr: command at '/home/nobody/logrotate.sh' is not executable 2023-01-30 23:29:58,623 INFO spawnerr: command at '/home/nobody/pyrocore.sh' is not executable 2023-01-30 23:29:58,624 INFO spawnerr: command at '/home/nobody/rutorrent.sh' is not executable 2023-01-30 23:29:58,624 INFO spawnerr: command at '/home/nobody/watchdog.sh' is not executable 2023-01-30 23:30:01,628 INFO spawnerr: command at '/home/nobody/logrotate.sh' is not executable I hacked at it and +x those files but I think there's something fundamentally wrong. After +x to those files, tmux was missing for some reason. After installing that it still doesn't start just indicating that rtorrent wasn't able to start.

Is there some trick building this from source? I build it with just docker build . but that's not getting me very far right now It behaves very strange. When I build two images show up, one binhex/arch-int-vpn and another untagged one. A container also shows up that isn't tagged. I see from the docker build file that binhex/arch-int-vpn is pulled in as the base, so that makes sense.

For all who are running this as a container via docker, are you just pulling from docker hub or are you building it locally from source? The docker hub version is pretty old by now.

Funny you had this happen as I had the exact same issue. Turns out Mullvad actually had a bunch of server changes on Dec 28th. One of mine went offline as well and I had the exact same issue.

Is there any way to add more data directories or link to other disks by any chance?

Davos doesn't seem to be seeing new files which are added to a sub directory. For example, I have my root dir that it connects to and under that there is a folder where new content is added. The first time it ran it downloaded everything in this sub dir but now it doesn't see the new files which have been added since.