A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes
-
Updated
Mar 2, 2022 - Python
And go vet doesn't like it
Error: ./protocol_test.go:29:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:37:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:40:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:88:4: call to (*T).Fatalf from a non-test goroutine
Error: ./protocol_test.go:99:4: call to (*T).Fa
Add a description, image, and links to the haproxy topic page so that developers can more easily learn about it.
To associate your repository with the haproxy topic, visit your repo's landing page and select "manage topics."
Detailed Description of the Problem
Hello
I wrote some script for disabled/enable frontend when related backend status goes
DOWNORUP.BUT stat shows the frontend status is still
OPENeven if I was disabled it.echo "show stat" | sudo socat unix-connect:/run/haproxy-master.sock stdioand follow is my tested HAproxy version