# Upgrade to 3.0.2: NameError: undefined method \`call' for class \`Redis::Client' (with a "fix")

**URL:** <https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [March 18, 2023, 5:07pm UTC](https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602 "2023-03-18T17:07:33Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![steinhh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steinhh/32/242776_2.png) [@steinhh](https://meta.discourse.org/u/steinhh)\
**Post date:** [March 18, 2023, 5:07pm UTC](https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602/1 "2023-03-18T17:07:33Z")

</div>

Just tried upgrading from 3.0.1 to 3.0.2, and got this error during rake db:migrate stage:

```plaintext
rake aborted!
NameError: undefined method `call' for class `Redis::Client'
Did you mean? caller
/var/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:83:in `alias_method'
/var/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:83:in `profile_method'
/var/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:65:in `counter_method'
/var/discourse/config/initializers/006-mini_profiler.rb:90:in `<main>'
/var/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.4.3/lib/rails/engine.rb:667:in `load'

```

Very long story short, I found that pegging redis at version 4.8.0 instead of leaving the redis version unspecified in the Gemfile did the trick. I.e., for the Gemfile:

```plaintext
-gem "redis"
+gem "redis", "4.8.0"

```

I don’t feel very comfortable mucking about with this, but it seems to me that this is an unintended side effect of redis being upgraded elsewhere since my last upgrade (to 3.0.1), and that a reinstall of Discourse 3.0.1 would now show the same problem.

Hope this helps someone, and please let me know if this leaves my system in a vulnerable state 🙂

---

_[View the full topic](https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602)._