Patrick J. Collins patr...@collinatorstudios.com wrote:
You shouldn't even need the logger directive, it goes to stderr by
default so your console will still show it.
Hmm that's odd because I noticed as soon as I began using unicorn that I got
very little output. For example, running my
Lucas Parry lu...@envato.com wrote:
On Fri, Feb 17, 2012 at 1:29 PM, Lucas Parry lu...@envato.com wrote:
We recently made the switch to 1.9 for our large rails 2.3.14 project
(odd, neither I nor gmane got your original message:
Eric Wong normalper...@yhbt.net wrote:
ruby-core pointed me to the following issue:
https://bugs.ruby-lang.org/issues/5757
So there may already be a fix in Ruby SVN, can you test?
http://svn.ruby-lang.org/repos/ruby/branches/ruby_1_9_3 r34425
Btw, did anybody get a chance to try
Dmytrii Nagirniak dna...@gmail.com wrote:
I wonder how do you deploy Unicorn Rails apps using Foreman and the upstart.
The things I'm not sure how to deal with are:
- restarting the Unicorn with no downtime. With upstart I think the master
process gets restarted.
I'll defer to actual
Eric Wong normalper...@yhbt.net wrote:
A total stab in the dark, but I posted this patch to ruby-core anyways
to find more testers/reviewers:
http://mid.gmane.org/20120202221946.ga32...@dcvr.yhbt.net
Oops, and I just posted a follow-up since the original was a no-op
due to ordering issues
Eric Wong normalper...@yhbt.net wrote:
Can you report this as a bug to the Ruby core folks on
https://bugs.ruby-lang.org/ and also to whereever the FreeBSD hackers
take bug reports? Somebody from one of those camps should be able
to resolve the issue.
A total stab in the dark, but I posted
Eric Wong normalper...@yhbt.net wrote:
A total stab in the dark, but I posted this patch to ruby-core anyways
to find more testers/reviewers:
Last attempt at a patch on this issue, I'm just shotgunning here :x
http://bogomips.org/ruby.git/patch/?id=418827f4e41a618d91
ruby-core pointed me to the following issue:
https://bugs.ruby-lang.org/issues/5757
So there may already be a fix in Ruby SVN, can you test?
http://svn.ruby-lang.org/repos/ruby/branches/ruby_1_9_3 r34425
___
Unicorn mailing list -
Philipp Bruell philipp.bru...@skrill.com wrote:
First of all, thank you for your fast reply.
No problem, depends on the time of day of course :
The behaviour details Charles described are correct and we are using ruby
version 1.9.3.
It's good that you've asked for the other signals. I've
Eric Wong normalper...@yhbt.net wrote:
This isn't a project which targets 20 year-old i486 systems, so
s/, so/, where/
upgrading the distro/compiler is extremely time-consuming and
nearly impossible for some folks.
___
Unicorn mailing list - mongrel
Do you guys (or know of any users) stuck on Ruby 1.8.5 or earlier?
I know some users on RHEL/CentOS 5 have 1.8.5 installed as /usr/bin/ruby
by default and RHEL/CentOS 5.x will continue to be deployed for many
years to come. This is the unfortunate reality of distributions with
long-term support
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/41916
This means you can run more Unicorn worker processes per-host
if you have CPU for it :
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Troex Nevelin l...@mrtech.ru wrote:
Hello,
I have a simillar problem that started after update, 3 days ago we
moved from REE 1.8 / Rails 2 to Ruby 1.9.3 and Rails 3.1, also we
replaced memcached with redis so this is huge update and there are
many places where we can have an issue.
I
Laurens Pit laurens@mirror42.com wrote:
I didn't expect that to be the case, but in the past year occasionally
I've experienced I had to resort to QUIT and start all over in order
to get all components loaded correctly.
Specifically: yesterday I upgraded several projects to rails 3.0.11
Lawrence Pit lawrence@gmail.com wrote:
Bundler has been updated several times this year, I guess every time
that happens and a new version gets installed a complete restart of
unicorn is required? Am I the only one seeing this?
Managing bunder has always been tricky, unfortunately.
Jeremy Evans jeremyeva...@gmail.com wrote:
On Tue, Nov 15, 2011 at 4:17 AM, Eric Wong normalper...@yhbt.net wrote:
I usually prefer to work on each problem, one-at-a-time. However,
GNU make already has a handy -k/--keep-going flag to ignore failures.
Thanks, I didn't know about
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
Jeremy Evans jeremyeva...@gmail.com wrote:
On Mon, Nov 14, 2011 at 9:54 PM, Eric Wong normalper...@yhbt.net wrote:
Jeremy Evans jeremyeva...@gmail.com wrote:
This is obviously not a permanent fix, but I'm not sure why the tests
are hanging, and hanging during a test is bad. I suppose you
Xavier Noria f...@hashref.com wrote:
Hey, I have this pretty standard init script for Unicorn
http://pastie.org/2840779
where
fxn@cohen:~$ ls -la /etc/init.d/unicorn_home
lrwxrwxrwx 1 root root 32 2011-11-09 23:45 /etc/init.d/unicorn_home
- /home/fxn/home/config/unicorn.sh
Ben Somers somers@gmail.com wrote:
m1.xlarge running Ubuntu 9.10 (yes, we know it's out od date), with
15GB RAM, 4x2GHz CPU.
The server is behaving fine, with most of the unicorn workers sitting
at about 280MB resident memory, comparable to passenger's workers. But
I've been testing how
Marcin Stecki madshee...@gmail.com wrote:
In my ror 3.0.10 app Unicorn somehow causes my application to show
errors on staging like it was development environment (with backtrace
and everything) instead of sending them to hoptoad. This is strange -
same app on mongrel shows custom 500 page and
Pai-Hung Chen paihungc...@hotmail.com wrote:
On 10/10/2011 08:04 AM, Devin Ben-Hur wrote:
My question is: By the time the before_exec hook is executed, is it
guaranteed that unicorn.pid.oldbin ahas lready created (otherwise we
have a racing condition here)? Or is there a better way to
Tatsuya Ono onon...@gmail.com wrote:
I don't actually understand is why GC.disable solution could introduce
more memory leak. If I simplify the problem, the code is something
like bellow:
---
GC.disable
(do something)
GC.enable
GC.start
---
When the code block
(please don't send the same message twice in a short time period)
Andrey Cherkashin andor...@gmail.com wrote:
I have a problem with unicorn and signals.
FreeBSD freebsd 9.0-BETA3 FreeBSD 9.0-BETA3 #0 r225816+a1b6562: Thu Sep 29
06:46:06 PDT 2011 root@freebsd:/sys/i386/compile/XEN i386
---
- config.ru --
if ($unicorn_worker_nr % 2) == 0
run FooApp.new
else
run BarApp.new
end
--- 8 ---
--
Eric Wong
___
Unicorn
John Joseph Bachir j...@jjb.cc wrote:
So buffering the entire request and then sending it to the backend is
the default behavior of HttpUpstreamModule? That's fascinating. It
almost seems like that's a bad design choice, because it inhibits the
possibility of parallel work being done as the
John Joseph Bachir j...@jjb.cc wrote:
My application accepts uploads from users, which can be quite huge in
some cases. This of course requires setting the unicorn timeout to
something much higher than 60 seconds, more like 10 minutes.
Are there any drawbacks to doing this, other than the
Alex Sharp ajsh...@gmail.com wrote:
Would there be any support for a worker-level timeout callback, for
workers that get killed by the master process for violating the
Unicorn::Configurator.timeout setting?
Something like this /cannot/ be done right. The unicorn timeout uses
SIGKILL
for Unicorn, it fails with that message.
Maybe Passenger is more lenient with the Rack specs and/or working
around bugs.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote
be root to signal the
process anyway, but I'll cross that particular bridge when I come to
it!
Yeah, there's no point in knowing it unless you can send signals to it.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http
russell muetzelfeldt russm-rubyfo...@slofith.org wrote:
On 16/09/2011, at 9:11 PM, Eric Wong wrote:
:ThreadSpawn + worker_connections=1 and the (default) :Base option are
almost the same in Rainbows! if you don't want to worry about your app
being thread-safe at all.
snip
I passed
lib/unicorn/ssl_configurator.rb
create mode 100644 lib/unicorn/ssl_server.rb
create mode 100755 t/sslgen.sh
create mode 100755 t/t0600-https-server-basic.sh
create mode 100644 test/unit/test_sni_hostnames.rb
--
Eric Wong
___
Unicorn mailing list
Brian P O'Rourke b...@somnambulance.net wrote:
You can just pull from my public fork here:
git://github.com/bpo/unicorn.git - branch name is
'daemonization_detection'
Acked and pushed out as commit b48c6659b294b37f2c6ff3e75c1c9245522d48d1
Thanks!
___
setup.
Also, I don't subscribe to this list; please reply to my e-mail
address as well.
Thanks for the heads up :)
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do
://bogomips.org/unicorn.git
Please review the code/tests if you have a chance, thanks for reading!
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like
Alex Sharp ajsh...@gmail.com wrote:
On Tuesday, August 30, 2011 at 5:33 PM, Eric Wong wrote:
Eric Wong normalper...@yhbt.net (mailto:normalper...@yhbt.net) wrote:
+ trap(sig) do
+ @logger.debug(received SIG#{sig})
I'm even more glad I didn't apply this patch to Unicorn. I completely
Eric Wong normalper...@yhbt.net wrote:
+ trap(sig) do
+@logger.debug(received SIG#{sig})
I'm even more glad I didn't apply this patch to Unicorn. I completely
forgot Logger uses a mutex internally (even though it doesn't need to
when writing to a POSIX-compliant file system
Eric Wong normalper...@yhbt.net wrote:
I think it's safe to proceed with adding GPLv3 to Unicorn...
(GPLv2 and Ruby license terms will remain options, too)
Pushed out: http://bogomips.org/unicorn.git/patch/?id=cd22c59563
___
Unicorn mailing list
to discourage the reliance on this last-resort
mechanism. It is visible on the web at:
http://unicorn.bogomips.org/Application_Timeouts.html
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://bogomips.org/unicorn.git
* http://unicorn.bogomips.org/NEWS.atom.xml
--
Eric Wong
] mechanism
+in \Unicorn is an extreme solution that should be avoided whenever
+possible. It will help catch bugs in your application where and when
+your application forgets to use timeouts, but it is expensive as it
+kills and respawns a worker process.
--
Eric Wong
with no extra gems?
--
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
Alex Sharp ajsh...@gmail.com wrote:
On Tuesday, August 23, 2011 at 12:12 AM, Eric Wong wrote:
So this was with preload_app=true? While you're debugging problems,
I suggest keeping preload_app=false and worker_problems=1 to minimize
the variables.
Ok, I'll change those and report back. I'm
Eric Wong normalper...@yhbt.net wrote:
I would like to add the GPLv3 to the existing Unicorn license, making it
(Ruby terms|GPLv2|GPLv3). Furthermore, I'd like the project leader of
Unicorn (currently me) to be given the option to add future versions of
the GPL (as published by the Free
Eric Wong normalper...@yhbt.net wrote:
clift...@gmail.com wrote:
On Aug 19, 2011, at 5:46 PM, Alex Sharp wrote:
The exception message I get is: Mongo::ConnectionFailure: Failed to
connect to host xxx.yyy.zzz.com and port 12345: Interrupted system
call - connect(2)
I've been
Alex Sharp ajsh...@gmail.com wrote:
On Thu, Aug 18, 2011 at 6:53 PM, Eric Wong normalper...@yhbt.net wrote:
Basically anything you can tell use about the app, the configuration,
and which gems/libraries would be useful.
Gemfile: https://gist.github.com/05a9445471ad7edfdcb7
OK, out
-fot4u-fbzt2diqfndyn4...@mail.gmail.com
2b157204-e5c6-4f5d-98a9-e2a79f9f9...@christophsturm.com
From 1077961a3f8933c65d39c7e6c9ed6ff3b6b53647 Mon Sep 17 00:00:00 2001
From: Eric Wong normalper...@yhbt.net
Date: Fri, 19 Aug 2011 20:47:29 +
Subject: [PATCH] Rack::Chunked and ContentLength
Eric Wong normalper...@yhbt.net wrote:
Eric Wong normalper...@yhbt.net wrote:
If you SIGQUIT/SIGTERM before the app is loaded, the signal could
be ignored. This behavior should probably change...
I pushed the following to git://bogomips.org/unicorn
From
I've seen this happen before with
Net::HTTP. I'll try to locate that error.
This is a bug in fixed in Ruby 1.9.2-p290 (r31829 in the ruby_1_9_2 branch)
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
fail with
EINTR, and buggy libraries don't handle it properly.
The Ruby standard library is mostly good at gracefully handling EINTR,
and I've gotten all instances I've encountered fixed in MRI 1.9.x.
--
Eric Wong
___
Unicorn mailing list - mongrel
...
--
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
Alex Sharp ajsh...@gmail.com wrote:
On Fri, Aug 5, 2011 at 1:07 AM, Eric Wong normalper...@yhbt.net wrote:
Can I get more? (until the next select() call, at least). I'd like to
see the timeout argument that gets passed to the next select().
Here's some more output. This is from the old
]
end
end
- config.ru -
use LogBefore
use ...
use ...
use ...
run YourApp.new
-
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do
Eric Wong normalper...@yhbt.net wrote:
The the rest of the app should have local timeouts for all
non-deterministic calls.
If you're lazy, maybe the following middleware works, too, I haven't
ever needed it but wrote (and later rewrote it) as a proof-of-concept:
http://bogomips.org
Eric Wong normalper...@yhbt.net wrote:
Below is a proposed patch (to unicorn.git) which may help debug issues
in the signal - handler master path (but only once it enters the Ruby
runtime). I'm a hesitant to commit it since it worthless if the Ruby
process is stuck because of some bad C
/ - configurable logger for Rack
--
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
? (WEBrick/Passenger/Thin/...).
[1] - Sure it seems to favor non-Free operating systems and services,
too, but I draw the line there. I am a after all a
Free Software-only hippie :
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
experience with this, I don't rely on
non-Free APIs or services like new relic, ever.
--
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
(rack/lint.rb line 56).
Do you happen to have any middlewares that might rewrite REQUEST_METHOD?
I would edit rack/lint.rb and put some print statements to show the
value of @head_request and env[REQUEST_METHOD]
--
Eric Wong
___
Unicorn mailing list
(http://wiki.nginx.org/HttpProxyModule#proxy_ignore_client_abort) so
that requests that make it to the Rails
app aren't aborted. Does anyone have experience with this? I can see it
causing its own sorts of confusion.
I've never used it.
--
Eric Wong
/20110808192824.ga5...@dcvr.yhbt.net
--
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
Thanks! I've pushed out the following patch and updated the site:
From ec8a8f32d257290aac377f1c7b1c496e1df75f73 Mon Sep 17 00:00:00 2001
From: Eric Wong normalper...@yhbt.net
Date: Wed, 3 Aug 2011 11:00:28 -0700
Subject: [PATCH] KNOWN_ISSUES: add link to FreeBSD jail workaround notes
Thanks
config:
https://gist.github.com/0dd07c5ad00c56d161c7
Avoid the top piece of the before_fork hook to TTOU workers, it's
needlessly complex for most deployments unless you're really
memory-constrained.
--
Eric Wong
___
Unicorn mailing list - mongrel
?
--
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
James Cox ja...@imaj.es wrote:
On Tue, Aug 2, 2011 at 17:53, Eric Wong normalper...@yhbt.net wrote:
James Cox ja...@imaj.es wrote:
Hey,
So here are some tasks for managing unicorn:
https://gist.github.com/1121076
Can we ignore the :restart task? It's a bit fragile since
Eric Wong normalper...@yhbt.net wrote:
If you SIGQUIT/SIGTERM before the app is loaded, the signal could
be ignored. This behavior should probably change...
I pushed the following to git://bogomips.org/unicorn
From 406b8b0e2ed6e5be34d8ec3cd4b16048233c2856 Mon Sep 17 00:00:00 2001
From: Eric
on this list
is...
--
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
the purpose of bundler...
Please add me in the CC replies, I am not subscribed to the newsletter.
Thanks for making a note of this :
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel
Eric Wong normalper...@yhbt.net wrote:
Would anybody be negatively affected by this change? I've been seeing
\x00 bytes in HTTP headers from clients and would rather stop those
clients earlier rather than later.
Pushed out with tests to git://bogomips.org/unicorn.git
Would anybody be negatively affected by this change? I've been seeing
\x00 bytes in HTTP headers from clients and would rather stop those
clients earlier rather than later.
From 4a8ddcd017a75b9bc99190dc565880615709d810 Mon Sep 17 00:00:00 2001
From: Eric Wong normalper...@yhbt.net
Date: Tue, 12
components you use.
--
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
was using preload_app, but seems to have fixed it by reverting to
an older Unicorn (3.7.0, he was on 4.0.0, so you seem to be hitting a
a different problem).
ref: http://mid.gmane.org/20110630194515.ga29...@dcvr.yhbt.net
--
Eric Wong
___
Unicorn mailing
/gmane.comp.lang.ruby.rainbows.general/229
Keep in mind nobody I know of uses Rainbows! in production; but
it /should/ be able to work without nginx (or any proxy).
7) Should we go with nginx or apache? (Opinions ok.)
nginx remains the only supported reverse proxy for Unicorn at this
moment.
--
Eric Wong
Apache mpm_prefork + (mod_php|mod_perl) users to
put nginx in front of their apps regardless of what benchmarks
were saying: http://bogomips.org/david.git
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
strace (Linux) or equivalent on the master process.
Unicorn's log file is completely empty.
This is the log you setup to point to stderr_path? That shouldn't
happen...
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http
if I'm
using clogger.
--
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
Eric Wong normalper...@yhbt.net wrote:
Tiago Scolari tscol...@gmail.com wrote:
Any idea what could cause this?
Are you using preload_app?
(private response said yes)
vendor/plugins/rpm/lib/new_relic/agent/instrumentation/unicorn_instrumentation.rb:7:in
`call'
Hrm, I wonder
Author: Eric Wong normalper...@yhbt.net
Date: Wed Jun 29 07:19:32 2011 +
fix per-worker listen directive in after_fork hook
The testcase for this was broken, too, so we didn't notice
this :
Reported-by: gha...@gmail.com on the Rainbows! mailing list,
http
://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://bogomips.org/unicorn.git
--
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
faster.
[2] http://redmine.ruby-lang.org/issues/3905
Thanks for reading!
--
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
/http_server.rb:475:in
`spawn_missing_workers'
It might be worth it to try unicorn 3.7.0 since 4.0.0 was just released
and some gems that depend on internal implementation details could
be broken.
Maybe somebody else here has a better explanation...
--
Eric Wong
Aleksandar Simic asi...@gmail.com wrote:
just to report back that this does fix the issue.
Thanks for the confirmation! Just released raindrops 0.7.0:
http://mid.gmane.org/20110627073050.gb15...@dcvr.yhbt.net
--
Eric Wong
___
Unicorn mailing list
@rubyforge.org
* git://bogomips.org/unicorn.git
--
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
it.
--
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
to an upstream if it's still writing one
30.times { s.write(req) }
# don't read the response, or read it slowly, just keep the socket
# open here...
sleep
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org
Eric Wong normalper...@yhbt.net wrote:
The subset of raindrops used by Unicorn should work on all machines
with mmap(2) + MAP_ANON/MAP_ANONYMOUS support, so *BSDs shouldn't be
left out.
I've had one report from a FreeBSD 8 user who couldn't get raindrops
to build. I remember getting
Jeremy Evans jeremyeva...@gmail.com wrote:
On Fri, Jun 24, 2011 at 10:30 AM, Eric Wong normalper...@yhbt.net wrote:
Eric Wong normalper...@yhbt.net wrote:
The subset of raindrops used by Unicorn should work on all machines
with mmap(2) + MAP_ANON/MAP_ANONYMOUS support, so *BSDs shouldn't
.
If the below patch doesn't fix it, yes, it'd be greatly appreciated,
thanks!
From 1e7dc89cc38c5dec0b63ac452b23141297701f88 Mon Sep 17 00:00:00 2001
From: Eric Wong normalper...@yhbt.net
Date: Fri, 24 Jun 2011 17:06:56 -0700
Subject: [PATCH] remove _XOPEN_SOURCE #define for FreeBSD
This appears to cause
whatever the Rails v2.3.8..v2.3.11 upgrade broke
in your app, but whatever's broken is broken at the application layer
and not in Unicorn.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel
/cgi_wrapper.rb
The code that does this transformation of the Rack header to the
client socket is here:
http://bogomips.org/unicorn.git/tree/lib/unicorn/http_response.rb
cgi_wrapper.rb is only for Rails = 2.2, where it is called before
http_response.rb
--
Eric Wong
:
e0eb8e9c65ededce64169948d4dd51b0079cdd10
85b6d79d8a17fdef667770e31b44ac6647f8b584
--
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
looked for things that
would manipulate cookies/headers.
--
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
)
With:
Unicorn::HttpServer.new(app, options).start.join
This will be in the upcoming 4.x release.
ref: git://bogomips.org/unicorn.git
commit 5d2284afdc2d4f4ff122394ae5fd78a32cb8c09e
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://bogomips.org/unicorn.git
--
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
Hongli Lai hon...@phusion.nl wrote:
On Mon, Jun 6, 2011 at 7:51 PM, Eric Wong normalper...@yhbt.net wrote:
Oops, this was a regression introduced when I switched to wrongdoc
in f62ef19a4aa3d3e4ce1aa37a499907ff776a8964
Perhaps this is better? It'll also affect the tgz target
addresses in $remote_addr (e.g ::10.0.0.1
# instead of just 10.0.0.1) and potentially trigger bugs in
# some software.
# listen [::]:80 ipv6only=on; # deferred or accept_filter recommended
--
Eric Wong
___
Unicorn mailing list - mongrel
Eric Wong normalper...@yhbt.net wrote:
Unicorn itself supports IPv6, too, but nobody uses/needs it.
I'll add :ipv6only support shortly (probably tomorrow).
Pushed to unicorn.git (c3880bb0cc00821d1715a7dd94b0b76a03a7ace0)
Documentation below:
diff --git a/lib/unicorn/configurator.rb b/lib
easily).
--
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
$@+
cmp $@+ $@ || mv $@+ $@
--
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
or Ruby trunk? Or maybe a different version of
glibc, too. Do you have any non-standard kernel patches/scheduler
configs?
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do
not sure.
The kernel does all the work for balancing.
--
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
201 - 300 of 466 matches
Mail list logo
