Skip to content

docker-srs:3 kill HTTP-FLV client container will exit automatically #1629

Closed
@yangxiangzhi

Description

docker-srs:3 kill client container will exit automatically

  1. SRS version: docker-srs:3
  2. SRS logs are as follows:
container-srs   | [2020-03-05 10:18:03.193][Trace][1][1086] HTTP API GET http://docker-srs:1985/api/v1/clients?start=0&count=10000, content-length=-1, chunk
ed=0/0
container-srs   | [2020-03-05 10:18:03.193][Trace][1][1086] client finished.
container-srs   | [2020-03-05 10:18:03.206][Trace][1][1087] API server client, ip=172.20.0.5
container-srs   | [2020-03-05 10:18:03.206][Trace][1][1087] HTTP API GET http://docker-srs:1985/api/v1/clients/?start=0&count=10000, content-length=-1, chun
ked=0/0
container-srs   | [2020-03-05 10:18:03.206][Trace][1][1087] client finished.
container-srs   | [2020-03-05 10:18:03.355][Trace][1][1088] API server client, ip=172.20.0.5
container-srs   | [2020-03-05 10:18:03.355][Trace][1][1088] HTTP API DELETE http://docker-srs:1985/api/v1/clients/1079, content-length=-1, chunked=0/0
container-srs exited with code 139

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

Metadata

Assignees

Labels

BugIt might be a bug.TransByAITranslated by AI/GPT.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions