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

etcd client set log #230

Open
jicanghaixb opened this issue Nov 7, 2022 · 2 comments
Open

etcd client set log #230

jicanghaixb opened this issue Nov 7, 2022 · 2 comments

Comments

@jicanghaixb
Copy link

etcd client can't config log, which causes log output by the etcd client to be on the stderr,This may cause sigpipe problems when cooperating with systemd. Whether the function of log can be configured?

@zalegrala
Copy link
Contributor

Do you have an example log from the etcd client, or an error that was produced by trying to configure the etcd logging?

@jicanghaixb
Copy link
Author

If there is an error during the running of the etcd client, etcd client will output log . By default, the log will be output to stderr. If the program is managed by systemd, the information about stderr and stdout will be captured by systemd-journald. If systemd-journald restarts, etcd client write log at this time, it will get a boken pipe error. In Golang, a SIGPIPE signal will be generated for this situation, which will cause the program killed by SIGPIPE

charleskorn pushed a commit that referenced this issue Aug 3, 2023
Replace node_exporter https package with exporter-toolkit
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

2 participants