You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-02-22 22:52:52 +0000 [warn]: #0 Could not communicate to OpenSearch, resetting connection and trying again. SSL_read: unexpected eof while reading (OpenSSL::SSL::SSLError)
sometime it solves itself after a some retries, but sometime it gets stuck (on startup for long periods , I never waited for more that 10 minutes though).
If I sudo systemctl stop fluentd.service , fluentd will receive the graceful shutdown but it will take a long time to actually shutdown. It seems to be like it can't shutdown while a "retry is pending".
After the shutdown, if I restart it again then the SSL_read problem will disappear, which suggest to me that the problem is not on the AWS OpenSearch side,
Expected Behavior or What you need to ask
I would expect to succeed, or provide a better description of what is going on .
...
Using Fluentd and OpenSearch plugin versions
OS version: Ubuntu 22.04 LTS
Bare Metal or within Docker or Kubernetes or others?
(check apply)
Steps to replicate
WIth the following
/etc/fluent/fluentd.conf
I get on startup the following error
sometime it solves itself after a some retries, but sometime it gets stuck (on startup for long periods , I never waited for more that 10 minutes though).
If I
sudo systemctl stop fluentd.service
, fluentd will receive the graceful shutdown but it will take a long time to actually shutdown. It seems to be like it can't shutdown while a "retry is pending".After the shutdown, if I restart it again then the SSL_read problem will disappear, which suggest to me that the problem is not on the AWS OpenSearch side,
Expected Behavior or What you need to ask
I would expect to succeed, or provide a better description of what is going on .
...
Using Fluentd and OpenSearch plugin versions
fluent-package 5.0.2 fluentd 1.16.3 (d3cf2e0f95a0ad88b9897197db6c5152310f114f)
The text was updated successfully, but these errors were encountered: