-
Notifications
You must be signed in to change notification settings - Fork 48
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
Getting SIGABRTs #48
Comments
I'm seeing this in the console logs of HFC: This happens obviously on Startup in the static NativeTransport constructor when calling RegisterIcall. I think this is not related to the SIGABRT (Because SIGSEV) but since I'm trying to find out the reasons of all crashes we're experiencing I'm keeping the log here:
Also the line |
Using the new Mono 4.2.2.30 seems promising. We got higher performance and no more crashes. I'll update you when we have collected more information and experience with 4.2.2.30 |
We have intensively tested our server with hfc yesterday by using load/stress tests. When using the managed Listener on Mono 4.2.1, we used to achieve 130 rps and 5% failed responses due to crashes/timeouts in average. When using the native listener on Mono 4.2.1 we used to achieve around 85% of failed responses, mostly due to sigabrt. Wenn using the managed Listener on Mono 4.2.2 we achieved failed responses in the 0-0.5% field, and 130 rps in average. CPU was >100% with the managed Listener of course. No sigabrt, just Timeouts because of cpu limits. Using the native listener with 4.2.2 gave us double rps compared to the managed one, while CPU usage was at 20-25%. The error rate was 0-0.5%. No crashes, the errors were minor. We tested with and without involving I/O in the request handling, both were fine. We're now rolling this out on WIP projects to monitor the stability. |
Hi,
We're using supervisord which keeps mono-server-hyperfastcgi4 running, using the most current revision of HFC and Mono 4.2.1.
Our log shows that HFC crashed from time to time due to SIGABRT, "exit status 1" and SIGSEV.
That's the log:
Currently I'm trying to attach gdb to catch the SIGABRT signal (
(gdb) catch signal SIGABRT
) to hopefully get a stacktrace. For that I have to generate debug symbols for the libnative.Any hints what the reason of this could be, or how to find out what the reason is? Any help is appreciated, even if it is generic debugging help.
Thanks!
The text was updated successfully, but these errors were encountered: