similar to: Unicorn and streaming in Rails 3.1

Hello all, I have always deploys rails apps with unicorn and nginx as a reverse proxy in the past. However, I am working with a new firm and they would like to use Apache with mod_pagespeed in front of unicorn. We will be deploying a rails 3.1 app with streaming. To me, mod_pagespeed does not seem like a magic bullet, as it appears to be a collection of best practices which have to be rewritten

Hi, For one of our apps we switched to unicorn from mongrel. The unicorn server use to run behind an apache with timeout of 300sec, as sometime the customer may do a large file upload. After we made the switch we started getting lots of Unicorn::ClientShutdown occurred in photos#flash_upload bytes_read=2762663 (pr some other number) We were not able to recreate it in our tests, but support was

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

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 =

Hello all, I''m wondering if you deploy nginx: 1) on the same machine that runs unicorn (exclusively proxying to that) 2) on a different machine that doesn''t run unicorn 3) both, nginx could forward to either to localhost or another host on the same LAN And of course, the reason(s) you chose what you chose. I''m inclined to believe many folks are on 1) simply

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

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

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients. * http://unicorn.bogomips.org/ * mongrel-unicorn at

Hi folks On line #63 of unicorn/http_response.rb a "Status" header is written to the socket. A comment in the code explains that some broken clients require this header and unicorn generously accommodates them. We?re having the opposite problem. One of our clients using Microsoft Windows and ASP haven?t been able to connect to our HTTP API since we moved it to unicorn from passenger.

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,

I''m putting together a small web frontend for a client to upload files into an existing application. It''s trivial - there will never be more than a (small) handful of concurrent connections, but I need a streaming rack.input for upload progress on files up to 500MB or so. I was planning on using Rainbows! with ThreadSpawn and worker_connections=1, then noticed that unicorn is

Hi all, Some of you are wondering about the future of the project, especially since we''re nearing a 1.0 release. == 1.x - bugfixes and Rack-compatibility synchronization The 1.x series will focus mainly on bug fixes and compatibility with Rack as it evolves. If Rack drops the rewindability requirement of "rack.input", Unicorn will follow ASAP and allow TeeInput to be

This is a slow client buffering layer which may be used instead of nginx to protect Unicorn from slow clients. Nightmare! will _never_ beat nginx in raw throughput nor performance. It /may/ be easier to setup than nginx and a suitable alternative to Rainbows! for users who do not wish to maintain a thread-safe/async-safe Rack application. Code changes to the existing Unicorn codebase are

First - Thanks! We''re loving Unicorn. I''m serving about 200K API requests a day on a few linux servers running Unicorn. We have the API calls, and also some admin stuff that has a UI. I have a pair of F5 load balancers in front of the setup with two pools. The API pool passes directly to the unicorns, while the UI pool passes to nginx which passes to unicorn. At

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

Hi, I''m currently giving Nginx + Unicorn a try, to eventually replace Apache + Passenger. So far so good. I have a Rails 3.2.5 app behind Unicorn, itself behind Nginx. In this Rails app, I have set page caching for some resources. They are created in Rails.root/public/ to be directly available to Nginx. When I first hit such a page, the static cache file is not present, so the Rails

I am trying to deploy a rails application to a digitalocean VPS droplet. I have the following setup Ruby on Rails on Ubuntu 12.10 (Nginx + Unicorn). I have installed Ruby ruby-2.0.0-p247 and rails Rails 4.0.0 via rvm but when I try to restart Unicorn I get the following error. /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems /core_ext/kernel_require.rb:45:in