From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS33070 50.56.128.0/17 X-Spam-Status: No, score=0.0 required=5.0 tests=T_DKIM_INVALID shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 1D9971F704 for ; Wed, 5 Dec 2012 00:05:36 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2227A2E07A; Wed, 5 Dec 2012 00:05:37 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org X-Greylist: delayed 7649 seconds by postgrey-1.31 at rubyforge; Wed, 05 Dec 2012 00:05:27 UTC Received: from mail.whidbey.net (mailout.whidbey.net [209.166.65.36]) by rubyforge.org (Postfix) with ESMTP id AC9132E077 for ; Wed, 5 Dec 2012 00:05:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=whidbey.com; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=wcH9naU/og7SHx4bMEn9NHC/8L5838K37MoqaoC7dCs=; b=KJ1xdw2PAdSgTe6jn+Dq2I5O1NBaksNIpVaRpbN9INe2mQqjG6k69wJ34lfIeo7cuIQ1vTDl3npYYd8Zz2H+0H7LZdrZdo8GYYfhMb2nZtTE3Wx8Yiiu+tV5fWsluTLZk1VvPIQQSCu7gB7jkBrU+ted2Ap0vjmTl5Gl7mQunvE=; Received: from [67.158.203.183] (helo=[192.168.2.4]) by mail.whidbey.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1Tg0Yo-0006l3-DC for mongrel-unicorn@rubyforge.org; Tue, 04 Dec 2012 14:01:50 -0800 Message-ID: <50BE72CF.9050602@whidbey.com> Date: Tue, 04 Dec 2012 14:01:51 -0800 From: Jerrold Thompson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120724 Icedove/3.0.11 MIME-Version: 1.0 To: mongrel-unicorn@rubyforge.org Subject: Re: 403 Forbidden from nginx when unicorn started in debug mode References: <50BE71E2.6040504@whidbey.com> In-Reply-To: <50BE71E2.6040504@whidbey.com> X-BeenThere: mongrel-unicorn@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org ...in Gemfile: gem 'debugger', :git => 'git://github.com/cldwalker/debugger.git', :require => 'debugger' On 12/04/2012 01:57 PM, 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 up by nginx. > > Any ideas, or more information needed? > > Thanks! > > Jet > > Below is my unicorn.rb for developent: > > # config/unicorn.rb > > env = "development" > > preload_app true > > timeout 30 > > listen "/tmp/unicorn.sock", :backlog => 64 > > if env == 'development' > pid > "/home/jet/RailsApps/spree/aceleathergoods/tmp/pids/unicorn.aceleathergoods.pid" > > stderr_path "/var/www/aceleathergoods/shared/log/unicorn.stderr.log" > stdout_path "/var/www/aceleathergoods/shared/log/unicorn.stdout.log" > end > > > before_fork do |server, worker| > if defined?(ActiveRecord::Base) > ActiveRecord::Base.connection.disconnect! > end > > old_pid = "#{shared_path}/pids/unicorn.aceleathergoods.pid.oldbin" > if File.exists?(old_pid) && server.pid != old_pid > begin > Process.kill("QUIT", File.read(old_pid).to_i) > rescue Errno::ENOENT, Errno::ESRCH > # someone else did our job for us > end > end > end > > after_fork do |server, worker| > if defined?(ActiveRecord::Base) > ActiveRecord::Base.establish_connection > end > end > _______________________________________________ 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