-
-
Notifications
You must be signed in to change notification settings - Fork 279
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
NOSCRIPT No matching script. Please use EVAL. #168
NOSCRIPT No matching script. Please use EVAL. #168
Comments
I got the same error when try to add scheduled jobs to the queue through UI |
@mhenrixon, this gems works great but hopefully this will be fix. I'll try to send some pull request if I have some extra time. ;) |
Woops sorry I missed this, what seems to be the problem? What environment etc? |
Production environment. @warmwind, what redis-server are you using? |
@itsmechlark it is Redis server v=3.0.3 sha=00000000:0 malloc=libc bits=64 build=da32bfb2228a888d |
I see the same problem with Redis server v=3.0.3 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=4284de9902883ae9 and the following gems:
|
Same issue with sidekiq-unique-jobs 4.0.17 |
I honestly can't see how this could possibly have anything to do with the gem. Before using the script there is a call to check for if it has been added and adding it if not. Can anyone think of what might be possibly go wrong here? |
It looks like the root cause might be a terminated redis connection, in our case due to exceeding max file descriptors. Would it be possible for the gem to handle that exception separately? I suppose the error message leads people to think this is coming from the gem when in fact they should be looking elsewhere :) |
+1, same issue here sidekiq-unique-jobs 4.0.17, redis 2.8.4 behind ha proxy. |
same issue with redis 3.0.0, sidekiq-unique-jobs 4.0.17 and sidekiq 3.4.1
Backtrace
|
Hi, I've pushed the fix on PR #178 In order to get the NOSCRIPT error you can run a few sidekiq jobs, then run |
Hi, I've tried the version from the pull request and it fixes the problem we were having.....this was using version 3.0.7 of redis. |
fix for #168. Handle the NOSCRIPT by sending the script again
same problem |
Was facing same issue. Resolved it by upgrading sidekiq - |
Redis server v=3.0.6 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=efefc210bd1220c
rails v4.2.5.1
sidekiq v4.2.5.1
redis v3.2.2
The text was updated successfully, but these errors were encountered: