-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Admission Webhook not called when forcefully closing RTMP client #1570
Comments
OME may not be aware that the RTMP session has been disconnected. If TCP keepalive is working, OME will notice the tcp connection termination after several tens of seconds. Admission webhooks aren't being called even though the log shows the stream has been deleted? |
The logs don't show anything in regard to the disconnected RTMP client. |
Any updates on this issue? I need this feature because I need to keep track of active streams in a separate, realtime database. |
The server doesn't notice that the TCP connection between the RTMP client and the server has been lost. You might want to look into setting up TCP Keepalive on the server. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
The admission webhook for closing RTMP streams is not called when a it closes unexpectedly
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The admission webhook should be called with the information of the cancelled RTMP stream
Server
The text was updated successfully, but these errors were encountered: