Proxy does not recover after "Stopping listening" #888
Description
What happened:
There was a temporary Consul downtime in my cluster. After Stopping listening, the stolon-proxy does not recover:
2022-09-11T22:34:54.630Z INFO cmd/proxy.go:304 check timeout timer
2022-09-11T22:34:54.630Z INFO cmd/proxy.go:158 Stopping listening
No more output for multiple hours, even though Consul evidently recovered (Consul checks on the same machine succeeded).
What you expected to happen:
That after Stopping listening it eventually starts listening again, as written on #76 it says:
It will restart listening on successful etcd communication and a populated proxyConf.
How to reproduce it (as minimally and precisely as possible):
Not sure yet, I observed it after a temporary network hickup that temporarily made Consul connections fail.
Anything else we need to know?:
Environment:
- Stolon version:
0.16.0 - Stolon running environment (if useful to understand the bug): NixOS Linux