tickets #164706
closedKarma "proxyconnect tcp: dial tcp connect: connection refused"
0%
Description
Karma always worked fine, and I often had it open in the background, always returning to it showing the latest data.
Now however it seems after about one refresh cycle on the page, it fails with the aforementioned message.
The log is not much more helpful either:
Jul 30 12:55:16 monitor karma[28610]: level=error msg="Collection failed" error="Get \"https://alertmanager.infra.opensuse.org/api/v2/status\": proxyconnect tcp: dial tcp :0: connect: connection refused" alertmanager=local try=1/2
Jul 30 12:55:16 monitor karma[28610]: level=info msg="GET request" timeout=10 uri=https://alertmanager.infra.opensuse.org/metrics
Jul 30 12:55:16 monitor karma[28610]: level=error msg="Request failed" error="Get \"https://alertmanager.infra.opensuse.org/metrics\": proxyconnect tcp: dial tcp :0: connect: connection refused" alertmanager=local uri=https://alertmanager.infra.opensuse.org
Jul 30 12:55:16 monitor karma[28610]: level=error msg="Collection failed" error="Get \"https://alertmanager.infra.opensuse.org/api/v2/status\": proxyconnect tcp: dial tcp :0: connect: connection refused" alertmanager=local try=2/2
Jul 30 12:55:16 monitor karma[28610]: level=info msg="Collection completed"
Note originally this would say uri=http://ipv6-localhost:9093
, it now shows the httpd served URL for testing without proxy mode (see below).
There is no corresponding error on the Alertmanager side.
Running while true ; do curl https://alertmanager.infra.opensuse.org/api/v2/status ; echo ok ; done
as a very rudimentary load test does not show any stalls either.
Curl from the Karma user works as well.
No relevant AVC messages can be found.
No hardening options in the service unit should impact network connectivity.
I also tried disabling the proxy mode (which tunnels Alertmanager requests through Karma):
# /etc/karma/config.yaml
#proxy: true
proxy: false
#uri: http://ipv6-localhost:9093
uri: https://alertmanager.infra.opensuse.org
This did not help either, and is rather surprising, as I thought the "proxyconnect" was a result of using the proxy mode.