You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Received the error "Unexpected error condition 32/Linux, please report this as a bug" in our logs. The error code comes back to EPIPE.
I'm not familiar enough with error codes to understand the impact to the module.
Should the __try_read_sock sub return 0 in this case, or retry like it does with EINTR?
Is there further error handling required outside of the __try_read_sock sub when this happens?
How would I go about debugging why the pipe was broken -- is there something in the host OS that would log info about this, or should I inspect the Redis server logs and network traffic?
The text was updated successfully, but these errors were encountered:
Received the error "Unexpected error condition 32/Linux, please report this as a bug" in our logs. The error code comes back to EPIPE.
I'm not familiar enough with error codes to understand the impact to the module.
__try_read_sock
sub return 0 in this case, or retry like it does withEINTR
?__try_read_sock
sub when this happens?The text was updated successfully, but these errors were encountered: