You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having an issue where a cap deploy (and the deploy:restart task it executes) is causing Sidekiq to restart in an old release. In fact, when I manually issue a cap sidekiq:stop and cap sidekiq:start, Sidekiq ends up starting in the oldest release rather than the current one. Here's what's happening:
I end up seeing a background job failure reported by New Relic, with a stacktrace pointing to:
Note that release number. However, when SSHing into the server, here's what the current release is:
goodbrews@goodbre.ws:~/api$ ls -lah
total 16K
drwxrwxr-x 4 goodbrews goodbrews 4.0K May 31 16:49 .
drwxr-xr-x 8 goodbrews goodbrews 4.0K May 29 17:28 ..
lrwxrwxrwx 1 goodbrews goodbrews 43 May 31 16:49 current -> /home/goodbrews/api/releases/20130531164922
drwxrwxr-x 7 goodbrews goodbrews 4.0K May 31 16:49 releases
drwxrwxr-x 9 goodbrews goodbrews 4.0K May 25 02:58 shared
goodbrews@goodbre.ws:~/api$ ls -lah releases
total 28K
drwxrwxr-x 7 goodbrews goodbrews 4.0K May 31 16:49 .
drwxrwxr-x 4 goodbrews goodbrews 4.0K May 31 16:49 ..
drwxrwxr-x 11 goodbrews goodbrews 4.0K May 30 02:45 20130530024501
drwxrwxr-x 11 goodbrews goodbrews 4.0K May 31 14:51 20130531145135
drwxrwxr-x 11 goodbrews goodbrews 4.0K May 31 15:07 20130531150733
drwxrwxr-x 11 goodbrews goodbrews 4.0K May 31 15:30 20130531153013
drwxrwxr-x 11 goodbrews goodbrews 4.0K May 31 16:49 20130531164922
As you can see, Sidekiq jobs are apparently running on old code. This is after I issued a new deployment to fix my worker and hopefully solve the error. But Sidekiq restarted in what is actually the oldest kept release. I issued a cap sidekiq:stop and cap sidekiq:start manually with no luck. Errors are still streaming in and pointing to the oldest release.
I should perhaps also note that the jobs being run currently are retries. Is it possible that retries are, for some reason, run against the code they were initially queued from?
I should perhaps also note that the jobs being run currently are retries. Is it possible that retries are, for some reason, run against the code they were initially queued from?
—
Reply to this email directly or view it on GitHub.
That's actually what I found out was going on. I was waiting for a retry to trigger to make sure it wouldn't error out again, and it seems to be fine now. Sorry!
I'm having an issue where a
cap deploy
(and thedeploy:restart
task it executes) is causing Sidekiq to restart in an old release. In fact, when I manually issue acap sidekiq:stop
andcap sidekiq:start
, Sidekiq ends up starting in the oldest release rather than the current one. Here's what's happening:I end up seeing a background job failure reported by New Relic, with a stacktrace pointing to:
/home/goodbrews/api/releases/20130530024501/app/workers/webhook_worker.rb
Note that release number. However, when SSHing into the server, here's what the current release is:
As you can see, Sidekiq jobs are apparently running on old code. This is after I issued a new deployment to fix my worker and hopefully solve the error. But Sidekiq restarted in what is actually the oldest kept release. I issued a
cap sidekiq:stop
andcap sidekiq:start
manually with no luck. Errors are still streaming in and pointing to the oldest release.Here's my
deploy.rb
file for reference:The text was updated successfully, but these errors were encountered: