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
haproxy 2.0.0 snapshot 3f0b1d-9 quits (crashes?) on SIGBUS (signal 10) #137
Comments
I mean the daily snapshot; when built outside a git repository it tags itself as dev9. |
You meant |
I will try that and will update if anything happens. Sadly, it takes a while to manifest, and the core file is somehow not generated (even though it should be).
|
Thanks for your help. About the core file, the global option |
Seems like Thank you for help. |
set-dumpable's effect should be more limited on freebsd. Please make sure
you don't have any "user" nor "group" set in your config, as (at least on
linux) that also disables core dumps by default.
|
@wtarreau, thank you, your suggestion worked, with the child process running as root (but inside a chroot) I can get it to dump core. Built haproxy with debug info ( |
Got a core dump after the crash:
It looks like the offending thread is the first one in this backtrace. Which frames and what within them should I analyse (and what exactly) to post here? I would like to avoid sharing the core file itself as it likely has confidential data. |
@capflam, it seems to be working but the crash usually required a few hours (usually at least 10) to trigger, so I cannot really say I can properly test it before release. Thank you for the swift fix; closing this issue now. |
Ok, thanks. Reopen button is still there if it crash again :) |
Now approaching 23 hours of haproxy up-time with the debug snapshot from yesterday so it seems like the crash was indeed fixed. |
Nice. Thanks for your feedback ! |
Output of
haproxy -vv
anduname -a
What's the configuration?
Steps to reproduce the behavior
Actual behavior
haproxy exits (crashes?) without any action on the administrator's part:
Please note that this is FreeBSD and signal 10 is
SIGBUS
bus error, notSIGUSR1
as on Linux.Expected behavior
haproxy does not exit.
Do you have any idea what may have caused this?
Started after the upgrade to 2.0.0-3f0b1d-9. Did not run the 2.0.0 stable release for long enough to see if the bug manifests, as something in the stable release prevented the most visited website from working in Chrome (likely due to #127).
Prior to the upgrade haproxy 1.9.x was running for months without issues.
Do you have an idea how to solve the issue?
No ideas yet.
The text was updated successfully, but these errors were encountered: