-
-
Notifications
You must be signed in to change notification settings - Fork 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
An error has occurred while serving routing_http_client metrics #9891
Comments
I was unable to reproduce this with vanilla Docker image for 0.20.0,
Will try to poke more, want to confirm if this is or is not something that impacts ipfs.io bifrost-infra. |
bifrost-infra box running 0.20 did not experience this, which was a good sign. I've focused on the differences in config, and the problem only occurs if RPC API is exposed on more than one port. TLDR:
|
Hello, We are getting this error on our two nodes as well (running Kubo 0.24.0), but we don't have multiple listener setup:
When I restart kubo, there is a few seconds during which the metrics are printed, and then this error shows up. Anything I can provide to help debug this? |
Same situation with Kubo 0.25 (I did not yet tried 0.26 since I'm waiting for it to be released in the unstable branch of NixOS). |
This can be reproduced in v0.29.0 by: ipfs init
edit ~/.ipfs/config "Addresses": {
"API": ["/ip4/127.0.0.1/tcp/5001", "/ip6/::1/tcp/5001"], ipfs daemon
echo hello | ipfs add
open http://127.0.0.1:5001/debug/metrics/prometheus |
When there are multiple listeners configured for Addresses.API, serving metrics results in an errors: "<metric> was collected before with the same name and label values". This PR fixes this by maintaining a global map of metrics handlers, and only creating and reginstering them once. The same metrics handlers are provided to the mux for every listener. Fixes #9891 Fixes #9397 Unblocks #9637
Version
Config
Description
http://127.0.0.1:5001/debug/metrics/prometheus ends up in broken state after a multiple days of uptime:
Seems we have a bug in
boxo/routing/http/client
, needs analysis.The text was updated successfully, but these errors were encountered: