Question

如今只有以下几条被贴上<代码>logs/delayed_job.log/code>:

2012-04-20T03:57:44+0000: Cacher completed after 5.3676
2012-04-20T03:57:44+0000: 1 jobs processed at 0.1744 j/s, 0 failed ...

我想要做的是,它也要记录所有我的<代码>put。我的问询,以及我的问询,如同在发展模式中所做的一样,但依然贴在<代码>log/delayed_job.log上。

我试图在<条码>上添加以下内容:初始用户/延迟_job_config.rb但无uck:

Delayed::Worker.logger = Rails.logger
Delayed::Worker.logger.level = Logger::DEBUG

(所有我<代码>puts) 如今已经停下来,但不再有工作身份记录,也没有问询。

Answer 1

可通过以下链接:。

UPDATED:a 略多一点。 v.slogger:

I am not sure what your implementation of making "puts" result stored into log file. however I think it could be a much better choice to ALWAYS use "logger" instead of "puts". the reasons are:

在大多数情况下,<代码>puts 能够放慢其业绩(特别是在生产环境中,在我以往的所有项目中,puts不允许出现在源代码中)(对于java方案管理员,Systemout.println <> 是相同的障碍)

总是使用<代码>logger,因为它有5个违约水平:衰减、焚烧、油、错误、致命,可以通过<代码>grep等工具加以控制和简化。 e.g. 可查阅puts a. 生产以下的标识:

07:27:48 INFO: in device_resource, options: [email protected] 07:27:48 INFO: cloudset: ??100

Answer 2

在铁路公司诉3.2.13案中,你可以:

Delayed::Worker.logger = ActiveSupport::Logger.new("log/delayed_job.log", Rails.logger.level)
Delayed::Worker.logger.auto_flushing = 1

#only reassign AR logger if we re in a delayed process(rake task or script/delayed_job)
if caller.last =~ /script/delayed_job/ or (File.basename($0) == "rake" and ARGV[0] =~ /jobs:work/)
  ActiveRecord::Base.logger = Delayed::Worker.logger
end

但... 主动支持:正在对以下项目进行折旧:

此外,你可能希望轮换你的标识? 因此,我认为这更好:

Delayed::Worker.logger = Logger.new("log/delayed_job.log", 5, 104857600)

if caller.last =~ /script/delayed_job/ or (File.basename($0) == "rake" and ARGV[0] =~ /jobs:work/)
  ActiveRecord::Base.logger = Delayed::Worker.logger
end

The constructor says keep around 5 log files and rotate when the current log file hits 100Mb. See here for details: http://www.ruby-doc.org/stdlib-1.9.3/libdoc/logger/rdoc/Logger.html#method-c-new

Credit to: http://www.heedspin.com/2011/01/17/delayed-job-logging.html for the inspiration

Answer 3

这对被占领土来说可能是很晚的,但这里采取不同的做法:使用一种拖延的焦布金来设定铁路(和活性记录:底线)与被指派给工人的木.。

两个步骤:在您的推迟工作初始者中:

require  delayed_job_log_setup 
Delayed::Worker.plugins << DelayedJobLogSetup

原始材料本身(我显然在校准/推迟_job_log_setup.rb):

require  delayed_job 

class DelayedJobLogSetup < Delayed::Plugin
  callbacks do |lifecycle|
    lifecycle.before(:execute) do |worker|
      Rails.logger = worker.logger
      ActiveRecord::Base.logger = worker.logger
    end
  end
end

不幸的是,我试图将 log子-拼凑起来的<代码>目标#puts直接称作 log(在gin子里)的尝试,仍然 t不去欧佩集团想要做的事情。

Answer 4

这样做的另一个办法是,在您的铁路申请中,在<代码>上填写必要的标识文件。我们现在看着这一点。

#!/usr/bin/env ruby

require File.expand_path(File.join(File.dirname(__FILE__),  .. ,  config ,  environment ))
require  delayed/command 

# This was added to make sure the DJ log has the same log level 
# as the rails app, and to ensure ActiveRecord uses the same log 
# when loaded inside a DJ worker process.
#
Delayed::Worker.logger ||= Logger.new(File.join(Rails.root,  log ,  delayed_job.log ), Rails.configuration.log_level)
ActiveRecord::Base.logger = Delayed::Worker.logger

Delayed::Command.new(ARGV).daemonize

这种做法十分简单、清晰。

更为重要的是,在不涉及延迟工人过程的假设情景下,不会出现忽略AR记录的风险。对我们来说,这种做法与其他一些答案相似,造成许多头痛和混乱。

友情链接