[Support]: #7485
Comments
|
Need to let logs run longer before posting |
Sorry, I updated, I know it's a lot but it seemed like different info was showing up farther down didn't want to leave out anything. |
|
I'd suggest using preset-vaapi for hardware accel |
standby. |
|
I'm getting this: 2023-08-15 20:37:16.910871135 [2023-08-15 20:37:16] ffmpeg.living_room_cam.detect ERROR : Option hwaccel (use HW accelerated decoding) cannot be applied to output url vaapi -- you are trying to apply an input option to an output file or vice versa. Move this option before the file it belongs to. I'm pretty sure I'm doing the config right. cameras: weird because this was working. |
|
This is usually an issue with the GPU drivers on the host |
what is the recommended version of ubuntu server to use with frigate? I believe I am running the newest version. |
|
I would start by running |
I will do that when I get home from work. 😎 |
How do I get into the container? |
|
vainfo on the host: vainfo from frigate: |
|
the host is missing drivers then, you'll need to install them. Not sure how that would happen but must have been some sort of update done on the host if it was working previously |
you wouldn't have any idea how to do that or be able to point me in a direction would you? |
|
What is your CPU? |
|
So I was reading posts and saw something about that my integrated video, I hooked up a monitor and the video didn't seem to be working, got into the bios, set the integrated video to be the primary, so cameras are working except 1 of them I can see every stream except for the jsmpeg stream, lemee grab the logs. |
|
2023-08-16 20:05:27.026093257 [INFO] Starting Frigate... |
|
2023-08-16 20:17:27.985429268 [INFO] Preparing go2rtc config... |
|
this was working before so I'm not sure what is still wrong. |
|
it's crashing now on the mse stream too.
|
|
Enable trace logs for go2rtc go2rtc:
streams:
...
log:
exec: trace |
|
2023-08-16 21:35:34.533637603 [INFO] Preparing go2rtc config... |
|
Try removing |
|
2023-08-16 22:20:14.744881776 Last message repeated 2 times |
|
getting close lol |
|
also go2rtc dashboard gives a 404 error. |
|
also that kills audio on the office camera :\ |
|
apparently the audio settings from that camera reverted and were not AAC anymore, I think I am good to go but I will test everything tomorrow and report back. |
|
Okay so literally the only issue I am having is when I try to use the mse stream with this one camera in the living room its fine until I try to do audio and then I get this in the logs. size=N/A time=00:00:44.58 bitrate=N/A speed=0.995x audio settings are pretty basic. any ideas? I would like to say audio was working with mse before but I can't remember now. |
yeah as soon as I click the speaker I either get a jittery studdery sound or it crashes and I get this. I'll check out that link. webrtc audio works fine, weird. |
|
am I downloading this? |
|
yes, the one that is appropriate for your machine |
|
I grabbed go2rtc_linux_amd64 which should be correct for ubuntu server 64 bit, renamed it go2rtc, made it executable, and put it into the config folder where the config.yaml is and restarted frigate and the log still shows 1.2, do I need to restart the docker container? |
|
if you are using docker compose / docker cli, you need to make sure that the entire /config directory is mapped and not just the config file |
|
got ya, so instead of the default I want this? |
|
yes |
|
stopped docker service restarted and it still says go2rtc version 1.2.0 linux/amd64 |
|
what did you run to make it executable? |
|
chmod 777 go2rtc, I know, super insecure but I was lazy haha it shows -rwxrwxrwx it should definately be able to execute. |
|
what do the go2rtc logs show? |
|
2023-08-17 08:59:33.747439980 [INFO] Preparing go2rtc config... and then all the other stuff. |
|
so it seems like it isn't trying to use the custom version which seems to imply it does not see the file. Can you show your full docker config? |
|
|
This seems kind of wrong, you have |
I wanted to run the db on my solid state drive instead of the big slow drive I have my videos on so I put it into the config folder. |
|
Right, but you shouldn't have identical mounts. I'd suggest removing the mount for /db entirely and just have in the config |
|
in my config.yaml I have database: do I need to remove ?
|
|
I am suggesting you remove with |
oohh got ya, stand by. |
|
okay so I did that, it still shows go2rtc version 1.2.0 linux/amd64 and while it's working I don't see the db in the config folder now, no idea where it went, it's not in media either. |
|
find / -name frigate.db |
|
did you do |
|
seems like something is very off here, either the docker compose changes are not being applied correctly or something is causing issues |
|
I didn't, I guess I assumed when you start the service it re reads the compose file, sorry, still kinda new to docker, hold on. |
|
okay db looks good, go2rtc seems to be working now, I'm testing, thanks man, the docs were definitely confusing when I set up moving the db haha. but I think I may be good now. The next version of frigate will have 1.6 go2rtc won't it? Will I need to just delete the file I downloaded so that it keeps using whatever version frigate comes with in the future? |
yes, you will just want to delete the custom go2rtc file the next version of frigate will also move the database to have a default location of /config/frigate.db |
|
feel free to create a new issue if something else comes up |
|
Will do, so far the audio has been solid, thanks a lot! Take it easy! |
Describe the problem you are having
Frigate was fine, now camera feeds won't display. Camera feeds working fine in VLC, nothing has changed in the config.
Version
0.12.1-367d724
Frigate config file
Relevant log output
FFprobe output from your camera
[{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"15/1","codec_long_name":"H.264/AVC/MPEG-4AVC/MPEG-4part10","height":1080,"width":1920},{"avg_frame_rate":"0/0","bit_rate":"64000","codec_long_name":"PCMmu-law/G.711mu-law"}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"6/1","codec_long_name":"H.264/AVC/MPEG-4AVC/MPEG-4part10","height":480,"width":704},{"avg_frame_rate":"0/0","bit_rate":"64000","codec_long_name":"PCMmu-law/G.711mu-law"}]}}]Frigate stats
No response
Operating system
Other Linux
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
dahua and hikvision
Any other information that may be helpful
I also get this under gpu's
error-gpu
There was an error getting usage stats. This does not mean hardware acceleration is not working. Either your GPU does not support this or Frigate does not have proper access to get statistics. This is expected for the Home Assistant addon.
The text was updated successfully, but these errors were encountered: