ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:93886] [Ruby master Bug#10965] logger.rb may not daily rotate
Date: Tue, 23 Jul 2019 15:09:34 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-79866.20190723150934.b3bcfa66cbadb23c@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-10965.20150311110924@ruby-lang.org

Issue #10965 has been updated by hsbt (Hiroshi SHIBATA).

Assignee changed from nahi (Hiroshi Nakamura) to sonots (Naotoshi Seo)
Status changed from Open to Assigned
Description updated

----------------------------------------
Bug #10965: logger.rb may not daily rotate
https://bugs.ruby-lang.org/issues/10965#change-79866

* Author: leiting (Lei Ting)
* Status: Assigned
* Priority: Normal
* Assignee: sonots (Naotoshi Seo)
* Target version: 
* ruby -v: 2.0.0-p353
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
We have had a ruby game server running using logger.rb to log into daily rotated log files.

For test it's all ok, but when put on production, sometimes the log files don't rotate daily.

When one day passed, the logger still write to yesterday's log file.

When looking at the source code, I found the following in logger.rb:

```
    def write(message)
      begin
        @mutex.synchronize do
          if @shift_age and @dev.respond_to?(:stat)
            begin
              check_shift_log
            rescue
              warn("log shifting failed. #{$!}")
            end
          end
          begin
            @dev.write(message)
          rescue
            warn("log writing failed. #{$!}")
          end
        end
      rescue Exception => ignored
        warn("log writing failed. #{ignored}")
      end
    end
```

```
# The following running sequence for two write() may bring up the bug:

# now is 03/11 23:59:59
check_shift_log

# scheduling happens
# now is 03/12 00:00:00
@dev.write(message)

# @dev.write is buffered (correct me if I'm wrong)
# we can assume after write, @dev.stat.mtime becomes 03/12 00:00:01
# now is 03/12 00:00:01, but @dev.stat.mtime > period_end (which is 03/11 23:59:59)
check_shift_log

# now is 03/12 00:00:01
# will write to yesterday's log file
@dev.write(message)

# Both scheduling and buffered write can cause check_shift_log to fail when the log file should be rotated.
```



-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2019-07-23 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-10965.20150311110924@ruby-lang.org>
2015-03-11 11:09 ` [ruby-core:68498] [Ruby trunk - Bug #10965] [Open] logger.rb may not daily rotate leiting
2019-07-23 15:09 ` hsbt [this message]
2019-08-17  4:01 ` [ruby-core:94399] [Ruby master Bug#10965] " sonots

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-list from there: mbox

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

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

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

  git send-email \
    --in-reply-to=redmine.journal-79866.20190723150934.b3bcfa66cbadb23c@ruby-lang.org \
    --to=ruby-core@ruby-lang.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.
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).