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

Unable to use syslog as input pipeline, not starting #5153

Closed
whysi opened this issue Mar 22, 2022 · 6 comments
Closed

Unable to use syslog as input pipeline, not starting #5153

whysi opened this issue Mar 22, 2022 · 6 comments

Comments

@whysi
Copy link

whysi commented Mar 22, 2022

Bug Report

Unable to use syslog as input pipeline, not starting

I'm trying to start fluent-bit with the syslog input using various type of installations under Windows. All of them are failing with:
[error] [config] section 'syslog' tried to instance a plugin name that don't exists

To Reproduce

  • Clean installation of Fluent-Bit on Windows (x64), tested with version 1.9.0-win64 and 1.8.13-win64 or just use the .zip archive
  • Start a simple execution with syslog as input and stdout as output, via command line (fluent-bit.exe -i syslog -o stdout -R parsers.conf) or with a simple config file, like this:
[SERVICE]
   Flush         1
   Log_Level     trace
   Daemon        Off
   Parsers_File  parsers.conf
   HTTP_Server   Off
   HTTP_Listen   0.0.0.0
   HTTP_Port     2020

[INPUT]
   Name              syslog
   Parser            syslog-rfc3164
   Mode              tcp
   Listen            0.0.0.0
   Port              24225
   Buffer_Chunk_Size 32KB
   Buffer_Max_Size   64KB

[OUTPUT]
   Name             stdout
   Match            *

The parsers file is the default one shipped with the installation/archive.

Expected behavior

Application starting as expected with syslog input using the given parsers.

Screenshots

image

Error log result:
[2022/03/22 14:56:00] [error] [config] section 'syslog' tried to instance a plugin name that don't exists [2022/03/22 14:56:00] [error] configuration file contains errors, aborting.

Your Environment

  • Version used: 1.9.0-win64 and 1.8.13-win64
  • Configuration:
[SERVICE]
    Flush         1
    Log_Level     trace
    Daemon        Off
    Parsers_File  parsers.conf
    HTTP_Server   Off
    HTTP_Listen   0.0.0.0
    HTTP_Port     2020

[INPUT]
    Name              syslog
    Parser            syslog-rfc3164
    Mode              tcp
    Listen            0.0.0.0
    Port              24225
    Buffer_Chunk_Size 32KB
    Buffer_Max_Size   64KB

[OUTPUT]
    Name             stdout
    Match            *
  • Environment: Windows 10, Windows Server 2022 core, Windows Server 2022 nano docker image
@whysi whysi changed the title Unable to use syslog as input pipeline not starting Unable to use syslog as input pipeline, not starting Mar 22, 2022
@nokute78
Copy link
Collaborator

According to build configuration , fluent-bit doesn't contain in_syslog on Windows system.
https://github.com/fluent/fluent-bit/blob/v1.9.0/cmake/windows-setup.cmake#L30

@whysi
Copy link
Author

whysi commented Apr 20, 2022

According to build configuration , fluent-bit doesn't contain in_syslog on Windows system. https://github.com/fluent/fluent-bit/blob/v1.9.0/cmake/windows-setup.cmake#L30

I've missed that, thank you very much for your help!

@whysi whysi closed this as completed Apr 20, 2022
@sean-scott-lr
Copy link

Not sure why this was closed. Why doesnt in_syslog work on windows? Is it an oversight, or purposeful?

@tirelibirefe
Copy link

the same problem exist also for exec plugin.

[error] [config] section 'exec' tried to instance a plugin name that don't exists

@leonardo-albertovich
Copy link
Collaborator

leonardo-albertovich commented May 12, 2023

@tirelibirefe : Could you please create a new issue with a proper report of your issue so we can give you a meaningful answer?

Edit: Disregard this, I just understood what you meant. I don't know why in_exec isn't enabled in windows and I haven't tried to build fluent-bit with it enabled either but an improvement request issue would be welcome, that way we can track the issue and measure its progress once it's internally assigned and ensure it doesn't keep slipping through the cracks.

@leonardo-albertovich
Copy link
Collaborator

@sean-scott-lr : in_syslog wasn't enabled in windows because it optionally uses a unix socket to receive data and not making just that feature platform dependent was an oversight. We have already made the necessary changes to enable its usage in windows and it will be included in the next release of fluent-bit 2.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants