Closed czunker closed 6 years ago
Thanks for reporting. Actually this bug might happen, if multiple HTTP requests hit at the same time. I will restructure the code to use different data structure instances for each request.
But for now your service just restarts and doesn't impact your monitoring, right?
Yes. I just added:
Restart=on-failure
RestartSec=1
to the systemd unit file and it works.
I released v0.1.2.1, which should resolve the issue. Can you verify that the issue is resolved?
I installed the new version. I will let you know whether it crashed or not.
The ipsec_exporter didn't crash since friday. Before the new release it was alive for just some hours, so assume you fixed it.
Thanks for the new release.
Thanks for validating the release!
From time to time ipsec_exporter crashed with this stacktrace:
I don't know go. But as the word
concurrent
highlights multiple times, perhaps it has something to do with our setup. We are monitoring multiple VPN connections on the same server with ipsec_exporter. Perhaps that's the cause?