Sidekiq工作並非在開發模式下開工，只在生產中

編輯：我們剛纔告訴我們，碼頭工人甚至沒有用於生產。所以看起來這個問題僅限於Docker，而不是Rails正在推出的環境。Sidekiq工作並非在開發模式下開工，只在生產中

我有一個項目我在sidekiq工作上工作似乎在我們的生產環境中運行良好，但在我的本地開發機器中，我得到了一堆sidekiq的控制檯錯誤，我不知道爲什麼。

這裏是我的sidekiq錯誤：

sidekiq_1 | 2017-03-15T17:16:24.346Z 1 TID-gq075lic0 INFO: Booting Sidekiq 4.2.3 with redis options {:url=>"redis://redis:6379/"} 
sidekiq_1 | 2017-03-15T17:16:25.240Z 1 TID-gq075lic0 INFO: Running in ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] 
sidekiq_1 | 2017-03-15T17:16:25.240Z 1 TID-gq075lic0 INFO: See LICENSE and the LGPL-3.0 for licensing details. 
sidekiq_1 | 2017-03-15T17:16:25.241Z 1 TID-gq075lic0 INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org 
sidekiq_1 | 2017-03-15T17:16:25.260Z 1 TID-gq075lic0 INFO: Loading Schedule 
sidekiq_1 | 2017-03-15T17:16:25.260Z 1 TID-gq075lic0 INFO: Schedule empty! Set Sidekiq.schedule 
sidekiq_1 | 2017-03-15T17:16:25.264Z 1 TID-gq075lic0 INFO: Schedules Loaded 
sidekiq_1 | 2017-03-15T17:16:25.266Z 1 TID-gq075lic0 WARN: {"context":"Exception during Sidekiq lifecycle event.","event":"startup"} 
sidekiq_1 | 2017-03-15T17:16:25.266Z 1 TID-gq075lic0 WARN: TypeError: can't dup NilClass 
sidekiq_1 | 2017-03-15T17:16:25.267Z 1 TID-gq075lic0 WARN: /usr/local/bundle/gems/sidekiq-scheduler-2.0.19/lib/sidekiq-scheduler/schedule.rb:126:in `dup' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-scheduler-2.0.19/lib/sidekiq-scheduler/schedule.rb:126:in `block in prepare_schedule' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-scheduler-2.0.19/lib/sidekiq-scheduler/schedule.rb:125:in `each' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-scheduler-2.0.19/lib/sidekiq-scheduler/schedule.rb:125:in `prepare_schedule' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-scheduler-2.0.19/lib/sidekiq-scheduler/schedule.rb:40:in `schedule=' 
sidekiq_1 | /gathrly/config/initializers/scheduler.rb:5:in `block (2 levels) in <top (required)>' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-4.2.3/lib/sidekiq/util.rb:54:in `block in fire_event' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-4.2.3/lib/sidekiq/util.rb:52:in `each' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-4.2.3/lib/sidekiq/util.rb:52:in `fire_event' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-4.2.3/lib/sidekiq/cli.rb:79:in `run' 
sidekiq_1 | /usr/local/bundle/gems/sidekiq-4.2.3/bin/sidekiq:12:in `<top (required)>' 
sidekiq_1 | /usr/local/bundle/bin/sidekiq:17:in `load' 
sidekiq_1 | /usr/local/bundle/bin/sidekiq:17:in `<top (required)>' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/cli/exec.rb:74:in `load' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/cli/exec.rb:74:in `kernel_load' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/cli/exec.rb:27:in `run' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/cli.rb:335:in `exec' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/cli.rb:20:in `dispatch' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/cli.rb:11:in `start' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/exe/bundle:32:in `block in <top (required)>' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors' 
sidekiq_1 | /usr/local/bundle/gems/bundler-1.14.6/exe/bundle:24:in `<top (required)>' 
sidekiq_1 | /usr/local/bundle/bin/bundle:22:in `load' 
sidekiq_1 | /usr/local/bundle/bin/bundle:22:in `<main>' 
sidekiq_1 | 2017-03-15T17:16:25.268Z 1 TID-gq075lic0 INFO: Starting processing, hit Ctrl-C to stop 
web_1  | Puma starting in single mode... 
web_1  | * Version 3.6.0 (ruby 2.3.1-p112), codename: Sleepy Sunday Serenity 
web_1  | * Min threads: 5, max threads: 5 
web_1  | * Environment: development 
web_1  | * Listening on tcp://0.0.0.0:3000

它說：

sidekiq_1 | 2017-03-15T17:16:25.260Z 1 TID-gq075lic0 INFO: Loading Schedule 
sidekiq_1 | 2017-03-15T17:16:25.260Z 1 TID-gq075lic0 INFO: Schedule empty! Set Sidekiq.schedule 
sidekiq_1 | 2017-03-15T17:16:25.264Z 1 TID-gq075lic0 INFO: Schedules Loaded

但後來我得到一個NilClass錯誤。

這裏是我的scheduler.rb文件：

require 'sidekiq/scheduler' 

Sidekiq.configure_server do |config| 
    config.on(:startup) do 
    Sidekiq.schedule = YAML.load_file(File.expand_path('../../sidekiq_scheduler.yml', __FILE__)) 
    Sidekiq::Scheduler.reload_schedule! 
    end 
end

和我sidekiq-scheduler.rb文件：

UpdateEventbriteJob: 
    cron: "*/15 * * * *" 
UpdateMeetupJob: 
    cron: "*/15 * * * *" 
PostEventEmailJob: 
    # cron: "0 9 * * *" 
    # cron: "*/1 * * * *" 
UpdateStatusJob: 
    cron: "*/1 * * * *" # Every minute for testing. Plan on every 24 hours

我測試了UpdateStatusJob本地。其他工作生產，似乎工作正常。但是這個調度程序中沒有任何東西會在開發模式下激發。我想在將它投入生產之前測試這項工作。我究竟做錯了什麼？

我也應該注意我在docker中運行的東西。我不太經常使用的東西，所以我不確定這是否阻礙了事情。

這裏是我的搬運工，撰寫文件中的相關信息：

version: '2' 
services: 

    ... 

    sidekiq: 
    build: . 
    command: bundle exec sidekiq -C config/sidekiq.yml 
    env_file: .env 
    links: 
     - db 
     - redis 

    ...

來源

2017-03-15 Antonio

yml文件可能位於開發中的不同位置嗎？ – bobber205

sidekiq.yml和sidekiq-scheduler.rb位於rails應用程序的/ config中。 – Antonio

執行路徑可能不同。加載sidekiq運行上下文時，相對路徑依賴於當前目錄。 – bobber205

在scheduler.yml PostEventEmailJob沒有任何價值，只是註釋掉行。

如果更改了文件：

UpdateEventbriteJob: 
    cron: "*/15 * * * *" 
UpdateMeetupJob: 
    cron: "*/15 * * * *" 
PostEventEmailJob: 
    cron: "0 9 * * *" 
UpdateStatusJob: 
    cron: "*/1 * * * *" # Every minute for testing. Plan on every 24 hours

它會正確解析，並開始Sidekiq。

來源

2017-03-16 21:17:55 matov

Sidekiq工作並非在開發模式下開工，只在生產中

回答

相關問題