georgersantoss encountered an error while updating their Discourse installation, specifically during the db:migrate step, which failed with a Pups::ExecError. After reviewing logs, they identified that the discourse-chatbot plugin — installed via merefield — was causing a conflict during the rebuild. Removing the plugin allowed the update to proceed successfully georgersantoss. Jagster asked which plugin was the culprit, and merefield clarified that the chatbot plugin requires manual updates to app.yml, a breaking change due to its experimental nature. georgersantoss acknowledged they hadn’t kept up with plugin updates and appreciated the guidance. merefield apologized for the disruption but noted the new features justify the effort. The community helped diagnose the issue, highlighting the importance of checking plugin compatibility during updates.
It’s been a while since I updated my Discourse installation and today I went to do so and it’s giving me this error. I’ve never picked up something like this because I’m just an enthusiast and not a programmer.
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 514 exit 1>
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
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
If you scroll up from that end ‘FAILED’ block you should be able to see more detailed error messages within the output that you can share here (or paste all of it in so we can have a look )
