Error accepting connection from remote causes panic
B3rs opened this issue · comments
Marco Bersani commented
After an error in listener.Accept()
remote
object can be nil.
Line 122 in d3db570
Calling
remote.Close()
in this line causes a panic.Line 125 in d3db570
We noticed this behaviour because this error Error accepting connection from remote: accept tcp [::]:11211: accept4: too many open files
causes our implementation to panic.
Since the wanted behavior is to continue the listener.Accept()
loop in case of error, we should wrap this particular remote.Close()
call with an if remote != nil
statement