Displaying 20 results from an estimated 6000 matches similar to: "A barrage of unexplained timeouts"
2010 Dec 01
14
Unicorn and HAProxy, 500 Internal errors after checks
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
2011 Aug 12
16
Rack content-length Rack::Lint::LintErrors errors with unicorn
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
2011 Jan 13
5
Unicorn 3.3.1 "Too many open files" error in kgio_tryaccept
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
2011 Nov 14
3
nginx + unicorn deployment survey
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
2009 Feb 11
16
Unicorn: UNIX+localhost/LAN-only Mongrel fork
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,
2010 Oct 22
4
502 bad gateway on nginx with recv() failed
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
2013 Apr 25
4
Why doesn't SIGTERM quit gracefully?
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
2010 Jan 09
8
X-Forwarded-Proto / X_FORWARDED_PROTO
Eric,
think I came across an issue with the parser in unicorn, with a request
(due to 2 layers of nginx proxying) coming across with both a
X_FORWARDED_PROTO and a X-Forwarded-Proto header. From the socket (in
HttpRequest) - we get:
X_FORWARDED_PROTO: http
X-Forwarded-Proto: https
which is parsed to
HTTP_X_FORWARDED_PROTO"=>"http,https
There was a passenger ticket that
2009 Nov 04
7
About Unicorn Rack handler
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:
2012 Apr 27
14
app error: Socket is not connected (Errno::ENOTCONN)
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
2012 Nov 29
13
Fwd: Maintaining capacity during deploys
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
2011 Jun 07
2
[PATCH] examples/nginx.conf: add ipv6only comment
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
2011 Aug 16
6
Unicorn logging in production env
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
2009 Oct 13
7
Unicorn Nginx Issue
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
2013 Jan 29
2
unicorn 4.6.0pre1 - hijacking support!
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.
2010 May 06
5
Garbage collection outside of request cycle?
I''ve been analyzing our Unicorn-powered Rails app''s performance, and have found that garbage collection is a big factor in slow requests.
In the interest of avoiding those performance hits while handling requests, would it be possible to have a unicorn worker run garbage collection after handling a request and before waiting for the next one? Would this be a good idea?
Cheers,
2010 Nov 20
6
unicorn 3.0.0 - disable rewindable input!
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
2012 Apr 12
8
Background jobs with #fork
Hi
I''ve migrated from Passenger to Unicorn about a week ago. It''s great.
Great transparency and management, thanks for this great software!
A few of my Rails applications start background jobs using
Kernel#fork. Of course, the ActiveRecord connections are closed and
reopened again in the parent and child processes. The child process
also does its job.
Unfortunately, it seems
2010 Jun 02
8
Read error: #<TypeError: can't modify frozen string> raised from HttpParser
Hey guys,
Started running unicorn in a production server like two weeks ago.
It''s been running smoothly, but looking at the logs found 44
exceptions like this:
E, [2010-06-02T16:17:15.117071 #22680] ERROR -- : Read error:
#<TypeError: can''t modify frozen string>
E, [2010-06-02T16:17:15.117270 #22680] ERROR -- :
2012 Feb 29
2
[PATCH] Start the server if another user has a PID matching our stale pidfile.
If unicorn doesn''t get terminated cleanly (for example if the machine
has its power interrupted) and the pid in the pidfile gets used by
another process, the current unicorn code will exit and not start a
server. This tiny patch fixes that behaviour.
---
lib/unicorn/http_server.rb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/unicorn/http_server.rb