cedricve
commented
1 year ago Thanks @vadimzharov for the very detailed information! It looks like the agent is able to open the stream, but cannot read the packets (or just for some seconds). The behaviour below happens, if the agent is not able to read key frames.
{"level":"info","msg":"HandleStream: packet size 84577","time":"2022-12-01T02:03:06+01:00"}
{"level":"info","msg":"ControlAgent: Number of packets read 5","time":"2022-12-01T02:03:07+01:00"}
{"level":"info","msg":"ControlAgent: Number of packets read 5","time":"2022-12-01T02:03:12+01:00"}
{"level":"info","msg":"ControlAgent: Number of packets read 5","time":"2022-12-01T02:03:17+01:00"}
{"level":"info","msg":"ControlAgent: Number of packets read 5","time":"2022-12-01T02:03:22+01:00"}
{"level":"info","msg":"Main: Restarting machinery.","time":"2022-12-01T02:03:22+01:00"}The log is showing though that it is able to read the first key frame, but afterwards no new packets were able to read. The mechanism you see in place is that it checks if the stream is working for 4 times in a row, and if not it will restart the agent as an issue occurred with the stream (as it assumed that no new key frames means, a dead stream).
Please note that VLC and this Kerberos Agent are different. Kerberos Agent is more lightweight and doesn't contain fallback mechanisms as VLC, so if VLC processes a stream it might correct the stream on the fly to be able to view it.
My advise would be to look into the stream, and gather some more statistics using ffplay to know more about the headers. Also I would like to modify the ffmpeg configuration a bit, it might be that we need to force some attributes like keyframe interval.
vadimzharov
I have an USB camera on my Lenovo laptop (running Fedora 35 Linux) and I ran RTSP Simple server according to this guide https://github.com/kerberos-io/camera-to-rtsp to expose it via RTSP as a container.
The command I used is:
podman run --rm --name rtsp-server --network=host -d --privileged -v $PWD/rtsp-simple-server.yml:/rtsp-simple-server.yml kerberos/rtsp-simple-serverFile rtsp-simple-server.yml changed according to the doc, added lines:
The server is working and I can connect to the camera using VLC and see live video without any interruptions.
Then I ran agent using latest docker image using this command:
podman run --rm --name kerberos -p 8081:80 -d kerberos/agent:latestBoth containers are running on the same host (Lenovo with Fedora).
The agent is working and accessible via port 8081, and I can successfully add camera in agent UI using URL rtsp://:8554/usbcam - if I click Verify connection it saying Camera settings are successfully verified.
However, the Live view doesn't work - it shows nothing (only button Configure connection).
Also in the dashboard the message in IP camera frame is flipping from "Connected" to "Disconnected"
If I enable Continuous recording - then recording is happening - I see files available in Recordings - and each file has length 16-20 sec. It means agent can connect to the camera and do recordings, but looks like the connection is interrupting.
In rtsp-simple-server container I see following log messages:
Looks like the connection between agent and rtsp server is resetting each ~20 sec.
But this is not happening for VLC connection, it stays for any period of time, for example, if I open streaming in VLC:
It stays forever and finish only when I stop streaming in VLC with this message in logs:
Also I noticed in Agent container logs that machinery is restarting constantly:
Troubleshooting Done docker image kerberos/agent:latest I tried to run agent on separate RPI4 host - and I'm having the same issue (USB camera on Lenovo Laptop and agent on RPI) - connection resetting after ~20 sec.
Host Specs: Lenovo T260 with Fedora 36 + podman + USB camera Agent tested also on RPI4 with Ubuntu 22.04