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

Exceptions throwed by spack jobs: NOAUTH Exception Cache #239

Open
LucyWengCSS opened this issue Jul 6, 2019 · 2 comments
Open

Exceptions throwed by spack jobs: NOAUTH Exception Cache #239

LucyWengCSS opened this issue Jul 6, 2019 · 2 comments

Comments

@LucyWengCSS
Copy link

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 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

@debasishg
Copy link
Owner

Looks like you are running both Jedis and scala-redis - I am not sure if the issue has something to do with this.

Regarding

AUTH was never sent within the timeout period

can there be any network issues that caused the timeout ?

I am just guessing as this looks like a local environment specific issue as it has been running for 9 months without any issue ..

@LucyWengCSS
Copy link
Author

Hi Debasish,

Thanks so much for your help in the issue.

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.

Thanks again.

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

2 participants