Duplicate e-mails arriving for new notes
@ernstvn and I started receiving duplicate e-mails for notes. A quick scan of our logs show a few failures:
When I looked at the actual logs, I see:
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67614 worker-kiq09 sidekiq: 2017-05-02T20:00:53.676Z 9358 TID-oqvm6vrwg WARN: {"context":"Job raised exception","job":{"class":"NewNoteWorker","args":[28687792],"retry":3,"queue":"new_note","jid":"c1f27a61208f317e7a6ce72c","created_at":1493755252.889792,"enqueued_at":1493755252.8927827,"error_message":"No such file or directory - getcwd","error_class":"Errno::ENOENT","failed_at":1493755253.6754174,"retry_count":0},"jobstr":"{\"class\":\"NewNoteWorker\",\"args\":[28687792],\"retry\":3,\"queue\":\"new_note\",\"jid\":\"c1f27a61208f317e7a6ce72c\",\"created_at\":1493755252.889792,\"enqueued_at\":1493755252.8927827}"}
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67620 worker-kiq09 sidekiq: 2017-05-02T20:00:53.676Z 9358 TID-oqvm6vrwg WARN: Errno::ENOENT: No such file or directory - getcwd
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67625 worker-kiq09 sidekiq: 2017-05-02T20:00:53.676Z 9358 TID-oqvm6vrwg WARN: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/popen.rb:13:in `pwd'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67629 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/popen.rb:13:in `popen'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67633 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/sidekiq_middleware/memory_killer.rb:47:in `get_rss'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67639 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/sidekiq_middleware/memory_killer.rb:18:in `call'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67644 worker-kiq09 sidekiq: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/sidekiq-4.2.7/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67649 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/sidekiq_middleware/arguments_logger.rb:6:in `call'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67654 worker-kiq09 sidekiq: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/sidekiq-4.2.7/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67659 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/metrics/sidekiq_middleware.rb:13:in `block in call'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67663 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/metrics/transaction.rb:49:in `run'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67668 worker-kiq09 sidekiq: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/metrics/sidekiq_middleware.rb:13:in `call'
May 2 20:00:53 localhost 2017-05-02_20: 00:53.67672 worker-kiq09 sidekiq: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/sidekiq-4.2.7/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
Is there something wrong with worker-kiq09?