Massive amounts of log spam

[craig]

On the attacking side, I'm doing:

oha -z 60sec -c 1000 -q 1000000 --latency-correction http://192.168.0.40:8080

(https://github.com/hatoo/oha)

Immediately, the go process spits out massive amounts of errors:

root@host:~/berghain# go run ./cmd/spop/. -config cmd/spop/config.yaml
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:55 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:56 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:56 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:47:56 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:48:04 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:48:04 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer
2024/02/24 21:48:04 scheduler.go:96: write unix ./spop.sock->@: use of closed network connection
2024/02/24 21:48:04 scheduler.go:96: write unix ./spop.sock->@: use of closed network connection
2024/02/24 21:48:04 agent.go:54: reading frame length: read unix ./spop.sock->@: read: connection reset by peer

IMHO if it's an error (our maybe just debug output?) it should be printed out, but otherwise pollutes logs.