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
Bug V2.4 - disconnected redis #1853
Comments
I am also encountering the same issue... Redis is connected fine but after_fork the worker complains that it can't connect to Redis... This issue doesn't happen when Im running locally but once I push into Docker swarm its occurs continuously and I've tried everything... I am now reverting to 2.2.1 as well |
If I open the rails console and do Resque.redis = ENV.fetch(REDIS_URL) it connects |
What version of the redis gem are you guys running when this happens? |
I see this issue a few times a day. I'm running resque (2.5.0) |
This still happens to me on Resque 2.5.0. I've had it about 9 times in the last month on Heroku. |
All of my exceptions occur on the call to
|
Hello,
I'm working on heroku with multi worker and I have a problem with resque V2.4
I often have
SSL_read: sslv3 alert bad record mac
errorIt has been fixed in 2.2.1 :
https://github.com/resque/resque/pull/1739/files
And in the 2.4 the reconnect method in data_store file (https://github.com/resque/resque/blob/master/lib/resque/data_store.rb) :
Downgrading the gem to 2.2.1 resolve my problem.
Maybe something I'm doing wrong with 2.4 version ?
Thanks for your feedback
The text was updated successfully, but these errors were encountered: