-
Notifications
You must be signed in to change notification settings - Fork 460
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 in the fluentd pod #540
Comments
Could you please provide configuration parameters? |
@dioguerra : Thanks for your reply. I am using argocd manifest for the deployment and this is what i am passing from argocd manifest (check from the helm: part) . So it takes the overridden value (i can see in the livemanifest and logs) and it targets the right elastic host (with overridden value) but when the daemonset pods tries to put the log into elastic it falls into the original error message for which i created this issue. targetRevision: {{ index .Values "fluentd" "targetRevision" }} |
@dioguerra : I have provided the configuration parameters above, any suggestions? as I can understood from the issue it doesn't like @type elasticsearch but i think when I am trying to override i have to provide the whole config set from my manifest. |
Helllo,
I have a fluend daemonset deployment with your chart but i am getting this warning message in the pod and this causes a crash, could you please check what could be it? Any help is highly appreciated
ailed to flush the buffer. retry_times=0 next_retry_time=2024-08-07 23:12:16 +0000 chunk="61f20090e1c9331f4ac0a93f878658be" error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error="could not push logs to Elasticsearch cluster ({:host=>"xxxx.fluentd.svc.cluster.local", :port=>9200, :scheme=>"http", :user=>"xxxxx", :password=>"obfuscated", :path=>""}): [400] {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"}],"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"},"status":400}"
The text was updated successfully, but these errors were encountered: