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

change server listen error log to info #145

Merged
merged 2 commits into from
Jun 17, 2021
Merged

Conversation

willarmiros
Copy link
Contributor

Issue #, if available:
#144

Description of changes:
Changes the log-level and wording of the error message when the proxy server stops listening. I also audited other log messages added in #138 but the rest appear to be legitimate errors that should still be logged as such.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Copy link
Contributor

@anuraaga anuraaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If err isn't nil isn't it actually an error? E.g., port already in use

@@ -133,7 +133,7 @@ func (s *Server) Serve() {
log.Infof("Starting proxy http server on %s", s.Addr)
err := s.ListenAndServe()
if err != nil {
log.Errorf("unable to start the server: %v", err)
log.Infof("proxy http server has stopped listening: %v", err)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great catch, updated

@willarmiros willarmiros merged commit 77aa084 into master Jun 17, 2021
@willarmiros willarmiros deleted the willarmiros-patch-1-1 branch June 17, 2021 17:52
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

Successfully merging this pull request may close these issues.

aws-xray-daemon:3.3.2 starts logging Error level message while stopping x-ray daemon container
2 participants