Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPIPE - Unexpected error condition 32/Linux, please report this as a bug #176

Open
davmillar opened this issue Oct 16, 2024 · 0 comments
Open

Comments

@davmillar
Copy link

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.

  1. Should the __try_read_sock sub return 0 in this case, or retry like it does with EINTR?
  2. Is there further error handling required outside of the __try_read_sock sub when this happens?
  3. 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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant