-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Support]: Exception in thread Thread-12/13/14 #7257
Comments
What browser are you using? Something is breaking the websocket connection between the frontend and the backend |
@NickM-27 lot of different users with different kind of browsers from desktop to smartphone browsers, I'm not sure how to point each of them out. |
I've actually noticed this on 0.13.x as well - I haven't been able to pin it down, but I haven't really tried to look deeply into it as I'm still on 0.12 on my production machine. It's happened several times as my Mac/Firefox has gone to sleep with a camera streaming. I'll return a while later to a semi-crashed Frigate with a similar stack trace. |
At the very least the exception should be caught, but I've not seen this at all. I use mac + chrome and have definitely had computer fall asleep while streaming a camera before |
Right. When it happened to me a few weeks back I looked briefly at a commit history and didn't see any changes to the websocket code since 0.12. So I figured it was something else, and didn't dig any deeper. |
@LckySndays Just curious, are you using Frigate on Fully Kiosk browser on a tablet? |
@hawkeye217 I'm pretty sure no one using kiosk on my end, so it might not be the problem. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
2023-08-01 ghcr.io/blakeblackshear/frigate:dev-7d3e5c9 (Exception in thread Thread-XX)
2023-07-08 ghcr.io/blakeblackshear/frigate:dev-88fc0fa (Exception in thread Thread-XX)
2023-07-08 ghcr.io/blakeblackshear/frigate:dev-d6f82f9 (Exception in thread Thread-XX)
2023-07-07 ghcr.io/blakeblackshear/frigate:dev-00b9a49
2023-07-07 ghcr.io/blakeblackshear/frigate:dev-5259d51
2023-07-07 ghcr.io/blakeblackshear/frigate:dev-dd02958
2023-07-06 ghcr.io/blakeblackshear/frigate:dev-baf671b
2023-07-06 ghcr.io/blakeblackshear/frigate:dev-2fae9dc (Cannot start properly)
2023-07-02 ghcr.io/blakeblackshear/frigate:dev-83edf95 (Exception in thread Thread-XX)
2023-06-30 ghcr.io/blakeblackshear/frigate:dev-f3f9b36 (Exception in thread Thread-XX)
2023-06-19 ghcr.io/blakeblackshear/frigate:dev-7c1568f (Exception in thread Thread-XX)
|
This comment was marked as outdated.
This comment was marked as outdated.
These "Connection reset by peer" messages happen during normal usage of the frontend when the websocket is disconnected. It is not the source of the problems you are seeing and can be ignored. |
The brokenpipe error looks like the useful log message. |
The bad news is the brokenpipe error is still showing up even on recent build And yes the "Connection reset by peer" is not the source of problem but the "Exception in thread Thread-XX" follow up into Since sometimes the error log is just stop there without having the chance to log the "BrokenPipeError: [Errno 32] Broken pipe" afterward, of course it still need more testing to make sure all of this |
Showing up still in dev-3921a7f
|
It seems clear where the error is coming from, just not sure if it can be caught without consequences or more investigation needs to happen. I have been entirely unable to reproduce this issue myself. One thing I notice is that i have birdseye restream enabled, so perhaps there is some issue when it is not enabled. |
I have been running the stable again for a full week with same config etc, to make sure its not happening there and the result is that it run greatly without crashing at all. Below is the the earliest recorded Exception in thread Thread-XX logs from my testing. 2023-06-30 ghcr.io/blakeblackshear/frigate:dev-f3f9b36 (Exception in thread Thread-XX with BrokenPipe)
2023-06-14 ghcr.io/blakeblackshear/frigate:dev-ff1b5c8 (Exception in thread Thread-XX without BrokenPipe)
|
Difficulty is that both of those commits are unrelated to output.py and websockets in general so it would seem unlikely that they directly caused it. In any case, I think the more important part is why some users are seeing it and others are not, I have not seen this even one time. I'm going to create a PR to catch this and print debug info, perhaps it won't have any consequences catching and ignoring and at least won't caught a failure |
2023-06-12 ghcr.io/blakeblackshear/frigate:dev-ff90db3 (Exception in thread Thread-XX with BrokenPipe)
I only have 3 more build to test out |
I have enabled birdseye restream 3 days ago and the issue has gone away. Im still on dev-3921a7f which has the issue with birdseye restream disabled. Edit: spoke too soon,
for the record, my frigate box has a |
received same broken camera behavior, but different error. Instead of connection reset i get broken pipe.
|
Put up another PR to catch both |
I hope that we can just catch and ignore that without consequences, but in case that if we need to deal with it, I'm pretty sure that the cause of issue is this commit dev-ff90db3 So far I've been testing 1 previous build before that commit for 3 days and it still running just fine |
Hi guys, Only affects the Birdseye.
Frigate.yml "Birdseye" section:...
birdseye:
enabled: true
width: 3072
height: 2048
quality: 4
mode: continuous
restream: false
... Frigate Logs only show this exception several times.
The running instance of Frigate uses docker-compose. No errors there.● frigate.service - Docker Compose Application Service
Loaded: loaded (/etc/systemd/system/frigate.service; enabled; preset: disabled)
Active: active (exited) since Sun 2024-02-04 23:22:05 EST; 51min ago
Process: 1651 ExecStart=/usr/local/bin/docker-compose up -d (code=exited, status=0/SUCCESS)
Main PID: 1651 (code=exited, status=0/SUCCESS)
CPU: 116ms docker-compose logs -f frigate | morefrigate | s6-rc: info: service s6rc-fdholder: starting
frigate | s6-rc: info: service s6rc-oneshot-runner: starting
frigate | s6-rc: info: service s6rc-oneshot-runner successfully started
frigate | s6-rc: info: service fix-attrs: starting
frigate | s6-rc: info: service s6rc-fdholder successfully started
frigate | s6-rc: info: service fix-attrs successfully started
frigate | s6-rc: info: service legacy-cont-init: starting
frigate | s6-rc: info: service legacy-cont-init successfully started
frigate | s6-rc: info: service log-prepare: starting
frigate | s6-rc: info: service log-prepare successfully started
frigate | s6-rc: info: service nginx-log: starting
frigate | s6-rc: info: service go2rtc-log: starting
frigate | s6-rc: info: service frigate-log: starting
frigate | s6-rc: info: service nginx-log successfully started
frigate | s6-rc: info: service frigate-log successfully started
frigate | s6-rc: info: service go2rtc-log successfully started
frigate | s6-rc: info: service go2rtc: starting
frigate | s6-rc: info: service go2rtc successfully started
frigate | s6-rc: info: service go2rtc-healthcheck: starting
frigate | s6-rc: info: service frigate: starting
frigate | s6-rc: info: service frigate successfully started
frigate | s6-rc: info: service nginx: starting
frigate | s6-rc: info: service go2rtc-healthcheck successfully started
frigate | s6-rc: info: service nginx successfully started
frigate | s6-rc: info: service legacy-services: starting
frigate | 2024-02-04 23:22:05.541874931 [INFO] Preparing Frigate...
frigate | 2024-02-04 23:22:05.548417993 [INFO] Starting NGINX...
frigate | s6-rc: info: service legacy-services successfully started
frigate | 2024-02-04 23:22:05.810167389 [INFO] Starting Frigate...
frigate | 2024-02-04 23:22:05.810477330 [INFO] Removing stale config from last run...
frigate | rm: cannot remove '/dev/shm/go2rtc.yaml': Device or resource busy
frigate | 2024-02-04 23:22:05.821179991 [INFO] The go2rtc service exited with code 1 (by signal 0)
frigate | 2024-02-04 23:22:06.853657600 [INFO] Removing stale config from last run...
frigate | rm: cannot remove '/dev/shm/go2rtc.yaml': Device or resource busy
frigate | 2024-02-04 23:22:06.865831658 [INFO] The go2rtc service exited with code 1 (by signal 0)
frigate | 2024-02-04 23:22:07.885150042 [INFO] Removing stale config from last run...
frigate | rm: cannot remove '/dev/shm/go2rtc.yaml': Device or resource busy
... There is anything that I am missing in the release notes about any Birdseye changes in the config file or anywhere else? txs in advance... |
Describe the problem you are having
Roughly for the last month, my frigate crashed with the following Exception in thread Thread-12/13/14 almost once everyday. This error cause the Debug view for all camera not loading up but the Live view is working properly. Anyone know what may cause this issue?
Version
0.13.0-D0413E3
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
M.2
Network connection
Wired
Camera make and model
Hikvision DS-2CD3367WDV3-L
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: