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
Recurrence: The binary was running without any errors since the past 9 months. However, since 9th Jun the error NOAUTH Exception Cache can be observed. Occurrence of this issue is very less. Most of the time this is working fine.
Client SDK: Jedis 2.8.0 and Scala-redis_2.11.
org.redis
scala-redis_2.11
0.0.25
redis.clients
jedis
2.8.0
jar
compile
Investigation:
By checking the server side logs,the NOAUTH issue is “Closing unauthenticated client, either AUTH didn't succeed or AUTH was never sent within the timeout period”, which means AUTH was not sent on some of the connections.
Could you please provide us with any insights about troubleshooting the issue?
Thanks
The text was updated successfully, but these errors were encountered:
The information is very useful. We agree that the intermittent network issue may cause the NOAUTH exception in the client and we already add the try-catch logic in our application.
Hi Team,
Issue Definition: Exceptions throwed by spack jobs: ncom.redis.RedisProtocolParsingException: NOAUTH Exception Cache
Recurrence: The binary was running without any errors since the past 9 months. However, since 9th Jun the error NOAUTH Exception Cache can be observed. Occurrence of this issue is very less. Most of the time this is working fine.
Client SDK: Jedis 2.8.0 and Scala-redis_2.11.
org.redis scala-redis_2.11 0.0.25 redis.clients jedis 2.8.0 jar compileInvestigation:
By checking the server side logs,the NOAUTH issue is “Closing unauthenticated client, either AUTH didn't succeed or AUTH was never sent within the timeout period”, which means AUTH was not sent on some of the connections.
Could you please provide us with any insights about troubleshooting the issue?
Thanks
The text was updated successfully, but these errors were encountered: