similar to: nginx + unicorn deployment survey

I would love to see a timestamp in each line of unicorn stderr and stdout logs. Has this been considered? Thanks. Best, alex sharp

Has anyone seen anything like this before? I can get it to happen all the time if I issue a HEAD request, but it only happens very intermittently on GET requests. I''m using Ruby 1.9.2p180. Any ideas on where to start debugging? 204.93.223.151, 10.195.114.81 - - [11/Aug/2011 21:03:50] "GET / HTTP/1.0" 200 37902 0.5316 app error: Content-Length header was 37902, but should be

Hi, This morning, while checking for a correct deployment, we found out that the Unicorns we are using were sending 500 Internal errors very frequently to the HAProxy that sits in front of them. After some investigation, It turned out that HAProxy checks the backend by opening and closing a connection to the unicorn. Unfortunately the Unicorns we use ( v 0.990.0 ) will try to reply to this probe

Strange error which took down my server today: Unhandled listen loop exception #<Errno::EMFILE: Too many open files - accept>. /usr/local/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/unicorn-3.3.1/lib/unicorn/http_server.rb:606:in `kgio_tryaccept'' /usr/local/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/unicorn-3.3.1/lib/unicorn/http_server.rb:606:in

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:

We''ve been running unicorn-3.6.2 on REE 1.8.7 2011.12 in production for quite some time and we use monit to monitor each unicorn worker. Occasionally, I''ll get a notification that a worker has timed-out and has been re-spawned. In all these cases, when I look at the rails logs, I can see the last request that the worker handled, and they all have appeared to complete

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,

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

Installing from RubyGems.org: gem install --pre unicorn >From db919d18e01f6b2339915cbd057fba9dc040988b Mon Sep 17 00:00:00 2001 From: Eric Wong <normalperson at yhbt.net> Date: Tue, 29 Jan 2013 21:02:55 +0000 Subject: [PATCH] unicorn 4.6.0pre1 - hijacking support This pre-release adds hijacking support for Rack 1.5 users. See Rack documentation for more information about hijacking.

Hi All, as I can see on https://github.com/defunkt/unicorn/blob/master/lib/unicorn.rb#L53 the?Rack::CommonLogger used only in development env and in weird evn called "deployment". Any chance to add "production" to this case? Serg Podtynnyi

Changes: Rewindable "rack.input" may be disabled via the "rewindable_input false" directive in the configuration file. This will violate Rack::Lint for Rack 1.x applications, but can reduce I/O for applications that do not need a rewindable input. This release updates us to the Kgio 2.x series which should play more nicely with other libraries and applications. There are

IPv4 addresses started looking very ugly the first time I got IPv6 working on bogomips.org. In case somebody else can''t stand how IPv4-mapped-IPv6 addresses look, the workaround is to use two listeners and ensure the IPv6 one is ipv6only. Unicorn itself supports IPv6, too, but nobody uses/needs it. I''ll add :ipv6only support shortly (probably tomorrow). >From

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,

Hi, I''m wondering why SIGINT and SIGTERM both were chosen for the quick shutdown? I agree with SIGINT but not with SIGTERM. A lot of unix tools send SIGTERM as default (kill, runit among some) and it seems to be the standard way of telling a process to quit gracefully but not among Ruby people (there are a few other ruby processes behaving the same way). I just think it''s weird

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

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

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

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

In case more people are interested, I originally posted the following to ruby-core: http://mid.gmane.org/20101210190448.GA6534 at dcvr.yhbt.net Eric Wong <normalperson at yhbt.net> wrote: > zuerrong <zuerrong at gmail.com> wrote: > > 2010/12/10 Tony Arcieri <tony.arcieri at medioh.com>: > > > And Unicorns are fantastical mythical creatures! > > > >