[Support]: On TrueNAS APP: Restart from the UI is not working #16108
Replies: 2 comments 6 replies
-
The logs show that Frigate stops and exits successfully. Your issue is likely related to truenas. We don't produce the truenas app so we can't provide support for it. |
Beta Was this translation helpful? Give feedback.
-
|
the problem is likely the default restart_mode |
Beta Was this translation helpful? Give feedback.
-
|
The restart mode is unless_stoped |
Beta Was this translation helpful? Give feedback.
-
|
You might also glean assistance by asking in the forum at https://forums.truenas.com/ You could perhaps try a very simple config to see if it will work, and then build up to the full requirement. I use TrueNAS to host their official Frigate app. I have had many problems, often of my own making, and I have found that deleting the app and the associated image and then reinstalling from scratch can fix things sometimes. If these ideas don't work, I can post screenshots of my app settings in the hope that they might help you. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answer. So in your case in the official app of truenas you can restart it from the ui? Then i will try to deinstall everything and install it again. |
Beta Was this translation helpful? Give feedback.
-
|
Yes - take a copy of your config if the Frigate UI is running, and then inside the TrueNAS app UI region here:
delete Frigate by ticking the box which says "delete":
and then tick both of these boxes:
I has helped me in the past with frigate problems on trueNAS, but not this time: I have an ongoing problem ...Frigate runs with maybe 25% of my NAS CPU being used by Frgate and the inference time is 8 ms or 10 ms ...then suddenly after an hour or two the total CPU due to Frigate jumps up to at least 50% and the total TrueNAS CPU use is >80 or even 90% and the TPU inference time gets longer to maybe 30 ms or even 60 ms. The problem is to do with the Frigate App from TrueNAS, or to do with Electric Eel, or both. The earlier app (Frigate 0.13.2) was OK on Dragonfish but EE requires 0.14.2 and now I have these problems. Nobody seems to know why! |
Beta Was this translation helpful? Give feedback.
-
|
OK Thanks i will try that. I have also long a problem with frigate sinze the update to Electric Eel and nobody have found a solution. After a long time, i have found the problem. Maby it can also help in your case. In the App settings of frigate in the truenas UI. The last point. How many CPUs you have there? |
Beta Was this translation helpful? Give feedback.
-
|
@Danit2 this is very interesting. I had my app set to "4" CPUs so I increased it to "8". My Xeon is 4 cores but each is dual threaded allowing me 8 threads in total. I have started the app and this time, so far, it is remaining at low inference times and low CPU demand. The thread I mentioned earlier shows some graphs. I will continue to update it as the day wears on, to see if the problem is fixed or if it is just random luck. In any case, thanks for your help! |
Beta Was this translation helpful? Give feedback.
-
Checklist
Describe the problem you are having
When i want to restart frigate from the WebUI it is not working.
Also when the app crash, the app won't restart.
You can also not press the Start/Stop button because the status is "starting". You have to "edit" and "update" the app to restart.
What can i do?
Issue also open at the channel of TrueNAS Apps: truenas/apps#1404
Steps to reproduce
...
Version
0.14.1-f4f3cfa
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Other Linux
Install method
Docker Compose
Network connection
Mixed
Camera make and model
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions