500 Response on varnish reload

[mbiencinto]

• Varnish varnish-6.2.1 revision 9f8588e4ab785244e06c3446fe09bf9db5dd8753
• prometheus_varnish_exporter v1.6 (0855dcb)

---

I encontered a issue when i reload varnish, the output of metrics is a 500 Status code with this message:

http://myvarnishhost:9131/metrics

An error has occurred while serving metrics:

210 error(s) occurred:
* collected metric "varnish_backend_beresp_bodybytes" { label:<name:"backend" value:"es" > label:<name:"server" value:"unknown" > counter:<value:0 > } was collected before with the same name and label values
* collected metric "varnish_backend_pipe_in" { label:<name:"backend" value:"tod" > label:<name:"server" value:"unknown" > counter:<value:0 > } was collected before with the same 
....

• If i restart the exporter, i get the same response.
• If i wait 5~10 minutes sometimes the response is 200 with a normal metrics
• if i restart varnishd the metrics works fine

In the production environment is not possible restart varnish becaus we lost all cached data.

I wait for you help. Thanks a lot!

[mbiencinto]

Yes, is the same problem, duplicate metrics. Thanks for your info! Mariano Biencinto ***@***.*** ***@***.***/0?redirect=mailto%3Amariano.biencinto%40hola.com&recipient=cmVwbHkrQVAyV0VRSkxCSzNPNU9ITFdZQ1FVWFY3VTU2VDdFVkJOSEhEV1c2NkdZQHJlcGx5LmdpdGh1Yi5jb20%3D)

…

On nov. 22 2021, at 2:33 pm, Stefan Goethals ***@***.***> wrote: This looks like #57 ***@***.***/1?redirect=https%3A%2F%2Fgithub.com%2Fjonnenauha%2Fprometheus_varnish_exporter%2Fissues%2F57&recipient=cmVwbHkrQVAyV0VRSkxCSzNPNU9ITFdZQ1FVWFY3VTU2VDdFVkJOSEhEV1c2NkdZQHJlcGx5LmdpdGh1Yi5jb20%3D) is still not fixed :-( — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub ***@***.***/2?redirect=https%3A%2F%2Fgithub.com%2Fjonnenauha%2Fprometheus_varnish_exporter%2Fissues%2F74%23issuecomment-975526756&recipient=cmVwbHkrQVAyV0VRSkxCSzNPNU9ITFdZQ1FVWFY3VTU2VDdFVkJOSEhEV1c2NkdZQHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe ***@***.***/3?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP2WEQMKJMWBA4QZZK5TWPTUNJBD7ANCNFSM5D73UWJQ&recipient=cmVwbHkrQVAyV0VRSkxCSzNPNU9ITFdZQ1FVWFY3VTU2VDdFVkJOSEhEV1c2NkdZQHJlcGx5LmdpdGh1Yi5jb20%3D). Triage notifications on the go with GitHub Mobile for iOS ***@***.***/4?redirect=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&recipient=cmVwbHkrQVAyV0VRSkxCSzNPNU9ITFdZQ1FVWFY3VTU2VDdFVkJOSEhEV1c2NkdZQHJlcGx5LmdpdGh1Yi5jb20%3D) or Android ***@***.***/5?redirect=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&recipient=cmVwbHkrQVAyV0VRSkxCSzNPNU9ITFdZQ1FVWFY3VTU2VDdFVkJOSEhEV1c2NkdZQHJlcGx5LmdpdGh1Yi5jb20%3D).

[hashworks]

This has already been fixed in 1.6.1, so I guess this can be closed?