Error setting up with separate Redis

Random Group
1

There is a half-lazy database server running PostgreSQL inside local network and I wanted to use it for Discourse too. Reason for this is that the web server, is far more stressed than the previously mentioned database one, which still has a lot of unused resources/potential. Redirecting Discourse’s PostgreSQL was quite easy, following a few threads on this forum (example). Whenever I try to do the same for Redis though:

  • commenting out - "templates/redis.template.yml"
  • setting DISCOURSE_REDIS_HOST instead

I always get:

Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<:status: pid="" exit="">
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 1

whenever I try to rebuild with launcher rebuild app

Is this a known issue? Anyone successfully running Discourse with non-containerised Redis?

6 posts - 4 participants

Read full topic

This is a companion discussion topic for the original entry at https://meta.discourse.org/t/error-setting-up-with-separate-redis/260859