Listen loop error: #<IOError: closed stream> about puma

[kfatehi]

I get a similar error (Listen loop error), but with SSL, using Ruby 1.9.3p125

Mon Apr 23 15:43:08 -0700 2012: Listen loop error: #<OpenSSL::SSL::SSLError: SSL_accept SYSCALL returned=5 errno=0 state=SSLv3 read client certificate A>
/Users/spike/.rvm/rubies/ruby-1.8.7-p357/lib/ruby/1.8/openssl/ssl-internal.rb:166:in `accept'
/Users/spike/.rvm/rubies/ruby-1.8.7-p357/lib/ruby/1.8/openssl/ssl-internal.rb:166:in `accept'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/lib/puma/server.rb:217:in `run'
(eval):3:in `each_without_optional_block'
(eval):3:in `each'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/lib/puma/server.rb:213:in `run'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/lib/puma/server.rb:204:in `initialize'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/lib/puma/server.rb:204:in `new'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/lib/puma/server.rb:204:in `run'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/lib/puma/cli.rb:428:in `run'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/gems/puma-1.2.1/bin/puma:10
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/bin/puma:19:in `load'
/Users/spike/.rvm/gems/ruby-1.8.7-p357@myapp/bin/puma:19

It is nonfatal, the request still is handled correctly, there are no noticeable effects as a result, but I see this in the log. My guess is that Puma is trying to read the client certificate, but there is none, and instead of failing that routine gracefully it outputs this error?

Thanks

[beathyate]

I get the same error with MRI 1.9.3p194, even on puma 1.4.0

2012-06-07 21:23:31 +0000: Listen loop error: #<OpenSSL::SSL::SSLError: SSL_accept SYSCALL returned=5 errno=0 state=unknown state>
/usr/local/lib/ruby/1.9.1/openssl/ssl-internal.rb:164:in `accept'
/usr/local/lib/ruby/1.9.1/openssl/ssl-internal.rb:164:in `accept'
/usr/local/lib/ruby/gems/1.9.1/gems/puma-1.4.0/lib/puma/server.rb:217:in `block (2 levels) in run'
/usr/local/lib/ruby/gems/1.9.1/gems/puma-1.4.0/lib/puma/server.rb:213:in `each'
/usr/local/lib/ruby/gems/1.9.1/gems/puma-1.4.0/lib/puma/server.rb:213:in `block in run'

[beathyate]

BTW I'm using Ubuntu Server 12.04 (32bit) and the site works, but that gets printed to the logs.

[sorentwo]

The most recent version cited here is 1.4.0. Can any of you confirm if this is still an issue with the 2.0 betas?

[rumblinthebronx]

I am getting a similar error while running puma-1.6.3 java on jruby,

Error in reactor loop escaped: Detected invalid array contents due to unsynchronized modifications with concurrent users (ConcurrencyError)
org/jruby/RubyArray.java:2494:in `delete'
/home/developer/.rvm/gems/jruby-1.7.2/gems/puma-1.6.3-java/lib/puma/reactor.rb:51:in `run'
org/jruby/RubyArray.java:1613:in `each'
/home/developer/.rvm/gems/jruby-1.7.2/gems/puma-1.6.3-java/lib/puma/reactor.rb:26:in `run'
/home/developer/.rvm/gems/jruby-1.7.2/gems/puma-1.6.3-java/lib/puma/reactor.rb:95:in `run_in_thread'
_____________________________________________________________________________________________
developer@localhost ~ $ jruby --version
jruby 1.7.2 (1.9.3p327) 2013-01-04 302c706 on OpenJDK 64-Bit Server VM 1.7.0_09-b30 [linux-amd64]
developer@localhost ~ $ gem list puma

*** LOCAL GEMS ***

puma (1.6.3 java)

[evanphx]

This is fixed in 2.0.

[x3qt]

Experienced same issue on heroku during stress and security testing. Using rails 4.0, ruby 2.0.0p247 and puma 2.5.0.

Error message:

2013-08-14T10:06:48.859102+00:00 app[web.1]: Error in reactor loop escaped: closed stream (IOError)
2013-08-14T10:06:48.959732+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/puma-2.5.0/lib/puma/reactor.rb:99:in `close'
2013-08-14T10:06:49.061355+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/puma-2.5.0/lib/puma/reactor.rb:99:in `ensure in run'
2013-08-14T10:06:49.166861+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/puma-2.5.0/lib/puma/reactor.rb:100:in `run'
2013-08-14T10:06:49.272039+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/puma-2.5.0/lib/puma/reactor.rb:107:in `block in run_in_thread'

Update: Saw puma 2.5.1 was released. Will update and report soon.

Update: 2.5.1 also affected.

[x3qt]

Cast @evanphx

[evanphx]

@x3qt Please open a new issue with as much info as you have