Bug 255593 - sysutils/fluent-bit: doesn't start
Summary: sysutils/fluent-bit: doesn't start
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Palle Girgensohn
Depends on:
Reported: 2021-05-04 13:02 UTC by Christopher Beppler
Modified: 2021-07-16 06:31 UTC (History)
3 users (show)

See Also:

updated fluent_bit rc file (1.16 KB, application/x-shellscript)
2021-05-04 13:02 UTC, Christopher Beppler
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Beppler 2021-05-04 13:02:32 UTC
Created attachment 224660 [details]
updated fluent_bit rc file

I have the issue that fluent-bit doesn't start anymore when using the sample config. It might be related to an upstream change, though.

However, if I change /usr/local/etc/rc.d/fluent_bit to the attached file it works.

Hope that helps,
Comment 1 bgdnlp 2021-07-16 06:31:19 UTC
I'll add some detail here, not sure if it's the same issue but seems to be.

Fluent-bit 1.7.9, installed from packages, doesn't start in daemon mode. Simple way to reproduce:

# fluent-bit -d -s 40000 -i random -o stdout
Fluent Bit v1.7.9
* Copyright (C) 2019-2021 The Fluent Bit Authors
* Copyright (C) 2015-2018 Treasure Data
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

[2021/07/16 06:28:08] [ info] switching to background mode (PID=59754)

Checking if the process exists will show that it doesn't. Truss produces this (shortened) output:

# truss fluent-bit -d -s 40000 -i random -o stdout
write(2,"* Fluent Bit is a CNCF sub-proje"...,65) = 65 (0x41)
* https://fluentbit.io

write(2,"* https://fluentbit.io\n\n",24)         = 24 (0x18)
fork()                                          [2021/07/16 06:27:47] [ info] switching to background mode (PID=59732)
 = 59732 (0xe954)
sigprocmask(SIG_SETMASK,{ },0x0)                 = 0 (0x0)
process exit, rval = 0

I'm guessing this should be reported upstream?