# Sidekiq problems after downgrade from 1.7 beta to 1.6 stable **URL:** \ **Category:** Support\ **Created:** [Dezembro 22, 2016, 2:41pm UTC](https://meta.discourse.org/t/sidekiq-problems-after-downgrade-from-1-7-beta-to-1-6-stable/54660 "2016-12-22T14:41:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Paul\_Cormier1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paul_cormier1/32/121348_2.png) [@Paul\_Cormier1](https://meta.discourse.org/u/Paul_Cormier1)\ **Post date:** [Dezembro 22, 2016, 2:41pm UTC](https://meta.discourse.org/t/sidekiq-problems-after-downgrade-from-1-7-beta-to-1-6-stable/54660/1 "2016-12-22T14:41:24Z")
Sidekiq appears to be running when viewing the Sidekiq dashboard, however the scheduled jobs aren’t running. The Discourse Error Logs show the following: > 377 - Sidekiq heartbeat test failed, restarting > /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/logger.rb:76:in `add_with_opts` > /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/logger.rb:37:in `add` > /usr/local/lib/ruby/2.3.0/logger.rb:498:in `warn` > config/unicorn.conf.rb:129:in `check_sidekiq_heartbeat` > config/unicorn.conf.rb:146:in `master_sleep` > /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http\_server.rb:284:in `join` > /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/bin/unicorn:126:in `` > /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load` > /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `
` and > 679453 - Job exception: undefined method `every` for Jobs::MigrateUploadScheme:Class > Job exception: undefined method `every` for Jobs::MigrateUploadScheme:Class It shows Sidekiq version as being v4.1.2 I’ve tried rebuilding a couple of times with no luck: > cd /var/discourse > git pull > ./launcher rebuild app I’m guessing that there’s some higher version file from the 1.7 beta that’s floating around, but I’m unsure what the proper procedure would be to wipe the install folder without losing my data or config. Any help would be appreciated. ---
**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\ **Post date:** [Dezembro 22, 2016, 3:30pm UTC](https://meta.discourse.org/t/sidekiq-problems-after-downgrade-from-1-7-beta-to-1-6-stable/54660/2 "2016-12-22T15:30:00Z")
By upgrading to 1.7, your database got upgraded. Unless you have a backup made before updating and you are willing to go back to the backup, there’s no easy way back. Why do you want to downgrade? ---
**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\ **Post date:** [Dezembro 22, 2016, 3:31pm UTC](https://meta.discourse.org/t/sidekiq-problems-after-downgrade-from-1-7-beta-to-1-6-stable/54660/3 "2016-12-22T15:31:00Z")
Discourse doesn’t support downgrades. ---
**Author:** ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)\ **Post date:** [Dezembro 22, 2016, 5:04pm UTC](https://meta.discourse.org/t/sidekiq-problems-after-downgrade-from-1-7-beta-to-1-6-stable/54660/4 "2016-12-22T17:04:13Z")
Stick with 1.7 development branch for two weeks, and then switch to stable when 1.7 is out (Jan 6th). ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [Dezembro 22, 2016, 5:04pm UTC](https://meta.discourse.org/t/sidekiq-problems-after-downgrade-from-1-7-beta-to-1-6-stable/54660/5 "2016-12-22T17:04:51Z")