similar to: Unicorn fails to restart gracefully on capistrano deploy

Hi, I have a question about automating the restarting of Unicorn with the following steps, and much appreciate your help. Assumption: (i) "pid" is set to unicorn.pid in the config file; (ii) a Unicorn process is already running. (1) kill -USR2 `cat unicorn.pid` (via Capistrano deployment task for example) (2) Inside the "before_exec" hook in the config file, do: kill -QUIT

Signaling using normal kill(2) is preserved, but the master now prefers to signal workers using a pipe rather than kill(2). Non-graceful signals (:TERM/:KILL) are still sent using kill(2), as they ask for immediate shutdown. This change is necessary to avoid triggering the ubf (unblocking function) for rb_thread_call_without_gvl (and similar) functions extensions. Most notably, this fixes

hi. i''ve been trying to upgrade my stack to ruby 2.0 but keep getting this on ubuntu (not on my local os x): /hello/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:746:in `for_fd'': Bad file descriptor (Errno::EBADF) from /hello/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:746:in `block in inherit_listeners!'' from

Hey guys, I''m sending USR2 to unicorn after cap deploy, and the old master is getting replaced by a new master that doesn''t work. Here are some similar threads I found ... http://rubyforge.org/pipermail/mongrel-unicorn/2010-October/000733.html http://rubyforge.org/pipermail/mongrel-unicorn/2010-October/000717.html I''m not using Bundler, and I have working_directory

--- lib/unicorn/configurator.rb | 19 ++++++++++++++++--- lib/unicorn/http_server.rb | 3 +++ test/unit/test_configurator.rb | 8 ++++++++ 3 files changed, 27 insertions(+), 3 deletions(-) diff --git a/lib/unicorn/configurator.rb b/lib/unicorn/configurator.rb index 0d0eac7..a0ae576 100644 --- a/lib/unicorn/configurator.rb +++ b/lib/unicorn/configurator.rb @@ -441,9 +441,22 @@ class

?Hi, I was wondering if anyone has managed to get the preload_app and SIGUSR2 combination working well with upstart? My issue currently is that when I perform a SIGUSR2 against the master, check everything''s working and close off the old master, upstart then attempts to restart it because the original PID/binary are no longer running. What is the correct way of handling this? In my

Greetings, I''m getting this - ActiveModel::MissingAttributeError: missing attribute: some_attr - on a random basis under a unicorn server, running rails 3.2 and ruby 1.9.3 As the case of the last poster in the following thread - https://github.com/rails/rails/issues/1906 - I too am able to resolve this issue by settingpreload_app to false. However, this is not the behaviour I want to

I am using nginx with unicorn as a reverse proxy. Has been fantastic, but needed to look through some code for first time. Using ruby 1.9.3p194 with rails 3.2.9, development mode with ssl enabled, I start unicorn with -d ...and it does not get served up by nginx. Any ideas, or more information needed? Thanks! Jet Below is my unicorn.rb for developent: # config/unicorn.rb env =

Hi all, I''m having issues with Unicorn and connecting to RabbitMQ using the tmm1-amqp gem. I''ve tried lots of approaches. The classic initializer with Thread.new { EM.run } for the Rails app and even tried using the Qusion library. (https://github.com/danielsdeleo/qusion) I''ve made a simple mod to Qusion for it to monkey patch unicorn too. The code looks

Hi There, Im running an amazon instance with nginx proxying to a unicorn sock. For some reason, even though i specify the production environment, when being visited by nginx, the site shows errors in development form. Interestingly, when running on a port rather than a sock, if i visit that port, the errors are rendered as normal with a 500 page, the same port, throught nginx, shows errors

Hi folks, I''ve experimented a problem while deploying my app, I''ve sent the HUP signal to the master process, I''ve checked everything is ok: new master and workers are spawned and the old ones are killed(I''ve checked the PIDs), but the new code deployed isn''t reflected in the living site, so I''ve to stop and start again unicorn in order to see

I sent this to the author of geoip a few days ago and haven''t heard back, yet. Since he may be on vacation or busy, somebody may also hit this problem in the mean time, I figured I''d post the patch + git repo I sent him here. Unicorn users: The pread(2)/pwrite(2) syscalls are very useful for making libraries like this one (that rely on an on-disk database) compatible with

I''m getting the following errors multiple times per request when using 4.3.0. I do not receive any errors when using 4.2.1. Please CC me on replies, I''m not subscribed to the mailing list. 16:48:42 web.1 | E, [2012-04-26T16:48:42.733954 #87940] ERROR -- : app error: Socket is not connected (Errno::ENOTCONN) 16:48:42 web.1 | E, [2012-04-26T16:48:42.734193 #87940] ERROR

If I''m running two rails apps on the same server using Unicorn, I have to run two instances of Unicorn, right? If so, then here''s a place where passenger might win in terms of memory use, as the rails code will be loaded into memory twice, right? I''m still probably going with Unicorn, but just exploring this first. Thanks, John

Hi all, I''m fighting with the after_fork hook and my sinatra application. The Sinatra app is using active_record, In my unciron.rb file I''m using preload_app true after_fork do |server, worker| ? defined?(ActiveRecord::Base) and ??? ActiveRecord::Base.establish_connection End but I always get the error: ERROR -- : ActiveRecord::AdapterNotSpecified

Hi, I''m deploying Unicorn on a Rails application with RUnit. Technically I''m using Chef''s deployment tools, if any of you are familiar with it (https://github.com/opscode-cookbooks/application_ruby) but to be clear they aren''t doing anything magical, so this is purely an issue with RUnit and Unicorn. The TL;DR of the following post, which has lots of

Switched my RoR (3.1.3, 1.9.2) app from Thin to Unicorn (4.6.2). It ran fine in development (Mac OSX), but when deploying to production on Heroku, it fails silently (no backtrace, no error detail). Log looks like: Starting process with command `bundle exec unicorn start -p 6069 -c ./config/unicorn.rb` /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:634:in

Hi all, I''ve pushed the following patch out go git://git.bogomips.org/unicorn along with a few other Rails-related test updates. This is more of a shotgun fix (but less code is better :) since I haven''t been able to reproduce the brokeness people have been seeing with "unicorn_rails" and Rails 3 betas. Even though "unicorn" works perfectly well for Rails3,

We''re using unicornctl restart with the default before/after hook behavior, which is to reap old Unicorn workers via SIGQUIT after the new one has finished booting. Unfortunately, while the new workers are forking and begin processing requests, we''re still seeing significant spikes in our haproxy request queue. It seems as if after we restart, the unwarmed workers get swamped by

Hello, I''m using unicorn since a while, but now I try to run it the first time inside a FreeBSD jail. The initial start of unicorn works fine and it serves all the requests. But if I want to restart it using the USR2 signal, it (more or less) slowly starts using more and more CPU cycles. There is no error message in the logs and it quite hard to reproduce that error. In 1 of 20 tries,