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
ATS 10.0.0 crashes with segmentation fault SIG 11 #8952
Comments
demangled stack:
|
As per my conversation in slack . In the diags.log This Note is also being logged [Jul 11 22:18:11.768] [ET_NET 6] NOTE: Cannot update aggregate field; invalid operator 0 |
The issue was in my configuration in the logging.yaml It was a bad configuration as i was trying to create a summary log. This caused the above notes as
SO these have been mitigated now. But i am again seeing some crashes with I think are related to configuration as well
I am monitoring the situation and will update . |
so i did a gdb debugging for the crash and using bt in gdb i got
|
Hi @NischalBhandari . Thank you for the update! This latter crash is different than the first. Can you please file a separate issue for that newer crash? For the original logging crash, can you provide the |
The error configuration that caused the issue in the logging.yaml was as follows So i think we can close the issue for this error.
|
I am trying to rewrite a header for a video streaming website where i am using a header_rewrite plugin to just convert a origin server response of 4xx code to 200 and also add certain headers. This essentially is a preflight request. This is not important but after the request is accepted and after that the video starts streaming but after some time the traffic server restarts .
The crashlog is a SIG 11 : Segmentation Fault but after that I do not know how to resolve the issue.
Just Before the crash in traffic.out file shows the following and a crash report is also generated but i don't know how to read the crashlog.
The text was updated successfully, but these errors were encountered: