-
-
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
SIGSEGV interrupt after TLS warning without having TLS enabled #1721
Comments
Since there is no need to use TLS in the It is likely that an issue such as a stack overflow may have caused incorrect execution. For a more detailed analysis, please share the full logs, |
Here's the server configuration for the origin:
I wasn't able to get any dumps from as the K8s container was deleted |
@bartvp1 |
These are the startup logs, I wasn't able to retrieve any other logs before the crash since they havent been persisted
|
@bartvp1 If you could mount the |
Thank you, I'll post the logs here when this problem appears again! |
This issue was caused by a 524 Timeout from the admission webhook (cloudflare, using https). Another observation: Even though the timeout was set to 3000ms i the origin server config, it would sometimes take up to a minute for the SSL warning to show up and kill OME. |
@bartvp1 |
Since the root cause has been resolved (timeout between Cloudflare and the admission webhook server), I can't reproduce this anymore either. So the only issue remaining is the timeout ( |
@bartvp1 Regarding the |
Describe the bug
Even though I dont use TLS in my OvenMediaEngine configuration, it still occasionally warns about not being able to do something related to TLS, which often coincides with a crash of the Origin server.
I can't confirm whether this is related to the TLS warning, but since most crashes end with these same warnings I have my suspicions.
To Reproduce
No steps to reproduce, this seems to happen out of the blue
Expected behavior
I would expect there not to be any logs or crashes related to TLS if I'm not using any TLS for this service, because the load balancer terminates it.
Logs
Origin:
Server
The text was updated successfully, but these errors were encountered: