OSX hangs on close_io about daemons HOT 8 CLOSED

Update - So delayed_job calls Daemons.run_proc from within an environment that already has Rails loaded and Rails doesn't seem to like having all its IO closed out from underneath it.

Perhaps a cmd line option is in order to disable the close_io call within simulate? Or running without simulate at all?

from daemons.

Can you try to replace [$stdin, $stdout, $stderr]by [STDIN, STDOUT, STDERR]? There was a change in the last release that might have had undesired side effects.

from daemons.

I tried changing it to this:

    ObjectSpace.each_object(IO) do |io|
      unless [STDIN, STDOUT, STDERR].include?(io)
        print "Attempting "
        pp io
        io.close rescue nil
      else 
        puts "Skipping #{io}"
      end
    end

And the output is:

jack:import_tester sblackstone$ ./bin/delayed_job run
Skipping #<IO:0x007fae328a2b08>
Skipping #<IO:0x007fae328a2ba8>
Skipping #<IO:0x007fae328a2c48>
Attempting #<File:/Users/sblackstone/code/import_tester/log/development.log>
Attempting #<File:/Users/sblackstone/.rvm/gems/ruby-2.3.1/gems/delayed_job-4.1.2/lib/delayed/command.rb (closed)>
Attempting #<IO:fd 20>

with lsof showing:

ruby      28355 sblackstone   20     PIPE 0x2e2061ee1d21f023       16384         ->0x2e2061ee3d31bc23

from daemons.

So is it still hanging? (in the original order of the calls)

from daemons.

Yep - its hanging at the last line in that output... Calling close on that fd..

from daemons.

Then I rather don't think it is a daemons issue. Can you open a bug report for delayed_job?

from daemons.

will do - thanks.

from daemons.

Cross posting this from the delayed_job ticket:

Alright, so it only occurs when rails is running in development mode. If you run bin/delayed_job run with daemons, it will hang..

But then if you killall -9 fsevent_watch (part of Rails dev mode) - it will then get past the hung IO.close and enter in into the normal run loop and start processing jobs..

from daemons.