-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
With threaded on, SIGSEGV occurs during a dry run #9355
Comments
This also fails with the container image when using $ docker run --rm -it -v $PWD/fluent-bit.conf:/fluent-bit/etc/fluent-bit.conf:ro fluent/fluent-bit:3.1.7 -c /fluent-bit/etc/fluent-bit.conf --dry-run
Fluent Bit v3.1.7
* Copyright (C) 2015-2024 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
______ _ _ ______ _ _ _____ __
| ___| | | | | ___ (_) | |____ |/ |
| |_ | |_ _ ___ _ __ | |_ | |_/ /_| |_ __ __ / /`| |
| _| | | | | |/ _ \ '_ \| __| | ___ \ | __| \ \ / / \ \ | |
| | | | |_| | __/ | | | |_ | |_/ / | |_ \ V /.___/ /_| |_
\_| |_|\__,_|\___|_| |_|\__| \____/|_|\__| \_/ \____(_)___/
configuration test is successful
[2024/09/06 10:01:36] [engine] caught signal (SIGSEGV)
#0 0xaaaae293bd9b in flb_input_exit_all() at src/flb_input.c:1341
#1 0xaaaae2951fbb in flb_engine_shutdown() at src/flb_engine.c:1121
#2 0xaaaae2930c4f in flb_destroy() at src/flb_lib.c:240
#3 0xaaaae28c693f in flb_main() at src/fluent-bit.c:1360
#4 0xffff7f47777f in ???() at ???:0
#5 0xffff7f477857 in ???() at ???:0
#6 0xaaaae28c466f in ???() at ???:0
#7 0xffffffffffffffff in ???() at ???:0
$ cat fluent-bit.conf
[SERVICE]
flush 1
daemon Off
log_level info
parsers_file parsers.conf
plugins_file plugins.conf
http_server On
http_listen 0.0.0.0
http_port 2020
[INPUT]
name cpu
tag cpu.local
interval_sec 1
threaded on
[OUTPUT]
name stdout
match * |
Removing the |
Using the debug image also fails:
|
I am also getting this issue but the message while tracing it is different Thread 11 "flb-pipeline" received signal SIGSEGV, Segmentation fault. (gdb) continue Thread 11 "flb-pipeline" received signal SIGABRT, Aborted. (gdb) info locals |
Bug Report
Describe the bug
With threaded on, SIGSEGV occurs during a dry run
To Reproduce
remove "threaded on", it works.
Expected behavior
--dry-run should work with threaded on
Your Environment
The text was updated successfully, but these errors were encountered: