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

Error Starting Fluentd #74

Open
wooxudong opened this issue Sep 23, 2021 · 5 comments
Open

Error Starting Fluentd #74

wooxudong opened this issue Sep 23, 2021 · 5 comments

Comments

@wooxudong
Copy link

wooxudong commented Sep 23, 2021

Problem

The fluend container would not be able to start with following errors
Screenshot 2021-09-22 at 5 43 01 PM
...

Steps to replicate

FROM bitnami/fluentd:1.14.0

RUN fluent-gem install 'fluent-plugin-aws-elasticsearch-service' -v 2.4.1

Expected Behavior or What you need to ask

Fluentd to start correctly
...

Using Fluentd and ES plugin versions

Fluentd: v1.14.0 fluent-plugin-aws-elasticsearch-service: v 2.4.1

@pavel-trubitsyn
Copy link

Hi, I have the same issue with fluent/fluentd:v1.14.1.

@pavel-trubitsyn
Copy link

@wooxudong
Copy link
Author

wooxudong commented Oct 4, 2021

@pavel-trubitsyn , thanks for the solution.

I think it shall be a proper fix for this plugin to solve the dependency chain ?

@wooxudong
Copy link
Author

Any updates on this ?

@DaemonDude23
Copy link

DaemonDude23 commented Feb 25, 2022

I've been watching this problem overall for the last year. Today I got it working after learning about an OpenSearch-specific plugin from the Fluentd maintainers.

I had previously built a container with plugins from this repo to push logs to AWS's OpenSearch, but when trying to update it, ran into these dependency conflicts.
I upgraded from: fluent/fluentd:v1.13.3-debian-1.0 to fluent/fluentd:v1.14.5-debian-1.0. The Dockerfile I kept the same, other than removing any elasticsearch plugins and replacing it with: fluent-plugin-opensearch:1.0.1 (https://github.com/fluent/fluent-plugin-opensearch).

Then I modified the config to change the output @type aws-elasticsearch-service to opensearch. I removed 2 parameters that are not supported by this plugin (log_es_400_reason and suppress_type_name) and it's working just fine.
I see there are many issues in this repo that relate to this problem. Hopefully this will help someone resolve it.
EDIT: There's a bug with the Opensearch plugin: fluent/fluent-plugin-opensearch#24

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

3 participants