10000 SRT Relay freezes and stops logging when trying to play multiple non published sources · Issue #42 · voc/srtrelay · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SRT Relay freezes and stops logging when trying to play multiple non published sources #42

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.

Sign up for GitHub

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

Jump to bottom
Open
jahaddow opened this issue Aug 20, 2024 · 6 comments
Open

SRT Relay freezes and stops logging when trying to play multiple non published sources #42

jahaddow opened this issue Aug 20, 2024 · 6 comments

Comments

@jahaddow
Copy link

We've successfully used SRT relay for a single source without any problems. However, we're now attempting to relay four sources simultaneously, and issues have started to arise.

Our OBS play sources are always active, with a reconnect delay set to 1 second.

The publish sources are not always active, but OBS picks them up quickly when they are.

The main issue we're facing is that the SRT relay seems to freeze after a few mins. When this happens, it stops logging any publish or play requests, effectively ceasing to function. Although the publish sources indicate that they are connected and sending data, the log remains empty. This issue seems to occur when OBS repeatedly attempts to connect to the four sources for a period of time.
@jahaddow jahaddow changed the title SRT Relay stops listening for requests SRT Relay Freezes and Stops Logging When Relaying Multiple Sources Simultaneously Aug 20, 2024
@jahaddow jahaddow changed the title SRT Relay Freezes and Stops Logging When Relaying Multiple Sources Simultaneously SRT Relay freezes and stops logging when trying to play multiple non published sources Aug 20, 2024
@dbussert
Copy link

I have the same symptoms posted here #34, are your logs the same? For me, it worked perfect doing plays for non-existing feeds in v1.1 but v.1.2 broke it

@jahaddow
Copy link
Author
jahaddow commented Oct 1, 2024

I have the same symptoms posted here #34, are your logs the same? For me, it worked perfect doing plays for non-existing feeds in v1.1 but v.1.2 broke it

I think so, I gave up on this last month and I'm using Mediamtx until it can be fixed. Are you still using v1.1 no issues?

@iSchluff
Copy link
Member
iSchluff commented Oct 1, 2024

will look into it

@dbussert
Copy link
dbussert commented Oct 1, 2024

I have the same symptoms posted here #34, are your logs the same? For me, it worked perfect doing plays for non-existing feeds in v1.1 but v.1.2 broke it

I think so, I gave up on this last month and I'm using Mediamtx until it can be fixed. Are you still using v1.1 no issues?

v1.1 has continued to work great, so I just use that.

@hanatyan128
Copy link
hanatyan128 commented Mar 4, 2025 •
edited
Loading

Hello, just FYI there is workaround of this issue.
Move the channel existence check into listenCallback and do not accept non-existence streamid.
d97b29f

I'm not sure but looks libsrt has vulnerable to rapid accept-close.

@dbussert
Copy link
dbussert commented Mar 4, 2025

Hello, just FYI there is workaround of this issue. Move the channel existence check into listenCallback and do not accept non-existence streamid. d97b29f

I'm not sure but looks libsrt has vulnerable to rapid accept-close.

@iSchluff could you look at that? This has been an issue for anything after v1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@iSchluff @dbussert @hanatyan128 @jahaddow
0