unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Emmanuel Gomez <emmanuel.gomez@gmail.com>
Subject: Re: Struggling with logrotate and unicorn
Date: Tue, 12 Apr 2011 17:58:55 +0000	[thread overview]
Message-ID: <20110412175855.GA21250@dcvr.yhbt.net> (raw)
In-Reply-To: <8A1F87B7-F4A6-4186-AE22-604F875C7F29@gmail.com>

Emmanuel Gomez <emmanuel.gomez@gmail.com> wrote:
> I have confirmed that logrotate creates the logs with a 0600 umask and
> the uid/gid of my unprivileged user (per my logrotate config, loosely
> based on the example logrotate.conf from 3.4 or 3.5). 

Did the permissions of the old (rotated) log files change?

> The problem occurs when I send a USR1 signal to the master process (as
> root, because the master is running as root) after the logs have been
> rotated. As near as I can tell, after that the Unicorn master chowns
> the logs to root ownership. Then, the workers attempt to chown the
> logs back to ownership by the unprivileged user, which repeatedly
> fails, spewing megabytes of errors that look like:

The rotation error handling should probably just exit! the worker
and rely on the master to restart it...

Eric Wong
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2011-04-12 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 16:13 Struggling with logrotate and unicorn Emmanuel Gomez
2011-04-12 17:58 ` Eric Wong [this message]
2011-04-12 18:36   ` Emmanuel Gomez
2011-04-12 18:59     ` Eric Wong
2011-04-12 22:38       ` Emmanuel Gomez
2011-04-12 22:51         ` Eric Wong
2011-04-12 23:01           ` Emmanuel Gomez

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:

  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=20110412175855.GA21250@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=emmanuel.gomez@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \


* 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


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).