[Support]: Frigate server regularly crashing? #18140
Replies: 2 comments 7 replies
-
you're going to need to capture syslogs, there is no way to know why this might be happening |
Beta Was this translation helpful? Give feedback.
7 replies
-
In my case I had two problems going on. First, my CMOS battery was dead and second, I had an old Nvidia GPU (730 I think?) that was throwing errors left and right. After replacing the CMOS battery and removing that card I no longer have any issues with crashes or it not recovering from power loss/reboot situations on some occasions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
My Frigate server randomly crashes on a regular basis (a bit of an oxymoron but I hope you get what I mean). I'm not much of a Linux user, so I'm having trouble tracking down what exactly is happening. I can't tell if it's the OS (Ubuntu), Docker, or Frigate causing the crash. It locks up the whole PC and I'm unable to remote into it (it is headless - but plugging a screen/mouse/keyboard into does not help, there is no picture or response at all when it has crashed), the only way to get everything back up and running is to hold the power down in person and force a hard power down, then turn it back on and everything is fine again.
I added a daily cron to restart the system hoping that would help, and it seemed to a bit - but after thinking that would fix the issue and it running fine for a few days - I just got a crash in the middle of the day again today.
I'm hoping someone can help me track down what is going on before I go away for a 2 week vacation, don't really want to lose access to all of my cameras and have them all stop recording while I'm away!
I found some things online that said to check /var/crash - but when I try to open any of the files there then VS Code says there is an error and it can't open the file. I then found some people saying to check using
journalctl -b -1 -e
- but I don't really see anything wrong there? Not really 100% what I'm looking at/for though. This is the output I get before the last crash today occured:Also worth noting that I've rebuilt this server twice and it was doing this on both of those builds as well.
I have Google Coral m.2 in the system. I used to have a USB Coral plugged in too, but I removed that before this latest rebuild in case that was causing the issue.
I have Timeshift installed for backups and Visual Studio Code installed, plus Docker and Frigate. Everything else is just stock Ubuntu.
Should I rebuild again except just use Debian? I thought Ubuntu would be safe as a Debian derivative.
Thanks for any help on tracking down what is happening!!
Version
0.15.0-cea210d
What browser(s) are you using?
Firefox 138.0.1 (64-bit)
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
Amcrest ASH43-W
Screenshots of the Frigate UI's System metrics pages
system just crashed again while typing this up! Trying to get my wife to restart it again if she'll look at her phone and see my message. I'll update with screenshots here when I can.
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions