# Sidekiq Gem::ConflictError

**URL:** <https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076>\
**Category:** Support\
**Created:** [August 23, 2016, 4:25pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076 "2016-08-23T16:25:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Overgrow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overgrow/32/478189_2.png) [@Overgrow](https://meta.discourse.org/u/Overgrow)\
**Post date:** [August 23, 2016, 4:25pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076/1 "2016-08-23T16:25:53Z")

</div>

Hi, I’ve stumbled upon this issue, hard to tell what I’ve done wrong and changed in the process. My sidekiq was working well but suddenly I can’t start it…

> overgrow@axii:~/discourse$ sidekiq  
> /home/overgrow/.rbenv/versions/2.3.0/lib/ruby/site\_ruby/2.3.0/rubygems/specification.rb:2288:in `raise\_if\_conflicts’: Unable to activate actionpack-5.0.0, because rack-1.6.4 conflicts with rack (~\> 2.0) (Gem::ConflictError)  
> overgrow@axii:~/discourse$ gem list --local | grep rack  
> rack (2.0.1, 1.6.4)  
> overgrow@axii:~/discourse$ gem list --local | grep actionp  
> actionpack (5.0.0, 4.2.7)

I’ve already tried running `bundle install`

---

<div class="post-metadata">

**Author:** ![Overgrow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overgrow/32/478189_2.png) [@Overgrow](https://meta.discourse.org/u/Overgrow)\
**Post date:** [August 23, 2016, 4:42pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076/2 "2016-08-23T16:42:44Z")

</div>

Anyone? thanks in advance…

---

<div class="post-metadata">

**Author:** ![Overgrow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overgrow/32/478189_2.png) [@Overgrow](https://meta.discourse.org/u/Overgrow)\
**Post date:** [August 24, 2016, 2:47pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076/3 "2016-08-24T14:47:43Z")

</div>

Finally… Solved.. I have downgraded sidekiq to 4.1.2

`gem uninstall sidekiq`

`gem install sidekiq --version '<=4.1.2'`

/home/carlos/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:35:in `block in setup': You have already activated activesupport 5.0.0, but your Gemfile requires activesupport 4.2.7. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

So `bundle exec sidekiq` works perfectly..

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [August 24, 2016, 3:09pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076/4 "2016-08-24T15:09:28Z")

</div>

You shouldn’t have to install `sidekiq` if you did `bundle install`. You should run it use `bundle exec sidekiq` and it should use the one from the project.

---

<div class="post-metadata">

**Author:** ![Overgrow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overgrow/32/478189_2.png) [@Overgrow](https://meta.discourse.org/u/Overgrow)\
**Post date:** [August 24, 2016, 3:36pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076/5 "2016-08-24T15:36:14Z")

</div>

Ok, I got it… Thank you!

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [August 24, 2016, 6:24pm UTC](https://meta.discourse.org/t/sidekiq-gem-conflicterror/49076/6 "2016-08-24T18:24:22Z")

</div>