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

Error with -consulcatalog and missing load balance method on 1.0.0 #524

Closed
crumley opened this issue Jul 13, 2016 · 4 comments
Closed

Error with -consulcatalog and missing load balance method on 1.0.0 #524

crumley opened this issue Jul 13, 2016 · 4 comments
Labels
Milestone

Comments

@crumley
Copy link

crumley commented Jul 13, 2016

Running the docker image with tag v1.0.0 against a consul catalog results in the following message being sent to the console for every service in consul repeatedly:

time="2016-07-13T03:06:13Z" level=warning msg="Error loading load balancer method '<nil>' for backend backend-service-name: Invalid method, using default. Using default wrr."

Downgrading to v1.0.0-rc3 fixes the issue.

@errm
Copy link
Contributor

errm commented Jul 13, 2016

Looking at the change that caused this to occur it looks to me like we have started logging this message when the load balancer method is not specified and we fall back to the default.

So I don't think anything harmful is happening here apart from excessive logs. Perhaps this should really be info rather than warn, wdyt @emilevauge?

@emilevauge
Copy link
Member

Indeed, there is no issue here, normal behavior.
But we could move this log to INFO to avoid futur misunderstandings.

@emilevauge emilevauge added this to the 1.1 milestone Jul 13, 2016
@emilevauge emilevauge added the kind/enhancement a new or improved feature. label Jul 13, 2016
@keis
Copy link

keis commented Jul 13, 2016

IMHO that's still a bit noisy unless it's expected of the backends to always provide this field and in that case I guess the default template for consul_catalog should be updated.

@crumley
Copy link
Author

crumley commented Jul 13, 2016

The verbosity is killer when you have a lot of services and multiple traefik instances especially when it is quite common for the default to be used in most cases.

@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants