-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fluentd gives no error on empty cert file during startup #3085
Comments
Tested to have key file empty, and fluentd was able to detect during booting up, and exit with failure. |
So |
Signed-off-by: Masahiro Nakagawa <[email protected]>
Patch: #3086 |
That's correct.
At this time, fluentd just runs, without really working. |
Raise an error for broken certificate file. fix #3085
Just tried the patch. It does fix the empty cert file, or wrong formatted cert file, but it didn't fix what I mentioned in my last comment:
|
Could you write how to validate such cert at startup phase? |
openssl provides way to check if cert file and key file match: https://www.ssl247.com/kb/ssl-certificates/troubleshooting/certificate-matches-private-key |
Describe the bug
I have below TLS listener which works fine.
Recently clients can no longer connect. It turned out the /opt/tls/tls.crt on the server got an empty file. fluentd came up with no errors, but of course won't accept any TLS connections with empty cert file. I would expect fluentd should fail to start, and give errors about the empty cert file tls.crt.
To Reproduce
See above in description
Expected behavior
fluentd should fail during starting up, instead of starting up but fail to work.
Your Environment
fluentd --version
ortd-agent --version
cat /etc/os-release
uname -r
If you hit the problem with older fluentd version, try latest version first.
Your Configuration
See above in description
Your Error Log
No errors during starting up.
Additional context
The text was updated successfully, but these errors were encountered: