8000 Crash Output + Forward + TLS + ARM · Issue #8786 · fluent/fluent-bit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Crash Output + Forward + TLS + ARM #8786

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.

Sign up for GitHub

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

Jump to bottom
Open
pcasaspere opened this issue May 2, 2024 · 8 comments
Open

Crash Output + Forward + TLS + ARM #8786

pcasaspere opened this issue May 2, 2024 · 8 comments
Labels
status: waiting-for-triage

Comments

@pcasaspere
Copy link

Bug Report

Describe the bug
When I use OUTPUT + FORWARD + TLS on my Raspberry Pi armv7, I experience a SIGSEGV error.
I've tried to run it with same setup into another system, like ubuntu 24.04 amd64, and it've ran without crash.

To Reproduce
Client config

[SERVICE]
    flush        1
    log_level trace    
    parsers_file parsers.conf

[INPUT]
    Name   dummy
    Tag    dummy
    Samples 3
    Dummy {"message": "custom dummy"}
    Flush_on_startup true

[OUTPUT]
    Name          forward
    Match         *
    Host          xxx.xxx.xxx.xxx
    Port          242244
    tls           on
    tls.verify    off
    tls.debug     4

Server config

[SERVICE]
    flush        1
    log_level    info
    parsers_file parsers.conf
    plugins_file plugins.conf

[INPUT]
    Name              forward
    Listen            0.0.0.0
    Port              24224
    Buffer_Chunk_Size 1M
    Buffer_Max_Size   6M
    tls               on
    tls.verify        off
    tls.crt_file      /etc/fluent-bit/certs/server.crt
    tls.key_file      /etc/fluent-bit/certs/server.key
  • Steps to reproduce the problem:
/opt/fluent-bit/bin/fluent-bit -c fluent-bit.conf
Fluent Bit v3.0.3
* Copyright (C) 2015-2024 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

___________.__                        __    __________.__  __          ________  
\_   _____/|  |  __ __   ____   _____/  |_  \______   \__|/  |_  ___  _\_____  \ 
 |    __)  |  | |  |  \_/ __ \ /    \   __\  |    |  _/  \   __\ \  \/ / _(__  < 
 |     \   |  |_|  |  /\  ___/|   |  \  |    |    |   \  ||  |    \   / /       \
 \___  /   |____/____/  \___  >___|  /__|    |______  /__||__|     \_/ /______  /
     \/                     \/     \/               \/                        \/ 

[2024/05/02 19:37:58] [ info] Configuration:
[2024/05/02 19:37:58] [ info]  flush time     | 1.000000 seconds
[2024/05/02 19:37:58] [ info]  grace          | 5 seconds
[2024/05/02 19:37:58] [ info]  daemon         | 0
[2024/05/02 19:37:58] [ info] ___________
[2024/05/02 19:37:58] [ info]  inputs:
[2024/05/02 19:37:58] [ info]      dummy
[2024/05/02 19:37:58] [ info] ___________
[2024/05/02 19:37:58] [ info]  filters:
[2024/05/02 19:37:58] [ info] ___________
[2024/05/02 19:37:58] [ info]  outputs:
[2024/05/02 19:37:58] [ info]      forward.0
[2024/05/02 19:37:58] [ info] ___________
[2024/05/02 19:37:58] [ info]  collectors:
[2024/05/02 19:37:58] [ info] [fluent bit] version=3.0.3, commit=, pid=13380
[2024/05/02 19:37:58] [debug] [engine] coroutine stack size: 24576 bytes (24.0K)
[2024/05/02 19:37:58] [ info] [storage] ver=1.5.2, type=memory, sync=normal, checksum=off, max_chunks_up=128
[2024/05/02 19:37:58] [ info] [cmetrics] version=0.9.0
[2024/05/02 19:37:58] [ info] [ctraces ] version=0.5.1
[2024/05/02 19:37:58] [ info] [input:dummy:dummy.0] initializing
[2024/05/02 19:37:58] [ info] [input:dummy:dummy.0] storage_strategy='memory' (memory only)
[2024/05/02 19:37:58] [debug] [dummy:dummy.0] created event channels: read=21 write=22
[2024/05/02 19:37:58] [trace] [input chunk] update output instances with new chunk size diff=43, records=1, input=dummy.0
[2024/05/02 19:37:58] [debug] [forward:forward.0] created event channels: read=23 write=24
[2024/05/02 19:37:58] [ info] [sp] stream processor started
[2024/05/02 19:37:58] [ info] [output:forward:forward.0] worker #0 started
[2024/05/02 19:37:58] [ info] [output:forward:forward.0] worker #1 started
[2024/05/02 19:37:58] [trace] [task 0x75344d80] created (id=0)
[2024/05/02 19:37:58] [debug] [task] created task=0x75344d80 id=0 OK
[2024/05/02 19:37:58] [debug] [output:forward:forward.0] task_id=0 assigned to thread #0
[2024/05/02 19:37:58] [trace] [input chunk] update output instances with new chunk size diff=43, records=1, input=dummy.0
[2024/05/02 19:37:58] [debug] [output:forward:forward.0] request 43 bytes to flush
[2024/05/02 19:37:58] [trace] [upstream] get new connection for xxx.xxx.xxx.xxxx:242244, net setup:
net.connect_timeout        = 10 seconds
net.source_address         = any
net.keepalive              = enabled
net.keepalive_idle_timeout = 30 seconds
net.max_worker_connections = 0
[2024/05/02 19:37:58] [trace] [net] connection #49 in process to xxx.xxx.xxx.xxxx:242244
[2024/05/02 19:37:58] [trace] [engine] resuming coroutine=0x7524b000
[2024/05/02 19:37:58] [engine] caught signal (SIGSEGV)

Expected behavior
I expected run like amd64 arch.

Your Environment

  • Version used: v3.0.3 (client && server)
  • Operating System and version:
  • Client: Raspberry Pi 2 Model B ARMv7 - Debian Bullseye 11.9
  • Server: VPS - Ubuntu Server 24.04 AMD64
@patrick-stephens
Copy link
Contributor

I wonder if this is related to #8785?

@pcasaspere
Copy link
Author

I have done more testing. I'm not sure if it's the same problem.

This crash only happens when I use TLS or "Shared_Key" on the FORWARD protocol in my output configuration. If I don't use this settings FORWARD work fine.

@github-actions GitHub Actions
Copy link
Contributor
github-actions bot commented Aug 3, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Aug 3, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2024
@iamfil
Copy link
iamfil commented May 12, 2025

I ran into this issue recently due to not paying attention and installing the version from Bullseye repository on my Raspberry Pi 2 Model B running Raspbian 12 (Bookworm).

Changed deb https://packages.fluentbit.io/raspbian/bullseye bullseye main to deb https://packages.fluentbit.io/raspbian/bookworm bookworm main and installed the correct version. Works perfectly now!

@patrick-stephens
Copy link
Contributor

@iamfil did you just submit a docs PR for this too? Kudos! 👏

@iamfil
Copy link
iamfil commented May 12, 2025

@patrick-stephens yes sir. Hope that saves someone from repeating the same mistake!

@iamfil iamfil mentioned this issue May 12, 2025
Merged
@github-actions github-actions bot removed the Stale label May 13, 2025
@leonardo-albertovich
Copy link
Collaborator

Should this be closed as resolved then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: waiting-for-triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@leonardo-albertovich @iamfil @patrick-stephens @pcasaspere
0