Skip to content

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

@davmillar

Description

@davmillar

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions