-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
docker-srs:3 kill HTTP-FLV client container will exit automatically #1629
Comments
Unable to reproduce the issue, please reproduce the issue first and describe the reproduction steps.
|
Hello, today when I was testing, I discovered a pattern:
Additionally, I also found that the interface http://127.0.0.1:1985/api/v1/clients still cannot monitor the HLS streaming clients.
|
Great, I will try the kickoff of FLV, and if it can be reproduced, I will fix it quickly.
|
Ok, thank you!
|
Reproduced, it will cause SRS crash and exit.
|
Due to the lack of a connection (conn=0x0) for the API client during HTTP-FLV playback, it results in a null pointer reference when attempting to kick HTTP-FLV.
|
Already resolved:
|
docker-srs:3 kill client container will exit automatically
docker-srs:3
As you can see, I made a request to the built-in API of SRS to get the clients, and then killed one client. As a result, the container automatically exited. This is why I am hesitant to perform the kill action on the production server. This issue does not occur every time I kill a client. I have noticed that sometimes it happens, while other times the SRS container does not exit.
This is a very critical issue with the SRS API, which makes me hesitant to perform any actions on users who are watching live streams in a non-conventional way. It is important to resolve this issue promptly.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: