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
Issue running thin standalone server with redis #437
Comments
In the
Interesting it mentioned Hiredis... |
Debugging the client options... interesting it switches to the Ruby driver just before timing out?!
|
Plot thickens... not only is that last connection using Ruby, it looks like its switched to using a socket?!
|
And another dump when using hiredis and
|
So it seems to be an issue with Rails Eager Loading. It worked on mine and my colleagues local installs because config/environments/development.rb has |
Hi try to increase the timeout (default 5.0 ) in the config\initializers\websocket_rails.rb config.redis_options = {:host => '127.0.0.1', :port => '6379', :timeout => 25.0} |
Hi, I am gonna use websocket-rails gem in rails project deployed on heroku.
As you can see, I am gonna enable standalone server mode. |
This might help issue#313 I've tried that, it works ! |
I have spent the day debugging a very strange issue.
Locally, the Thin server runs fine against Redis 3.2.5 using all default settings.
On our testing server, I have tried Redis 2.8.x (OS repo version) and 3.2.5 (via docker); they both exhibit the same issue.
If I start the server with default settings, it seems to use the
synchrony
driver. No matter what I set the timeout to, the connection times out with this:Redis is running fine (default port). I can telnet to it and MONITOR or KEYS and it responds instantly. The services are all running locally, so firewall should not be a problem here.
I have tried changing the driver to hiredis and ruby, both of these solve the timeout problem but replace it with one that doesn't even error. Thin starts but then freezes; WS & WSS connections just time out (Chrome reports "pending", whereas locally I immediately get a 101 response).
My colleague has tried my code on his laptop and it runs fine. Clearly, this is an environment issue, but I cannot figure out what, specifically, the problem is.
Any tips?
The text was updated successfully, but these errors were encountered: