crashes after start: panic: runtime error: invalid memory address or nil pointer dereference

[path-network]

crashes after start: panic: runtime error: invalid memory address or nil pointer dereference

[kzemek]

Commit cd9f1fb might fix the issue - it ensures that source address variable is not dereferenced for logging if it's nil. Note that the only case the source address might be nil is when go-mmproxy received a connection with PROXY UNKNOWN header.

[kzemek]

I agree about the need for a new release. We'll be doing that soon :)

[kzemek]

Are you using go-mmproxy downloaded from the releases page, or built from source? If built from source, what version of Go are you using, and what's the Zap library version you built the executable with (e.g. git -C ~/go/src/go.uber.org/zap rev-parse --short HEAD)?

[onlyjob]

Built from source with Golang 1.13 and 1.14 (no difference). Initially I built "go-mmproxy" with "zap" v1.9.1 (from Debian package) but upgrading it to v1.14.1 did not help.

[kzemek]

Can you give me some more detail about your environment? What version of Debian are you running and is it fully updated? This might help me reproduce the issue.

Also, can you please paste the output when the panic happens while go-mmproxy is started with -v 2 argument?

[onlyjob]

Commit cd9f1fb fixed the problem! Thank you.

Maybe this problem happened due to haproxy upgrade from 1.x to v2.0?
Also I'm forwarding connection with send-proxy-v2...

IMHO this (and other) commits since 1.0 warrant a new release.

FYI go-mmproxy is in Debian :)

My environment is Debain 10 "Buster". Do you still want panic output with -v 2?