pushes fail when one of the push destination times out #1573
Assignees
Labels
investigating
Being checked
Comments
|
The destination (OSP) had an internet hickup, and connections would stall. So I'm assuming that the output queue in OME just got bigger and bigger till it crashed. Perhaps if the queue grows too big, OME should consider the connection ended and try to reconnect. From the logs it looks like it only warns when the threshold is reached, but takes no action. Perhaps there can be a warning threshold and a kill threshold. I don't know if it already does this but that's my two cents. |
|
Hopefully this is resolved soon, one of the important features to us. |
|
Can you post your Server.xml? I'm curious to see your settings. |
|
I use this as a template on multiple servers: <?xml version="1.0" encoding="UTF-8" ?>
<Server version="8">
<Name>OvenMediaEngine</Name>
<Type>origin</Type>
<IP>*</IP>
<PrivacyProtection>false</PrivacyProtection>
<Modules>
<HTTP2><Enable>true</Enable></HTTP2>
<LLHLS><Enable>true</Enable></LLHLS>
</Modules>
<Bind>
<Managers>
<API>
<Port>60080</Port>
<TLSPort>60443</TLSPort>
<WorkerCount>1</WorkerCount>
</API>
</Managers>
<Providers>
<RTMP>
<Port>61935</Port>
<WorkerCount>1</WorkerCount>
</RTMP>
<SRT>
<Port>60999</Port>
<WorkerCount>1</WorkerCount>
</SRT>
</Providers>
<Publishers>
<LLHLS>
<Port>60080</Port>
<TLSPort>60443</TLSPort>
<WorkerCount>1</WorkerCount>
</LLHLS>
</Publishers>
</Bind>
<Managers>
<Host>
<Names>
<Name>localhost:60080</Name>
</Names>
<TLS>
<CertPath>cert.pem</CertPath>
<KeyPath>key.pem</KeyPath>
<ChainCertPath>cert.pem</ChainCertPath>
</TLS>
</Host>
<API>
<AccessToken>poopy</AccessToken>
<CrossDomains><Url>*</Url></CrossDomains>
</API>
</Managers>
<VirtualHosts>
<VirtualHost>
<Name>default</Name>
<Distribution>LiveJoiner</Distribution>
<Host>
<Names><Name>*</Name></Names>
<TLS>
<CertPath>cert.pem</CertPath>
<KeyPath>key.pem</KeyPath>
<ChainCertPath>cert.pem</ChainCertPath>
</TLS>
</Host>
<Applications>
<Application>
<Name>live</Name>
<Type>live</Type>
<Providers><RTMP/><SRT/></Providers>
<Publishers><RTMPPush></RTMPPush><LLHLS><CrossDomains><Url>*</Url></CrossDomains></LLHLS></Publishers>
<OutputProfiles>
<OutputProfile>
<Name>bypass_stream</Name>
<OutputStreamName>${OriginStreamName}</OutputStreamName>
<Encodes>
<Audio>
<Name>bypass_audio</Name>
<Bypass>true</Bypass>
</Audio>
<Video>
<Name>bypass_video</Name>
<Bypass>true</Bypass>
</Video>
</Encodes>
</OutputProfile>
</OutputProfiles>
</Application>
</Applications>
<AdmissionWebhooks>
<ControlServerUrl>http://localhost:9999/webhook/25</ControlServerUrl>
<SecretKey>asdf</SecretKey>
<Timeout>3000</Timeout>
<Enables>
<Providers>rtmp,srt</Providers>
<Publishers></Publishers>
</Enables>
</AdmissionWebhooks>
<CrossDomains>
<Url>*</Url>
</CrossDomains>
</VirtualHost>
</VirtualHosts>
</Server>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #1572
Originally posted by vampirefrog March 31, 2024
I was streaming to about 12 pushes, when one of them went down (I mean the target site to which I was streaming, which is an OSP instance), and then all the other pushes started going down. Below you can see all I could find in the log.
Is there some kind of time out setting, or a setting to not take the other pushes down when one is stuck? Or is this a bug in OME? It seems to be similar to this: #819
The text was updated successfully, but these errors were encountered: