Skip to content

Log forwarding: incorrect fluent-bit path "Fluent Bit exe not found." #2032

@rcwsr

Description

@rcwsr

VM running Rocky 9.5 was updated, new relic infrastructure agent also updated but stopped forwarding logs to NR.

I've actually resolved the issue by explicitly setting fluent_bit_exe_path, see below.

Description

Describe the problem you're encountering.
TIP: Do NOT share sensitive information, whether personal, proprietary, or otherwise!

VM running Rocky 9 was updated, new relic infrastructure agent also updated but stopped forwarding logs to NR.

Debug logs showed fluent bit executable not found at /opt/fluent-bit/bin/fluent-bit, but docs say default value is /opt/td-agent-bit/bin/td-agent-bit. Neither of these paths exist.

time="2025-04-09T10:44:27+01:00" level=debug msg="Fluent Bit exe not found." component=integrations.Supervisor fbExePath=/opt/fluent-bit/bin/fluent-bit process=log-forwarder
time="2025-04-09T10:44:27+01:00" level=debug msg="Log forwarder is not available for this platform. The agent will start without log forwarding support." component=AgentService service=newrelic-infra

td-agent-bit does not appear to be installed

fluent-bit does however exist:

$ fluent-bit --version
Fluent Bit v3.2.8
Git commit: 
which fluent-bit 
/bin/fluent-bit

changed log config to set (it was not set previously) fluent_bit_exe_path: "/bin/fluent-bit" and restarted the service - logs now appear.

Expected Behavior

Logs forwarded using bundled fluent-bit

Troubleshooting or NR Diag results

Provide any other relevant log data.
TIP: Scrub logs and diagnostic information for sensitive information

time="2025-04-09T10:44:27+01:00" level=debug msg="Fluent Bit exe not found." component=integrations.Supervisor fbExePath=/opt/fluent-bit/bin/fluent-bit process=log-forwarder
time="2025-04-09T10:44:27+01:00" level=debug msg="Log forwarder is not available for this platform. The agent will start without log forwarding support." component=AgentService service=newrelic-infra

Steps to Reproduce

Please be as specific as possible.
TIP: Link a sample application that demonstrates the issue.

Not entirely sure how to reproduce, all I know is that our system did a package update, probably upgrading an outdated version of newrelic infra agent.

Your Environment

ec2 instance running:
Rocky 9.5 - dnf update ran
newrelic infra agent: 1.63.1
fluent-bit: 3.2.8

Additional context

aslog.Debug("Log forwarder is not available for this platform. The agent will start without log forwarding support.")

func (c *fBSupervisorConfig) IsLogForwarderAvailable() bool {

https://docs.newrelic.com/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/

For Maintainers Only or Hero Triaging this bug

Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions