Rails - Apr 2012 - Server starting failed (ruby 1.9.3p194, rails 3.2.3 )

Server starting failed (ruby 1.9.3p194, rails 3.2.3 )

Attachments:
http://www.ruby-forum.com/attachment/7346/ruby193err.txt


-- 
Posted via http://www.ruby-forum.com/.

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

On Sunday, April 29, 2012 7:51:38 AM UTC-3, Ruby-Forum.com User
wrote:
>
> Server starting failed (ruby 1.9.3p194, rails 3.2.3 ) 
>
> Attachments: 
> http://www.ruby-forum.com/attachment/7346/ruby193err.txt 
>
>
Please read the FAQ section that was mentioned with the release of 
RubyInstaller 1.9.3-p194:

https://groups.google.com/d/msg/rubyinstaller/nTcdd55fNiY/Mp-CitrdWkQJ

Will copy it here in case you don''t see it:

= Q: What means by "increased file descriptors", how that affects me?

A: By default Ruby 1.9 was limited to 64 sockets when using select() 
function.
select() is a mechanism to set and clear the state of sockets that are 
waiting
for data. In other OS you have different ''pooling'' mechanisms.

Most of the web servers that run on Ruby, specially the evented ones depends
on select().

Without this change these frameworks/libraries wouldn''t be able to use
more
than 64 open sockets, which affects any of us attempting to use Ruby on 
Windows
for more than testing things out.

Please note that this is a workaround to a bigger issue: select() and the
associated functions are not the recommended or optimally way to interact 
with
sockets on Windows.

If you encounter a problem running a pre-compiled evented library against 
this
build, please ask the library author to recompile with -DFD_SETSIZE=32767.

=
This will affect Thin because it uses EventMachine. Until that issue gets 
sorted out, you need to:

A) build locally EventMachine:

gem install eventmachine --pre --platform=ruby

B) Request the gem authors to release a gem with the flag updated

We are discussing the technical challenges to solve that at Ruby level:

http://bugs.ruby-lang.org/issues/6352

--
Luis Lavena

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/TdUXsp4IJK4J.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.