similar to: Master repeatedly killing workers due to timeouts

On Mon, Jan 21, 2013 at 11:28 AM, Eric Wong <normalperson at yhbt.net> wrote: > Charles Hornberger <charles.hornberger at gmail.com> wrote: >> Hi! >> >> I recently noticed this error message when restarting unicorn after a >> code deployment (and I don''t think I recall having seen it before): >> >> I, [2013-01-18T17:54:21.502554 #59285]

Hi, i''m trying to start up unicorn_rails with a rails 3 beta3 project. All I can get out of it is this: I, [2010-05-28T08:54:45.770957 #17852] INFO -- : reaped #<Process::Status: pid 17854 exit 1> worker=0 I, [2010-05-28T08:54:45.771200 #17852] INFO -- : worker=0 spawning... I, [2010-05-28T08:54:45.774049 #17858] INFO -- : worker=0 spawned pid=17858 I,

First off, I love unicorn. Thanks to all who have worked on it. For the first time, I am trying to run a rails 2.3 app with unicorn. I don''t understand what is not set correctly. I have rails 2.3.8 and dependencies installed. I am sure it is something simple.... See output below. Much thanks! Matt config/environment.rb ... RAILS_GEM_VERSION = ''2.3.8'' unless defined?

Hi, I''m serving the puppetmaster application with its config.ru through unicorn - proxied by nginx. I''m using unix sockets, 4 workers, and 2048 backlog. The clients - after their typical "puppet run" - send back a report to the master in YAML. Some clients whose reports tend to be large (close to 2mb) get a 502 bad gateway error and error out. nginx log: 2010/10/22

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 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

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 to everybody. I making shared hosting for rails and rack applications. For app. server i userd phusion passenger, but after some issues with that, want to migrate to unicorn. Is there any way to make unicorn stop all workers and start them on first request? It''ll be really great to have this opportunity. >No subscription is needed to post to the mailing list, let us know

Hi there, I would like to config Monit to monitor our production-unicorn-workers What memory size would you recommend to be the maximum reachable for a worker? so Monit can restart it. Thanks a lot ! Manuel Palenciano

This means we no longer waste an extra file descriptor per worker process in the master. Now there''s no need to set a higher file descriptor limit for systems running >= 1024 workers. --- I just pushed this out to git://bogomips.org/unicorn.git and it''ll be in Unicorn 4.x. The subset of raindrops used by Unicorn should work on all machines with mmap(2) +

Hello all, Last week, I finally decided to put into motion some ideas I''ve been kicking around for a year in my head since last year... Basically I don''t want to have to deal with threads or support platforms that rely on or encourage threads. Especially given MRI 1.9 where kernel threads are more difficult to debug than green ones. Given the limited scope of this project,

Two ideas, one more controversial than the other. First: auto-killing bloated workers.?My current app has some memory leakage that wasn''t really visible on our older passenger setup, since the auto-scaling meant that bloated workers got killed periodically. In a perfect world, we''d find and patch all of the leaks, but in the meantime (and as a safety net) I''d like to get

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

I have strange error that happens after couple of hours. Some instances start to respond on any request with status code 500. Log file unicorn.stderr.log gets populated with this error: app error: undefined method `each'' for nil:NilClass (NoMethodError) /usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.2/lib/rack/utils.rb:267:in `initialize''

I''ve been analyzing our Unicorn-powered Rails app''s performance, and have found that garbage collection is a big factor in slow requests. In the interest of avoiding those performance hits while handling requests, would it be possible to have a unicorn worker run garbage collection after handling a request and before waiting for the next one? Would this be a good idea? Cheers,

I''ve setup nginx with this server { listen 80; server_name unicorn.local; location / { proxy_pass http://unicorn; } } upstream unicorn { server unix:/Users/mattmongeau/projects/test/unicorn/tmp/sockets/unicorn.sock; } When I run unicorn_rails -c config/unicorn.rb -E development I can access the application just fine on unicorn.local When I run unicorn_rails -c

Hi, A couple days ago, I was trying to run Unicorn for Ramaze, and found that `Unicorn.run'' didn''t share the same interface with other Rack handlers, i.e. `options[:Host]'' and `options[:Port]'' Because of this, I can''t just use: Rack::Handler.register(''unicorn'', ''Unicorn'') And invoke this:

Hi - I tried to get Daemontools and Unicorn working together a while back - there are issues on USR2 restart because of the pid change - I''m hoping someone in the community will have some understanding of this issue I documented my experience and eventual defeat here : http://log.robotarmyma.de/post/2053448029/daemontools-ubuntu-rvm-bundler-unicorn-install Any help would be received

I am having issues when using unicorn with a Capistrano deployment. >From what I have been able to understand Capistrano uses a scheme in wich every release is deployed inside the releases directory under a unique name and if the transaction was successful, creates a symlink named current that will point to that release. So I end up with a deployment directory such as:

Hi Due to putting a DVD in my Virtual Machine Host Computer which then filled the logs with errors and subsequently filled the drive crashing all vms. Luckily I had a backup of the DC image which I restored and some machines just worked and some can?t find KDC kinit: Cannot contact any KDC for realm 'BALEWAN.UNICORN.COM' while getting initial credentials I have tried leaving the domain