-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Crash 6.2.0 : Flare.cc: zeek::detail::bad_pipe_op #3682
Comments
I'm seeing similar crashes with 6.0.3 (standalone):
Unfortunately I did not have debugging symbols enabled (I do now). |
Dang, I was really hoping this was something specific to 6.2. |
I had my first crash since building with debugging symbols (RELWITHDEBINFO) but I'm not sure that it's related:
The fatal error was:
|
I lied, I see now I had crash a week ago that looks related to this problem:
And the log says:
(The same error as today so maybe that was related but the stack got trashed...) So maybe the process on the other end of the pipe is gone and EBADF should not be fatal? Happy to make files available for analysis (note that the debugging symbol zeek is quite large...) |
Can reproduce back to 4.0.9 with the following script. It happens instantaneously on 6.0+ likely due to the more efficient/aggressive IO loop. The crux for the reproducer is the much lowered
Abort
ASAN
Reproducer
|
I don't quite know how to fix this yet, but I'll assign myself for now. |
I have been seeing intermittent crashes in 6.2.0 with the following coredump:
For reference:
I'll try to see how I can replicate it - so far different physical clusters have showing this crash - albeit very intermittent - I don't see a predictive pattern yet!
The text was updated successfully, but these errors were encountered: