Puma crashes with no output when stdout_redirect is set

[natew]

Using rails 4, rubinius at master (372b2d2) and puma 2.5.0.

Current config:

#!/usr/bin/env puma

basedir = '/var/www/2u/web/current'

directory "#{basedir}"
environment 'production'
daemonize true

bind "unix://#{basedir}/tmp/puma/puma.sock"
pidfile "#{basedir}/tmp/puma/pid"
state_path "#{basedir}/tmp/puma/state"

# stdout_redirect "#{basedir}/tmp/log/out.puma.log", "#{basedir}/tmp/log/err.puma.log", true

threads 4, 24
#workers 1
preload_app!

When i uncomment the stdout_redirect it will write to out.puma.log:

=== puma startup: 2013-08-27 16:09:15 +0000 ===

But it crashes after what seems like the full bootup, with nothing going into err.puma.log.

Edit: looks like working now.

[knopkodav]

The same problem again.

$ ruby -v
ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-linux]

$ bundle exec puma -C ./config/puma.rb
[32374] Puma starting in cluster mode...
[32374] * Version 2.7.0, codename: Earl of Sandwich Partition
[32374] * Min threads: 4, max threads: 16
[32374] * Environment: production
[32374] * Process workers: 2
[32374] * Preloading application
[32374] * Listening on unix:///srv/prj/shared/sockets/puma.sock
[32374] * Daemonizing...

No process, no answer, and no log files appears.

UPD: our config:

      daemonize
      environment           'production'
      directory             '/srv/prj/releases/20131205131955'
      state_path            '/srv/prj/shared/sockets/puma.state'
      bind                  'unix:///srv/prj/shared/sockets/puma.sock'
      activate_control_app  'unix:///srv/prj/shared/sockets/pumactl.sock'
      stdout_redirect       '/srv/prj/shared/log/puma.stdout', '/srv/prj/shared/log/puma.stderr', true

      threads 4, 16
      workers 2
      preload_app!
      on_worker_boot do
        ActiveSupport.on_load(:active_record) do
          ActiveRecord::Base.establish_connection
        end
      end

[zekus]

I have something similar too
it crashes and nothing gets written in the logs. I can see the error only if I do not demonize it

[evanphx]

@zekus what error do you see when not demonized?

[zekus]

@evanphx it was a syntax error in the application code but the point is: shouldn't puma fail to start but write the reason in the log?

[evanphx]

Ok, here is the issue:

Some people want puma to load the code BEFORE daemonizing, so that the user can see if there is an error. Other people need it to load AFTER demonizing because they start threads in their initializers and thus need them to survive.

So there is this tension between these 2 needs. I'll see about at least making it so that if there is an error like this, it shows up in the stderr output.