Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upfederation is failing with `http: multiple response.WriteHeader calls` error #2237
Comments
This comment has been minimized.
This comment has been minimized.
|
Apparently, I was missing
|
onorua
closed this
Dec 1, 2016
This comment has been minimized.
This comment has been minimized.
|
There's still a bug in here, what you provided as the config should work and that error message is bad. |
brian-brazil
reopened this
Dec 1, 2016
brian-brazil
added
the
kind/bug
label
Dec 1, 2016
This comment has been minimized.
This comment has been minimized.
|
Yep, confirming that it was just coincidence that errors disappeared with adding that line. I still see this:
as you can see, it doesn't happen often, but still... Do you need me to check something for you, or you know what is this and how to fix it? |
This comment has been minimized.
This comment has been minimized.
|
I don't think any of us has had a chance to reproduce yet. We'll let you know if we need further information. |
This comment has been minimized.
This comment has been minimized.
|
I haven't seen |
This comment has been minimized.
This comment has been minimized.
|
do you want me to do anything to help debugging it? |
This comment has been minimized.
This comment has been minimized.
|
Can you tell us what's hitting this Prometheus (e.g. Grafana), and if that's the full config file? |
This comment has been minimized.
This comment has been minimized.
natalia-k
commented
Dec 6, 2016
•
|
Hi, on federation prometheus server just have in targets status : "context deadline exceeded", nothing in log from 3 prometheus defined in federation, only one has this error. Deleting the problematic prometheus pod, temparary fixed the problem, but it back some time after that |
This comment has been minimized.
This comment has been minimized.
|
Federation server is hitting that prometheus server, we basically have the same problem as @natalia-k reported. Federation did not work, reporting showed that the node is "down" on targets tab, with "context deadline exceeded" in logs. |
This comment has been minimized.
This comment has been minimized.
|
Ah, so it is the scraped server – I thought it was the scraping one. Thanks. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
widgetpl
commented
Jan 19, 2017
|
isn't it connected whit too many metrics on federation endpoint and too low timout to collect them all ?
or
and in prometheus
with wget i get
|
This comment has been minimized.
This comment has been minimized.
|
That appears to be a different issue. The issue as reported as resolved. If there's another bug that was being hidden by this one, a new issue should be opened. |
brian-brazil
closed this
Apr 6, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
onorua commentedDec 1, 2016
What did you do?
Tried to increase amount of nodes for our prometheus more than 300 and decided to use federation
What did you expect to see?
Seamless and working solution
What did you see instead? Under which circumstances?
Some broken graphs, nothing is actually working
Environment
System information:
Linux prometheus-sfo2-prod-02 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/LinuxPrometheus version:
on federation server everything seems to be fine:
on federated server (the one which scrapes everything):