unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Imdad <khanimdad@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public <unicorn-public@bogomips.org>
Subject: Re: Having issue with Unicorn
Date: Sat, 25 Oct 2014 00:11:38 +0530	[thread overview]
Message-ID: <CADQvUy75nS+tET1QDWB_YQ-1c+CDwYJkFE177vCvRbKW+Q-9zA@mail.gmail.com> (raw)
In-Reply-To: <CADQvUy7TedH_3NSX1rES3ueHSmnAMU-FsBCLMNBG8QaRS1hJmA@mail.gmail.com>

FYI - after deploy, config/unicorn.rb is already updated
app_dir = app_dir = "/var/www/hailisys/current"#File.expand_path('../../',
__FILE__)
shared_dir = "/var/www/hailisys/shared"


Cheers!
Imdad Ali Khan
Mob (0) 9818484057
http://www.linkedin.com/in/imdad

On 25 October 2014 00:09, Imdad <khanimdad@gmail.com> wrote:

> Thanks Eric, not how to do
>  2) SIGHUP master to reload new config # manual step to fix up config
>  3) proceed with SIGUSR2 as usual
>
> Also not sure how did i send HTML portions
>
> Cheers!
> Imdad Ali Khan
> Mob (0) 9818484057
> http://www.linkedin.com/in/imdad
>
> On 25 October 2014 00:04, Eric Wong <e@80x24.org> wrote:
>
>> Imdad <khanimdad@gmail.com> wrote:
>> > Updates app_dir and shared_dir as stated here then did a deploy which
>> went
>> > okay, but my app still not running and log spit the following...
>>
>> I think you need to SIGHUP the existing master before SIGUSR2:
>>
>>    1) update config/unicorn.rb on the server
>>    2) SIGHUP master to reload new config # manual step to fix up config
>>    3) proceed with SIGUSR2 as usual
>>
>> Also, please don't send HTML portions or quote too much,
>> it wastes bandwidth and storage.  Thanks.
>>
>
>


  reply	other threads:[~2014-10-24 18:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 17:33 Having issue with Unicorn Imdad
2014-10-24 17:45 ` Eric Wong
2014-10-24 18:02   ` Imdad
2014-10-24 18:13     ` Eric Wong
2014-10-24 18:28       ` Imdad
2014-10-24 18:34         ` Eric Wong
2014-10-24 18:39           ` Imdad
2014-10-24 18:41             ` Imdad [this message]
2014-10-24 19:13             ` Eric Wong
2014-10-24 19:29               ` Imdad
2014-10-24 19:41                 ` Eric Wong
2014-10-24 19:58                   ` Imdad
2014-10-24 20:06                     ` Eric Wong
2014-10-24 20:09                       ` Imdad
2014-10-24 20:17                         ` Eric Wong
2014-10-24 20:35                           ` Imdad
2014-10-24 20:39                             ` Imdad
2014-10-24 20:44                               ` Eric Wong
2014-10-24 20:40                             ` Eric Wong
2014-10-24 20:45                               ` Imdad
2014-10-24 20:50                                 ` Imdad
2014-10-24 20:58                                 ` Eric Wong
2014-10-24 21:24                                   ` Imdad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADQvUy75nS+tET1QDWB_YQ-1c+CDwYJkFE177vCvRbKW+Q-9zA@mail.gmail.com \
    --to=khanimdad@gmail.com \
    --cc=e@80x24.org \
    --cc=unicorn-public@bogomips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).