Note that there are some explanatory texts on larger screens.

plurals
  1. PODelayed_job is no longer logging
    primarykey
    data
    text
    <p>For some reason, my Rails app is no longer logging my DelayedJob gem's activity, either to a separate log (<code>delayed_job.log</code>) or to the main Rails development log. I am also using the Workless gem, should this be relevant. </p> <p>It used to say things like this:</p> <pre><code>2013-06-07T19:16:25-0400: [Worker(delayed_job.workless host:MyNames-MacBook-Pro.local pid:28504)] Starting job worker 2013-06-07T19:16:38-0400: [Worker(delayed_job.workless host:MyNames-MacBook-Pro.local pid:28504)] MyApp#scrape completed after 13.0290 2013-06-07T19:16:38-0400: [Worker(delayed_job.workless host:MyNames-MacBook-Pro.local pid:28504)] 1 jobs processed at 0.0761 j/s, 0 failed ... 2013-06-07T19:16:43-0400: [Worker(delayed_job.workless host:MyNames-MacBook-Pro.local pid:28504)] Exiting... </code></pre> <p>But nothing is appearing anymore in any of the logs.</p> <p>How can I make sure that DelayedJob activity logs to the main development log? I don't mind if it also logs to a separate log, but the important thing is that I see its activity in my Mac's console. </p> <p>I have searched for answers to this issue online (such as <a href="https://stackoverflow.com/questions/9507765/delayed-job-not-logging">here</a> and nothing is working.</p> <p>Here is my delayed_job_config.rb: (in config/initializers)</p> <pre><code>Delayed::Worker.sleep_delay = 60 Delayed::Worker.max_attempts = 2 Delayed::Worker.max_run_time = 20.minutes Delayed::Worker.logger = Rails.logger Delayed::Worker.logger.auto_flushing = true </code></pre> <p>Please let me know if you'd like more code from my app - I'd be happy to provide it. Much thanks from a Rails newbie.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload