Skip to content
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

Segfault randomly happens with in_health #135

Closed
nokute78 opened this issue Nov 18, 2016 · 1 comment
Closed

Segfault randomly happens with in_health #135

nokute78 opened this issue Nov 18, 2016 · 1 comment
Assignees

Comments

@nokute78
Copy link
Collaborator

How to reproduce

  • $ bin/fluent-bit -i health://google.com:80 -o stdout -vvv

Note

Segfault is randomly happened.
However it seems to be happen after outputting this log and it's id >= 2.

[2016/11/18 22:54:49] [debug] [input] destroy input_thread id=3

Log

$ bin/fluent-bit -i health://google.com:80 -o stdout -vvv
Fluent-Bit v0.10.0
Copyright (C) Treasure Data

[2016/11/18 22:54:28] [ info] [engine] started
[2016/11/18 22:54:28] [debug] [router] default match rule health.0:stdout.0
[2016/11/18 22:54:29] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:30] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:31] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:32] [debug] [input] destroy input_thread id=0
[0] health.0: [1479477269, {"alive"=>true}]
[1] health.0: [1479477270, {"alive"=>true}]
[2] health.0: [1479477271, {"alive"=>true}]
[3] health.0: [1479477272, {"alive"=>true}]
[2016/11/18 22:54:33] [debug] [task] created task=0x1dc9cf0 id=0 OK
[2016/11/18 22:54:35] [debug] [task] destroy task=0x1dc9cf0 (task_id=0)
[2016/11/18 22:54:35] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:35] [debug] [input] destroy input_thread id=1
[2016/11/18 22:54:36] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:37] [debug] [input] destroy input_thread id=0
[0] health.0: [1479477275, {"alive"=>true}]
[1] health.0: [1479477275, {"alive"=>true}]
[2] health.0: [1479477276, {"alive"=>true}]
[3] health.0: [1479477277, {"alive"=>true}]
[2016/11/18 22:54:38] [debug] [task] created task=0x1dc81e0 id=0 OK
[2016/11/18 22:54:38] [debug] [task] destroy task=0x1dc81e0 (task_id=0)
[2016/11/18 22:54:38] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:39] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:40] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:41] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:42] [debug] [input] destroy input_thread id=0
[0] health.0: [1479477278, {"alive"=>true}]
[1] health.0: [1479477279, {"alive"=>true}]
[2] health.0: [1479477280, {"alive"=>true}]
[3] health.0: [1479477281, {"alive"=>true}]
[4] health.0: [1479477282, {"alive"=>true}]
[2016/11/18 22:54:43] [debug] [task] created task=0x1dc1f20 id=0 OK
[2016/11/18 22:54:47] [debug] [task] destroy task=0x1dc1f20 (task_id=0)
[2016/11/18 22:54:49] [debug] [task] created task=0x1dc2320 id=0 OK
[0] health.0: [1479477289, {"alive"=>true}]
[2016/11/18 22:54:49] [debug] [input] destroy input_thread id=0
[2016/11/18 22:54:49] [debug] [task] destroy task=0x1dc2320 (task_id=0)
[2016/11/18 22:54:49] [debug] [input] destroy input_thread id=2
[2016/11/18 22:54:49] [debug] [input] destroy input_thread id=3
Segmentation fault
@edsiper edsiper self-assigned this Nov 18, 2016
@edsiper
Copy link
Member

edsiper commented Nov 18, 2016

thanks for catching this. Fixed now (applying fix to 0.9 branch too)

edsiper added a commit that referenced this issue Nov 18, 2016
The current input plugins when running in a co-routine, was doing a
wrong thread deletion, instead of delete the thread associated with
a specific ID, it was deleting 'all threads contexts', leading to
a segfault when using in_health plugin.

This patch let the input thread deletion just focus on the thread
associated to the given id.

Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
edsiper added a commit that referenced this issue Nov 21, 2016
The current input plugins when running in a co-routine, was doing a
wrong thread deletion, instead of delete the thread associated with
a specific ID, it was deleting 'all threads contexts', leading to
a segfault when using in_health plugin.

This patch let the input thread deletion just focus on the thread
associated to the given id.

Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
rawahars pushed a commit to rawahars/fluent-bit that referenced this issue Oct 24, 2022
…ent#135)

Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants