BurningSky
Members-
Posts
48 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
BurningSky's Achievements
-
The server recovers by itself, how long would I need to stay in safe mode for. I'll close the browser but I've always had it open before so not sure why that would start to be the issue now?
-
I've had Unraid hang twice in the last 24 hours, both times for around 20-40 minutes, before recovering again. Syslog looks the same for both times, messages about disk temps being around 30C followed by "nginx: 2024/03/20 14:00:29 [error] 831#831: *31271114 limiting requests, excess: 21.000 by zone "authlimit", client: 192.168.3.30, server: , request: "GET /login HTTP/2.0"" then "php-fpm[7716]: [WARNING] [pool www] child 10760 exited on signal 9 (SIGKILL) after 936.425570 seconds from start" type messages. Any insights would be appreciated! ragon-diagnostics-20240320-1616.zip
-
Thanks, it happened again so I'll format the cache once I've copied data off
-
Thanks for the feedback, I'll keep an eye on it. Doesn't point to a disk failure though?
-
I noticed a container had stopped with a message about the log being RO so having looked at a couple of other similar looking issues decided to delete the docker.img to see if that would help. After that the Docker service wouldn't restart and I noticed in the logs it looked like a cache issue so I rebooted to see if that would resolve it. That let to the cache showing an "Unmountable: unsupported or no file system" error. Based on another forum post I ran "btrfs rescue zero-log /dev/sdi1" and restared the array and the pool appears to be back now but I'm worried if there is a deeper issue? I've attached 2 sets of logs, 1411 was before I ran the rescue command and 1414 is after. Does it look like sdi1 is going to fail or was there another potential cause. ragon-diagnostics-20240208-1414.zip ragon-diagnostics-20240208-1411.zip
-
[support] digiblur's Docker Template Repository
BurningSky replied to digiblur's topic in Docker Containers
Ah of course! Thanks, forgot about the tags webpage! -
Syslog filling with device eth0 entered/left promiscuous mode
BurningSky replied to BurningSky's topic in General Support
Found the culprit, it was Pi Alert, so that has been removed now! -
[support] digiblur's Docker Template Repository
BurningSky replied to digiblur's topic in Docker Containers
I'm having the same issue so might downgrade until there seems to be a resolution, how do I do that on this container? Would setting the repo to koenkk/zigbee2mqtt:1.35.1 work? -
Syslog filling with device eth0 entered/left promiscuous mode
BurningSky replied to BurningSky's topic in General Support
I checked this morning and there haven't been any containers that have restarted in line with the messages. I updated 2 containers 18mins ago so they show as more recent status, the others are 29+ hours but in the last 18mins there have been 7 more messages. Is there anything else I should be looking at rather than just status on docker ps? -
I just got a message that my /var/log is getting full and when I look there are hundreds of repeats of Jan 21 10:03:35 Ragon kernel: device eth0 left promiscuous mode Jan 21 10:06:51 Ragon kernel: device eth0 entered promiscuous mode I've seen some people mention similar issues with multiple dockers on the same port but I can't see any similar issues, most of my containers are on br0 if they use a repeated port like 8080 with their own IPs. I have a Realtek NIC but I've installed the driver from CA for that. ragon-diagnostics-20240121-1004.zip
-
PCIe passed through to Docker giving multiple errors
BurningSky replied to BurningSky's topic in General Support
After doing some digging I've added pcie_aspm=off to my syslinux config so I will see if that resolves the issue. -
I have a mPCIe Coral TPU connected to a PCIe to mPCIe adaptor which is then passed through to Frigate Docker which seems to be working but today I got a notification that my syslog is filling up and I've had a look and see this error relating to the Coral device but I don't know what could be causing this error? The Docker container is running in priviledged mode and passed through via /dev/apex_0 Nov 5 08:46:19 Ragon kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0 Nov 5 08:46:19 Ragon kernel: apex 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Nov 5 08:46:19 Ragon kernel: apex 0000:25:00.0: device [1ac1:089a] error status/mask=00000041/00006000 Nov 5 08:46:19 Ragon kernel: apex 0000:25:00.0: [ 0] RxErr Nov 5 08:46:19 Ragon kernel: apex 0000:25:00.0: [ 6] BadTLP ragon-diagnostics-20231105-0852.zip
-
I didn't realise you couldn't have 2 types of detectors at the same time! Commented out the cuda one and it's working now!
-
I sent back the Coral USB I was having issues with and have swapped it with a mini PCIE one which I have connected to a PCIE to mPCIE adaptor but I am still having some issues. I have installed the drivers and it is being recognised by the Coral Driver app: Coral TPU1: Status: ALIVE Temperature: 39.30 °C Frequency: 500 MHz Driver Version: 1.2 Framework Version: 1.1.4 I can also see the device under sysdevs: [1ac1:089a] 25:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU I had previously deleted the section for mapping the TPU but I have readded it with the following: Config Type: Device Name: Coral TPU/NCS2 Mapping Value: /dev/apex_0 Description: Use /dev/bus/usb for USB devices and /dev/apex_0 for PCIe devices (you must install the drivers first for PCIe devices). Remove this if you are not using it. In Frigate I added the following to detectors: detectors: coral: type: edgetpu device: pci But I get an error saying that no EdgeTPU was detected, have I misconfigured something? 2023-11-03 12:49:18.767219029 [INFO] Preparing go2rtc config... 2023-11-03 12:49:18.767580529 [INFO] Starting Frigate... 2023-11-03 12:49:18.768623682 [INFO] Starting NGINX... 2023-11-03 12:49:18.957519850 [WARN] Using go2rtc binary from '/config/go2rtc' instead of the embedded one 2023-11-03 12:49:18.960160839 [INFO] Starting go2rtc... 2023-11-03 12:49:19.063972373 12:49:19.063 INF go2rtc version 1.8.1 linux/amd64 2023-11-03 12:49:19.064282260 12:49:19.064 INF [api] listen addr=0.0.0.0:1984 2023-11-03 12:49:19.064866554 12:49:19.064 INF [rtsp] listen addr=0.0.0.0:8554 2023-11-03 12:49:19.064871792 12:49:19.064 INF [webrtc] listen addr=0.0.0.0:8555/tcp 2023-11-03 12:49:19.771751395 [2023-11-03 12:49:19] frigate.app INFO : Starting Frigate (0.12.1-367d724) 2023-11-03 12:49:19.811722914 [2023-11-03 12:49:19] peewee_migrate INFO : Starting migrations 2023-11-03 12:49:19.815743064 [2023-11-03 12:49:19] peewee_migrate INFO : There is nothing to migrate 2023-11-03 12:49:19.840242161 [2023-11-03 12:49:19] detector.coral INFO : Starting detection process: 577 2023-11-03 12:49:19.956163315 [2023-11-03 12:49:19] detector.cuda INFO : Starting detection process: 580 2023-11-03 12:49:19.956171347 [2023-11-03 12:49:19] frigate.app INFO : Output process started: 585 2023-11-03 12:49:19.956179867 [2023-11-03 12:49:19] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as pci 2023-11-03 12:49:19.956187410 Process detector:coral: 2023-11-03 12:49:19.956194534 [2023-11-03 12:49:19] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-11-03 12:49:19.956218629 [2023-11-03 12:49:19] frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Is there any way to check if the docker is actually seeing the device?
-
Thanks for that, I'll check the cables for the parity disk. What did you notice in the logs that led you to believe that?