Error in Passenger 3.0.9 and Ruby 1.9.3dev

[Strider]

I see the following in my error logs. (Removed Ruby bug notice.)
Looking through past emails, it was mentioned that this was fixed in
Passenger 3.0.8. Is this not true? Is there a workaround other than
downgrading ruby?

Prior Reference: http://groups.google.com/group/phusion-passenger/browse_thread/thread/bdd08ae94ebeb99c


Log:
[ASYNC BUG] thread_timer: select
EBADF

ruby 1.9.3dev (2011-09-23) [i386-solaris2.10]

[ASYNC BUG] consume_communication_pipe: read

EBADF

ruby 1.9.3dev (2011-09-23) [i386-solaris2.10]

[Josh Nichols]

I'm seeing this with passenger 3.0.9 and ruby-1.9.3-rc1 as well.

Same exact log as reported already here and on the earlier thread
(http://groups.google.com/group/phusion-passenger/browse_thread/thread/
bdd08ae94ebeb99c/8cc085241fa305b4?lnk=gst&q=%5BASYNC+BUG%5D
+thread_timer%3A+select++#8cc085241fa305b4):

------------------------------------------------------------------------------------------------------------------------
ruby 1.9.3dev (2011-09-23 revision 33323) [x86_64-linux]

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension
libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html
------------------------------------------------------------------------------------------------------------------------

The workaround of commenting out
`NativeSupport.close_all_file_descriptors` in lib/phusion_passenger/
abstract_server.rb does still work, but I'm guessing that's not a
'proper' fix.

- Josh

On Oct 12, 2:41 pm, Strider <strid...@gmail.com> wrote:
> I see the following in my error logs.  (Removed Rubybugnotice.)
> Looking through past emails, it was mentioned that this was fixed in
> Passenger 3.0.8.  Is this not true?  Is there a workaround other than
> downgrading ruby?
>

> Prior Reference:  http://groups.google.com/group/phusion-passenger/browse_thread/thread...
>
> Log:
> [ASYNCBUG]thread_timer:select

> EBADF
>
> ruby 1.9.3dev (2011-09-23) [i386-solaris2.10]
>

> [ASYNCBUG] consume_communication_pipe: read

[Matthew Jones]

I ended up going back to ruby 1.9.2, which I guess is fine since 1.9.3 is still beta.  I wouldn't use that workaround for long due to memory issues.

[cdunn]

fwiw I'm also getting these errors on ruby 1.9.3-p0 on both ubuntu
natty and oneiric and also with both nginx and apache.

On Oct 12, 11:41 am, Strider <strid...@gmail.com> wrote:
> I see the following in my error logs.  (Removed Ruby bug notice.)
> Looking through past emails, it was mentioned that this was fixed in
> Passenger 3.0.8.  Is this not true?  Is there a workaround other than
> downgrading ruby?
>

> Prior Reference:  http://groups.google.com/group/phusion-passenger/browse_thread/thread...

[Hongli Lai]

Ruby 1.9.3 should be officially supported since Phusion Passenger
3.0.8. I'm on OS X Snow Leopard and I confirm that Phusion Passenger
3.0.9 works with Ruby 1.9.3. Can anybody else confirm this?

--
Phusion | Ruby & Rails deployment, scaling and tuning solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[ur5]

I can confirm the problem.
I get the error message:

- - - - - -

[ASYNC BUG] thread_timer: select
EBADF

ruby 1.9.3p0 (2011-10-30) [x86_64-linux]

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension
libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

- - - - - -

setup:

ruby 1.9.3-p0 compiled from source
Linux version 2.6.32-5-vserver-amd64 (Debian 2.6.32-35)(gcc version
4.3.5 (Debian 4.3.5-4) )
Apache/2.2.16 (Debian)
passenger (3.0.9)

On 1 Nov., 12:00, Hongli Lai <hon...@phusion.nl> wrote:
> Ruby 1.9.3 should be officially supported since Phusion Passenger
> 3.0.8. I'm on OS X Snow Leopard and I confirm that Phusion Passenger
> 3.0.9 works with Ruby 1.9.3. Can anybody else confirm this?
>
> --
> Phusion | Ruby & Rails deployment, scaling and tuning solutions
>
> Web:http://www.phusion.nl/

> E-mail: i...@phusion.nl

[Greg Reinacker]

I get the same error message on Ubuntu 10.04, with Ruby 1.9.3p0 and Passenger 3.0.9. I even tried a clean install from scratch of the whole machine, in case I had something weird going on, but same error again.

Greg

> --
> You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
> To post to this group, send email to phusion-...@googlegroups.com.
> To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.
>

[TonyLa]

I can also confirm that I have experienced this error with Ruby 1.9.3-
p0/Passenger 3.0.9 on Debian (squeeze).

[Marten Veldthuis]

Yeah, I can confirm this error too.

[dura]

Same probleme here :(
-----
[Thu Nov 03 11:03:41 2011] [notice] Apache/2.2.15 (Unix) DAV/2
Phusion_Passenger/3.0.9 mod_ssl/2.2.15 OpenSSL/1.0.0-fips configured
-- resuming normal operations
/usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.9/lib/
phusion_passenger/platform_info/operating_system.rb:33: Use RbConfig
instead of obsolete and deprecated Config.
/usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.9/lib/
phusion_passenger/platform_info/operating_system.rb:33: Use RbConfig
instead of obsolete and deprecated Config.

[ASYNC BUG] thread_timer: select
EBADF

ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]

[Hongli Lai]

We're working on this right now, but I need some more feedback. Let's
continue the discussion at
http://code.google.com/p/phusion-passenger/issues/detail?id=714