similar to: why Unicorn doesn't do slow clients

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

http://bugzilla.netfilter.org/show_bug.cgi?id=610 Summary: conntrack doesn't work Product: netfilter/iptables Version: linux-2.6.x Platform: All OS/Version: All Status: NEW Severity: normal Priority: P1 Component: unknown AssignedTo: laforge at netfilter.org ReportedBy: urykhy at

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

Hello All. Is mod_php for apache hiding in a repo somewhere? I did a yum --enablerepo=centosplus install mod_php (as googled) but I don't see any mod_php lurking anywhere. Anyone know what's up? Thanks -- Flambeau Inc. Technology Center - Baraboo, WI Email : tblader at flambeau.com Keyserver: http://pgp.mit.edu KeyID: 0x00E9EC2C

On 07/26/2018 04:48 PM, Arun Khan wrote: > <preamble> > I have deployed Linux/Apache/PHP (node1) + MySQL (node2) with Security > Groups (AWS) or iptables controlling who can connect to the MySQL > server. In topology terms -- a 2 Tier architecture. In AWS - one > can deploy several such instances behind a ELB. Each LAP instance > talks to a MySQL RDS. The LAP instances

I don''t know if there are any folks wrapping Unicorn, but I''ve removed the Unicorn.run method in unicorn.git as part of an effort to reduce stack size (which will improve GC performance and reduce the cost of generating (and examining) backtraces. You can replace: Unicorn.run(app, options) With: Unicorn::HttpServer.new(app, options).start.join This will be in the

hey, i am a big unicorn fan -- i have been running it in production since late 2010, and it is happily handling (literally) billions of backend requests for a popular facebook game. i also <3 unicorns in general ..... so i decided to make an awesome t- shirt, sporting the "Angry Unicorn" that you may remember from github error pages. i hope some of you might like it as well:

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

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 =

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

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

Consider this a joke until somebody who knows crypto well can review it (_and_ kgio-monkey[1]). I know it works with curl (test case included) and I can''t see plain-text when I strace/tcpdump, that''s about it :) Subject: [PATCH] add preliminary SSL support This will also be the foundation of SSL support in Rainbows! and Zbatery. Some users may also want to use this in Unicorn

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

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

Changes: The new check_client_connection option allows unicorn to detect most disconnected local clients before potentially expensive application processing begins. This feature is useful for applications experiencing spikes of traffic leading to undesirable queue times, as clients will disconnect (and perhaps even retry, compounding the problem) before unicorn can even start processing the

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

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

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

Unicorn is a Rack HTTP server for Unix, fast clients and nothing else[1] We now have support for "Transfer-Encoding: chunked" bodies in requests. Not only that, Rack applications reading input bodies get that data streamed off to the client socket on an as-needed basis. This allows the application to do things like upload progress notification and even tunneling of arbitrary stream

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