Read responded with an error code that is not handled by Jedis

redis.clients.jedis.exceptions.JedisDataException
at redis.clients.jedis.Protocol.processError
at redis.clients.jedis.Protocol.process
at redis.clients.jedis.Protocol.read

Typical Exception Messages

  1. NOAUTH Authentication required.
  2. ERR Protocol error: invalid bulk length
  3. ERR Unsupported CONFIG parameter: notify-keyspace-events
  4. WRONGTYPE Operation against a key holding the wrong kind of value
  5. ERR Client sent AUTH, but no password is set
  6. ERR EXEC without MULTI
  7. ERR operation not permitted
  8. ERR unknown command 'CONFIG'
  9. ERR wrong number of arguments for 'hmset' command
  10. LOADING Redis is loading the dataset in memory

Origin

Specific cases

We have seen this error pattern in the following webpages (102)

  1. dpfundtvia GitHub1 week ago
    Unsupported operation 'info'
  2. gvasquezvia Stack Overflow2 months ago
    ERR unknown command 'SAVE'
  3. piaohaovia GitHub3 months ago
    ERR handle request, command 'CONFIG' is not allowed
  4. hkun0120via GitHub3 months ago
    ERR Syntax error, try CLIENT (LIST | KILL ip:port)
  5. mevivsvia GitHub3 months ago
    ERR DISCARD without MULTI
  6. v11via Stack Overflow3 months ago
    OOM command not allowed when used memory > 'maxmemory'.
  7. cssparkvia GitHub3 months ago
    ERR Unknown node 9168cd159e927816698db9effbe7f04c07fcc073
  8. mayongzevia GitHub4 months ago
    ERR unknown command 'AUTH'
  9. OhWordsvia Stack Overflow7 months ago
    ERR min or max not valid string range item
  10. huangkunquavia GitHub8 months ago
    ERR handle response, backend conn reset