n...@auger.net wrote:
> 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 r
We do not attempt to write HTTP responses for socket errors if
clients disconnect from us unexpectedly.
Additionally, we do not hide backtraces EINVAL/EBADF errors, since
they are indicative of real bugs which must be fixed.
We do continue to hide hide EOF, ECONNRESET, ENOTCONN, and EPIPE
because
As of r40610 in ruby trunk, internal encoding is ignored if
external coding is ASCII-8BIT (binary)
ref: r40610 http://svn.ruby-lang.org/repos/ruby/trunk
---
test/unit/test_util.rb | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/test/unit/test_util.rb b/test/unit/tes
9af083d7f6b97c0f5ebbdd9a42b58478a6f874b7:
test_util: fix encoding test for Ruby trunk (2.1.0dev) (2013-08-17 01:09:46
+)
Eric Wong (2):
http_server: improve handling of client-triggerable socket errors
test_util: fix encoding test for Ruby
Tim Snowhite wrote:
> We run Unicorn with ruby 1.8.7 on FreeBSD and began experiencing many
> early terminations of the body stream when attempting to transfer
> files over a couple hundred Kb. The body stream would terminate with
> …data…HTTP 1.1 500 Internal Service Error, due to raising an
> Er
Josh Sharpe wrote:
> I haven't seen my mailing list request confirmed. Please CC me your
> responses - thanks!
Done! (I think the confirmation should've gone through, Rubyforge has
been acting funny...). Anyways it's common practice on many FOSS
mailing lists to Cc: all parties (but not Ruby-r
Jeremy Lecour wrote:
> > This may be useful for daemontools and similar init replacements
> > which behave badly when the master process is replaced during the
> > normal SIGUSR2 && SIGQUIT routine.
>
> Does Monit fall into this category of tools?
>
> Each time I restart a master process I have
Troex Nevelin wrote:
> On Jan 15, 2013, at 21:44 , Eric Wong wrote:
> > But seriously, who will wait 120s for a website to load?
>
> I have similar situation, in my case it's admin interface so admin
> knows that some operations need time to process and will wait.
>
&
Comments/reports of success/failure appreciated.
(Bcc-ing the user who contacted me privately about daemontools :)
8<--
From: Eric Wong
Subject: [PATCH] unicorn_forever: new executable to respawn masters
Warning: lightly tested (
Hi all, just wondering how many users are still on Ruby 1.8. unicorn
still supports 1.8 for now, but going 1.9.3+ (or even 2.0.0+) will allow
us to kill some old code we've been keeping around...
Fwiw, "enterprise" distros (e.g. CentOS 6.x) will remain supported by
their distributors for many yea
Changes:
Thanks to Micah Chalmer for this fix. There are also minor
documentation updates and internal cleanups.
Eric Wong (4):
doc: update documentation for systemd + PrivateTmp users
test_signals: increase delay between Process.kill
HttpParser#next? becomes
Jon Wood wrote:
> Hello,
>
> I'm quite consistently seeing an issue where Unicorn leaves its PID
> files in place after a clean shut down, which is causing some issues
> when deploying releases that update Unicorn config.
>
> We're doing hot restarts with USR2+QUIT, and using Upstart for process
Jonathan Rudenberg wrote:
> On Jun 13, 2013, at 2:22 PM, Eric Wong wrote:
> > Jonathan Rudenberg wrote:
> >> RFC 2616 section 9.4[1] states:
> >>
> >>> The HEAD method is identical to GET except that the server MUST NOT
> >>> return a mess
Jonathan Rudenberg wrote:
> On Jun 13, 2013, at 3:21 PM, Eric Wong wrote:
> > Try the following:
> Thanks, this stack works.
Good to know!
> > I added the Rack::ContentLength (it's already in the default middleware
> > stack) since I believe Rack::Chunked add
Jonathan Rudenberg wrote:
> RFC 2616 section 9.4[1] states:
>
> > The HEAD method is identical to GET except that the server MUST NOT return
> > a message-body in the response.
>
> A HEAD request against this simple Rack app running on unicorn-4.6.2:
>
> require 'rack'
>
+ use Rack::
he :no_default_middleware option
was set from the lambda could not detect anything. This patch copies
it to a local variable that won't get clobbered, restoring the feature.
[ew: squashed test commit into the fix, whitespace fixes]
Signed-off-by: Eric Wong
---
lib/unicorn.rb
Btw, I (and I'm sure other readers) would be interested in what your
diagnosis/resolution is, regardless of whether it's a problem with
unicorn or anything else.
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinf
Alexander Dymo wrote:
> In short:
> - we have two groups of workers:
> - one serving long-running requests that take more than 10 sec, listening
> to a '/tmp/long_requests_unicorn.sock' socket
> - another serving normal requests, listening to '/tmp/unicorn.sock' socket
> - nginx determines wh
Graham Christensen wrote:
> 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
Andrew Stewart wrote:
> On Wed, May 15, 2013, at 11:28 AM, Eric Wong wrote:
> > If you're using preload_app, I suspect it's some background thread
> > or hook causing it. Otherwise, can you reproduce this with a barebones
> > application?
>
> Do you mean so
Andrew Stewart wrote:
> I was wondering why my Unicorn master process's memory use grows over
> time.
>
> As as I understand it, when I (re)start Unicorn a master process spins
> up which loads my Rails app. The master process then brings up worker
> processes which handle traffic to the app.
C
pille wrote:
> hi,
>
> is it possible to add static and dynamic HTTP response headers in
> unicorn.conf.rb?
No, but it is easily possible with a Rack config.ru
> i'd like to add the hostname of the worker for debugging and a
> timestamp, when the request was worked on.
>
> currently this is do
STS_DEFAULT
assert HttpParser::KEEPALIVE_REQUESTS_DEFAULT >= 0
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
{ sock.syswrite(buf) }
Process.kill(:KILL, killer)
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
Andreas Falk wrote:
> On Thu, Apr 25, 2013 at 10:51 AM, Eric Wong wrote:
> > Andreas Falk wrote:
> >> 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 s
Andreas Falk wrote:
> 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 n
Eric Wong wrote:
> If you're using Ruby 1.9 or later, maybe sending SIGBUS/SIGSEGV can work
> to trigger a Ruby core dump.
>
> Do not attempt to install SIGSEGV/BUS handler(s) via Ruby, Ruby 1.9
> already handles those internally. Ruby 2.0.0 prevents trapping SEGV/BUS
>
Bill Vieux wrote:
> I am getting occasional worker timeouts for a Rails app hosted on
> Heroku. I have rack-timeout set at the top of the middleware with a
> shorter timeout than unicorn workers, but it is not firing for some
> reason.
Which version of Ruby is this and what C extensions are you u
our problem, but I'll bet that more than a few Fedora users are
> using TCP sockets instead of unix sockets with Unicorn because of
> this.
Thanks, I'll queue up something like the following patch.
Comments/corrections greatly appreciated:
--
Jacob wrote:
> I know that Unicorn opens and shares it's bound socket amongst its
> sub-processes, however I was hoping I could also pre-open a socket to
> be handed off to Unicorn.
Yes, but unicorn has this feature to support in-place upgrades
(SIGUSR2). You still need to tell unicorn about the
"Lin Jen-Shin (godfat)" wrote:
> On Wed, Apr 3, 2013 at 6:36 AM, Eric Wong wrote:
> > Fwiw, Cool.io works pretty well in my experience.
> [...]
> > I can also help fix Cool.io bugs since it's written in C, but I can't
> > fix EM bugs: C++ is too b
Tom Pesman wrote:
> > Probably not, at least it won't improve _consistency_ of performance
> > without changing your app.
> >
> > The problem with buffering in Rainbows!+EM is the buffering happens after
> > the work is distributed to different worker processes (Rainbows!+EM is
> > still single-th
Tom Pesman wrote:
> > The request body doesn't seem to be there, presumably because Heroku
> > isn't sending it.
> >
> > Doe heroku fully buffer the request body before sending it to unicorn?
> > nginx fully buffers, and this is why I can only recommend nginx for slow
> > clients.
> >
> > The prox
Hongli Lai wrote:
> On Mon, Mar 11, 2013 at 11:48 PM, Eric Wong wrote:
> > Can we designate gems be signed by a trusted third party (e.g. you?)
> > That's how Debian (and presumably other OS distros work).
> >
> > _Nobody_ should trust me. I have and maintai
Tom Pesman wrote:
> > Tom Pesman wrote:
> >> Eric Wong wrote:
> >> > Tom Pesman wrote:
> >> >> I'm trying to fix a problem I'm experiencing with my Rails
> >> >> application hosted at Heroku. I've one POST reques
Hongli Lai wrote:
> After the recent Rubygems.org hack it became clear that somethings
> needs to be done about authenticating gems. One of the efforts that
> was launched is http://www.rubygems-openpgp-ca.org/. We at Phusion
> have just finished signing all our gems and repositories with our PGP
Tom Pesman wrote:
> Eric Wong wrote:
> > Tom Pesman wrote:
> >> I'm trying to fix a problem I'm experiencing with my Rails
> >> application hosted at Heroku. I've one POST request which hangs and
> >> with the help of a customized rack-timeout
Tom Pesman wrote:
> Hello,
>
> I'm trying to fix a problem I'm experiencing with my Rails
> application hosted at Heroku. I've one POST request which hangs and
> with the help of a customized rack-timeout gem
> (https://github.com/tompesman/rack-timeout) I managed to get a
> stacktrace: https://g
Alexey Chernenkov wrote:
> 2013/3/1 Eric Wong :
> > Alexey Chernenkov wrote:
> >>
> >> Can anyone explain why my Unicorn installation (for RoR site) have so
> >> many worker threads?
> >> * screenshot: http://i.stack.imgur.com/U9TFR.png
>
Alexey Chernenkov wrote:
> Hello!
>
> Can anyone explain why my Unicorn installation (for RoR site) have so
> many worker threads?
>
> * screenshot: http://i.stack.imgur.com/U9TFR.png
> * unicorn.rb: https://gist.github.com/907th/4995323
It's probably some gem/library you're using which spa
Hongli Lai wrote:
> On Tue, Feb 26, 2013 at 6:26 PM, Eric Wong wrote:
> > That's not true, Rainbows! was designed to serve clients directly.
> > On the other hand, I do not know if anybody uses Rainbows! that way
> > (or at all in production).
>
> I didn't
Hongli Lai wrote:
> On Tue, Feb 26, 2013 at 4:08 PM, Amol Dev wrote:
> > We are hosting multiple Rails applications on same server and using
> > Passenger + Apache. I can see Unicorn be useful for seamless
> > deploys, few questions running it on Rails platform with 50+ rails
> > apps:
> Rainbow
Changes:
This release fixes a bug in Unicorn::HttpParser#filter_body
which affected some configurations of Rainbows! There is
also a minor size reduction in the DSO.
(this parser fix only affects Ruby 2.0.0 with Rainbows!)
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://b
Eric Wong wrote:
> I'm stumped that rb_str_modify() doesn't seem to help with
> rb_str_set_len() raising in the chunked parser. More info here:
>
> https://bugs.ruby-lang.org/issues/7957
>
> Any help would be appreciated... It's way past my bed time.
Oops, my
I'm stumped that rb_str_modify() doesn't seem to help with
rb_str_set_len() raising in the chunked parser. More info here:
https://bugs.ruby-lang.org/issues/7957
Any help would be appreciated... It's way past my bed time.
___
Unicorn mailing list - mon
Changes:
Unicorn::Const::UNICORN_VERSION is now auto-generated from
GIT-VERSION-GEN and always correct. Minor cleanups for
hijacking.
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://bogomips.org/unicorn.git
* http://unicorn.bogomips.org/NEWS.atom.xml
__
Jérémy Lecour wrote:
> Hi,
>
> I'm using Unicorn with rbenv to have different Ruby versions between projects.
>
> This morning, I wanted to change the Ruby version used by an app.
> I've updated the content of .ruby-version, then sent a USR2 signal to
> the master process to restart Unicorn (as
As far as I can tell, this was never necessary.
---
lib/unicorn/http_request.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/unicorn/http_request.rb b/lib/unicorn/http_request.rb
index 681c0ca..6b20431 100644
--- a/lib/unicorn/http_request.rb
+++ b/lib/unicorn/http_reque
I've pushed out a few minor changes to master, nothing major.
git clone git://bogomips.org/unicorn.git
Eric Wong (3):
auto-generate Unicorn::Const::UNICORN_VERSION
http_request: remove FIXME for rack.version clarification
http_request: drop conditional assignmen
commit a9474624a148fe58e0944664190b259787dcf51e in rack.git
---
lib/unicorn/http_request.rb | 3 ---
1 file changed, 3 deletions(-)
diff --git a/lib/unicorn/http_request.rb b/lib/unicorn/http_request.rb
index 3795b3b..681c0ca 100644
--- a/lib/unicorn/http_request.rb
+++ b/lib/unicorn/http_request
ng GIT-VERSION-GEN. This should work:
- 8< --
>From cb0623f25db7f06660e563e8e746bfe0ae5ba9c5 Mon Sep 17 00:00:00 2001
From: Eric Wong
Date: Fri, 8 Feb 2013 18:50:07 +
Subject: [PATCH] auto-generate Unicorn::Const::UNICORN_VERSION
This
Changes:
This pre-release adds hijacking support for Rack 1.5 users.
See Rack documentation for more information about hijacking.
There is also a new --no-default-middleware/-N option
for the `unicorn' command to ignore RACK_ENV within unicorn
thanks to Lin Jen-Shin.
There are only documentation
Anybody running 4.6.0pre1, yet? I'm tempted to release 4.6.0 soon.
I just pushed out a couple of *BSD-related test fixes ported
over from rainbows.git (@ git://bogomips.org/rainbows.git )
commit 9cd8554749a9f120b010c93933d09d2dd27b1280
Author: Eric Wong
Date: Mon Feb 4 12:39:09
-N/--no-default-middleware needs a corresponding manpage entry.
Additionally, the Rack::Chunked/ContentLength middleware comment
is out-of-date as of unicorn v4.1.0
---
Also just pushed this to master of git://bogomips.org/unicorn
commit 64765b95df06256d39daefdeebde97c874770131
Documentation
Installing from RubyGems.org: gem install --pre unicorn
>From db919d18e01f6b2339915cbd057fba9dc040988b Mon Sep 17 00:00:00 2001
From: Eric Wong
Date: Tue, 29 Jan 2013 21:02:55 +
Subject: [PATCH] unicorn 4.6.0pre1 - hijacking support
This pre-release adds hijacking support for Rack 1.5 us
Eric Wong wrote:
> Lin Jen-Shin wrote:
> > + opts.on("-N", "--no-default-middleware",
> > + "no default middleware even if RACK_ENV is development") do |e|
>
> RACK_ENV=deployment also loads middleware, so I think it's more accur
Lin Jen-Shin wrote:
> + opts.on("-N", "--no-default-middleware",
> + "no default middleware even if RACK_ENV is development") do |e|
RACK_ENV=deployment also loads middleware, so I think it's more accurate
with:
do not load middleware implied by RACK_ENV
This also puts us back
"Lin Jen-Shin (godfat)" wrote:
> And should I send patches for rainbows and zbatery as well?
Yes please, thanks!
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like
"Lin Jen-Shin (godfat)" wrote:
> On Sat, Jan 26, 2013 at 2:39 AM, Eric Wong wrote:
> > Doesn't Rails favor RAILS_ENV over RACK_ENV? unicorn ignores RAILS_ENV
> > (unicorn_rails respects RAILS_ENV, but unicorn_rails isn't recommended
> > for modern (Rac
"Lin Jen-Shin (godfat)" wrote:
> Hi,
>
> This might be a bit silly, but finally I decided to bring this up.
>
> We're running a Rails app along with another Rack app in
> the same config.ru, and what I want to do is telling Unicorn
> that we don't want any middleware which Unicorn might
> insert
Charles Hornberger wrote:
> On Mon, Jan 21, 2013 at 11:28 AM, Eric Wong wrote:
> > Charles Hornberger wrote:
> >> E, [2013-01-18T17:54:21.502915 #59285] ERROR -- : reaped
> >> # worker=1
> >> I, [2013-01-18T17:54:21.605077 #59285] INFO -- : master compl
t;check request hijack" && {
- test "xhijack.OK" = x"$(curl -sSfv http://$listen/hijack_req)"
+ test "xrequest.hijacked" = x"$(curl -sSfv http://$listen/hijack_req)"
}
t_begin "check response hijack" && {
--
Eric W
(moving to public list, since this pull request (and your email address)
was already public)
Daisuke Taniwaki wrote:
> Hi,
>
> I mistakenly send pull request to the mirror on github.
For public patches/pull-requests, please use the public mailing list in
the future. See the HACKING doc, subm
.23a9ee4
--- /dev/null
+++ b/t/t0200-rack-hijack.sh
@@ -0,0 +1,27 @@
+#!/bin/sh
+. ./test-lib.sh
+t_plan 5 "rack.hijack tests (Rack 1.5+ (Rack::VERSION >= [ 1,2]))"
+
+t_begin "setup and start" && {
+ unicorn_setup
+ unicorn -D -c $unicorn_config h
Charles Hornberger 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] INFO -- : reaped
> # worker=6
> I, [2013-01-18T17:54:21.502692 #59285] INFO
Avner Cohen wrote:
> Eric,
> Thanks for the quick reply, and aplogies for not providing full info.
> I do have these set up, here is my full configuration:
>
> # -*- encoding : utf-8 -*-
> worker_processes 4
> working_directory "."
> listen 3000
> timeout 120
>
> preload_app true
>
> before_for
Avner Cohen wrote:
> 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/is
In case you missed it, I responded to your original message:
http://mid.gmane.org/20130115194408.ga30...@dcvr.yhbt.net
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (
Manuel Palenciano Guerrero wrote:
> Hello there
>
> We use Unicorn in all of our production/staging web-apps, and we are
> very happy with it. But we also have one of the apps talking to a
> web-service via SOAP, and this web-service now takes longer than usual
> processing requests. To solve thi
Julian Dunn wrote:
> > I was trying to run Unicorn 4.5.0's tests and I'm getting this. Am I doing
> > something wrong?
> >
> > [vagrant@localhost unicorn-4.5.0]$ testrb -Ilib -Iext/unicorn_http -I. test
I'm not sure what testrb is doing, I never use it. I can reproduce
your error and it's not o
Owen Davies wrote:
> I cannot find any good example of a unicorn upstart task that works
> properly for the following:
>
> * Upstart will restart if unicorn dies
> * Can send USR2 signal to unicorn to do a no downtime deploys
I don't think you can combine the first two items.
Sending QUIT to th
! compatibility in 4.5.0pre1.
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://bogomips.org/unicorn.git
* http://unicorn.bogomips.org/NEWS.atom.xml
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http
Tony Arcieri wrote:
> Here's a quick followup with what we're going to try:
>
> We changed the before_fork/after_fork hooks, getting rid of the
> original before_fork hook which sent SIGQUIT to the old master.
> Instead, we send SIGTTOU to the old master at the very end of the
> after_fork block,
Mac Martine <99mi...@gmail.com> wrote:
> Thanks,
>
> I can install other gems just fine in the same way, so it doesn't seem
> like permissions then, right?
>
> And disk space looks ok:
That's good to know.
> Here's the end of mkmf.log
>
> have_macro: checking for SIZEOF_SIZE_T in ruby.h... ---
Mac Martine <99mi...@gmail.com> wrote:
> I'm deploying a Rails 3.2.8 app to Ubuntu. The server already runs the app
> with Unicorn and Nginx.
> unicorn -v returns unicorn v4.4.0
>
> Adn rvm gem list shows:
> unicorn (4.4.0)
>
> Yet when I manually run 'gem install unicorn '4.4.0' it fails with
Peter Hall wrote:
> Hi,
>
> I'm trying to use unicorn in a test deployment of a Rails app that
> uses Mongoid, so Activerecord isn't included in the app. When I start
> unicorn through Capistrano though, the stderr log fills up endlessly
> with identical ActiveRecord-related errors:
>
> I, [2012
Jerrold Thompson wrote:
> 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
Eric Wong wrote:
> I fixed up some minor line-wrapping, signed-off, and added your
> quote above to the commit message. Pushed as
> commit 5c700fc2cf398848ddcf71a2aa3f0f2a6563e87b
> to git://bogomips.org/unicorn.git
One more fix/cleanup to maintain compatibility with Rain
Tony Arcieri wrote:
> On Fri, Nov 30, 2012 at 2:27 PM, Eric Wong wrote:
> > I usually put that logic in the deployment script (probably just
> > with "curl -sf"), but a background thread would probably work.
>
> Are you doing something different than unicornct
Eric Wong wrote:
> Lawrence Pit wrote:
> > A related question: is it possible to get insight in what's in the
> > unicorn queue and for how long requests have been queued there?
> Using SystemTap (or similar solutions), I think the same information may
> be retri
Tony Arcieri wrote:
> On Thu, Nov 29, 2012 at 3:32 PM, Eric Wong wrote:
> > If the server is down to haproxy, but still up, you can send some warmup
> > requests to the server before enabling the monitor-uri for haproxy.
>
> I've heard various solutions for exactl
Yoav Aner wrote:
> I simply added `Logging.reopen` to the after_fork block and now it
> looks like it's working again!
Awesome to know.
> Not sure I still fully (or even partially) understand what's going on
> there, but at least it's working.
Reading a manpage for the fork() syscall should hel
Yoav Aner wrote:
> Hi Eric,
>
> Thanks a bunch for getting back so quickly on this.
>
> I followed your suggestion and tried with `preload_app = false` and looks
> like this seems to fix this problem! Any idea what can go wrong when it's
> set to true or how I can try go about fixing this??
pre
Andrew Stewart wrote:
> On 30 Nov 2012, at 00:04, Eric Wong wrote:
> > Iñaki Baz Castillo wrote:
> >> I don't understand why the application on top of the HTTP/TCP layer
> >> (so the Rails app) should be interrupted because the TCP connection is
> >>
Yoav Aner wrote:
> Hope this is the right place to ask questions about unicorn. I'm not
> on the mailing list though, so please CC my email address.
No problem!
> Since moving from phusion passenger to Unicorn, it seems like one
> functionality of the logging-rails gem
> (https://github.com/TwP/
Tony Arcieri wrote:
> On Thu, Nov 29, 2012 at 3:34 PM, Lawrence Pit wrote:
> >
> > Perhaps it's possible to warm up the workers in the unicorn after_fork
> > block?
>
> Are people doing this in production (i.e. moving the termination of
> the old master from before_fork to after_fork)? My worry
Just pushed out the RubyGem for this.
Changes:
The new check_client_connection option allows unicorn to detect
most disconnected clients before potentially expensive
application processing begins.
This feature is useful for applications experiencing spikes of
traffic leading to undesirable queue
Tony Arcieri wrote:
> 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 s
Iñaki Baz Castillo wrote:
> 2012/11/28 Andrew Stewart :
> > 1. Client clicks a delete link in my webapp.
> > 2. Rails starts processing the appropriate destroy action. This updates
> > various things in the database (but not in a single db transaction).
> > 3. Client terminates the connection.
>
tcp_nodelay:false.
---
Eric Wong wrote:
> Tom Burns wrote:
> > +if set[:check_client_connection]
> > + set[:listeners].each do |address|
> > +if set[:listener_opts][address][:tcp_nopush] == true
> > + raise ArgumentError,
> > +
Lawrence Pit wrote:
> >[2]
> >http://mid.gmane.org/cak4qkg32dggnbztzcb6noh5hu_drhmofafhk-6xvy-t86++...@mail.gmail.com
> >I haven't heard back on results of our nasty/crazy solution, though.
>
> fyi: I've been running that patch for a while in our staging
> environment. As far as I can tell it wo
Tom Burns wrote:
> +if set[:check_client_connection]
> + set[:listeners].each do |address|
> +if set[:listener_opts][address][:tcp_nopush] == true
> + raise ArgumentError,
> +"check_client_connection is incompatible with tcp_nopush:true"
> +end
Btw, w
Tom Burns wrote:
> So we just finished the US Black Friday / Cyber Monday weekend running
> unicorn forked with the last version of the patch I had sent you. It
> worked splendidly and helped us handle huge flash sales without
> increased response time over the weekend.
>
> Whereas in previous f
Andrew Stewart wrote:
> On 28 Nov 2012, at 22:10, Eric Wong wrote:
> > Yes. Using the Unicorn::PrereadInput middleware (before Rails or
> > any other middleware/framework touches env["rack.input"]) should do
> > everything you want.
>
> Excellent.
>
>
Andrew Stewart wrote:
> Hello,
>
> I have run into the following situation several times in the past few months:
>
> (My stack is Nginx -- Unicorn -- Rails 3.0.12)
>
> 1. Client clicks a delete link in my webapp.
> 2. Rails starts processing the appropriate destroy action. This updates
> vari
Petteri Räty wrote:
> On 27.11.2012 4.02, Eric Wong wrote:
> > Petteri Räty wrote:
> >> On 27.11.2012 2.35, Eric Wong wrote:
> >>>>
> >>>> nginx does not explicitly unlink the old pid file before it renames it
> >>>> out of th
Petteri Räty wrote:
> On 27.11.2012 2.35, Eric Wong wrote:
>
> >>
> >> nginx does not explicitly unlink the old pid file before it renames it
> >> out of the way so yes matching nginx in that regard changes the behavior
> >> exactly how I originally
Petteri Räty wrote:
> On 26.11.2012 20.24, Eric Wong wrote:
> >
> >> The use case here is that with health monitors wouldn't have a window
> >> where a pid file does not exist. With a hot restart it should always be
> >> possible to have a pid file
Petteri Räty wrote:
> On 26.11.2012 2.43, Eric Wong wrote:
> > Petteri Räty wrote:
> >> What follows are all the write actions related to unicorn pid file when
> >> doing a hot restart. Seems like a bug to me that unicorn is deleting the
> >> pid file bef
Petteri Räty wrote:
> What follows are all the write actions related to unicorn pid file when
> doing a hot restart. Seems like a bug to me that unicorn is deleting the
> pid file before writing the new file. Is there a reason for it? It seems
> to go against that rename that aims for an atomic re
101 - 200 of 866 matches
Mail list logo
