rails server dies (but worker doesn't) upon first request

samuelkadolph / unicorn-rails

unicorn-rails is a simple gem that sets the default server for rack (and rails) to unicorn.

MIT License

127 stars 22 forks source link

rails server dies (but worker doesn't) upon first request #3

Closed drnic closed 11 years ago

drnic commented 11 years ago

=> Booting Unicorn
=> Rails 3.2.8 application starting in development on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
listening on addr=0.0.0.0:3000 fd=22
worker=0 spawning...
master process ready
worker=0 spawned pid=86872
worker=0 ready
...
first request to http://localhost:3000/
Assertion failed: ok (mailbox.cpp:84)
[1]    86870 abort      bundle exec rails s

Afterwards, the "rails worker" is still running.

What might cause this abort do you think?

drnic commented 11 years ago

This was on my OS/X machine. When I pushed to cloudfoundry, the "rails server" did not die

samuelkadolph commented 11 years ago

Assertion failed: ok (mailbox.cpp:84) sounds like it's coming from a gem you're using. What gems are you using that deal with mail?

rails server doesn't die in this case since only the worker process should die and the master will respawn one when that happens.

drnic commented 11 years ago

Fair enough - looks like it might be a 0mq bug https://zeromq.jira.com/browse/LIBZMQ-356

Thanks mate! Nic