I have error when upgrade new version of discourse

Product Support Self-hosting

AI-generated summary

A user, cmdntd, encountered a migration error while upgrading Discourse, specifically failing at db:migrate with a Pups::ExecError. JammyDodger advised checking earlier logs, which cmdntd shared — showing PostgreSQL and Redis shutdowns during the migration. merefield identified the root cause: the Discourse Chatbot plugin now has new installation requirements, and removing it without following uninstall instructions can break upgrades. After following the guide, cmdntd confirmed the fix but expressed concern about complexity and asked for a simpler process and clarity on topic restrictions for the bot’s content indexing. merefield directed them to the article’s section on the bot’s “vision” — detailing what content it can access and privacy implications. The issue was resolved by adhering to plugin-specific upgrade steps, highlighting the importance of reviewing plugin documentation during Discourse upgrades.

1

I have this error when upgrade newest version:
Could you help me, please?

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 888 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.
88bbed682282caba3443f559b68a7c49ac4995115633c09ffe4299aceea844ac
2

Can you scroll up from that message and check for any errors? (or paste the output here in a codeblock so we can have a look)

3

This is something before:

1 gem installed
gem install safe_ruby -v 1.0.4 -i /var/www/discourse/plugins/discourse-chatbot/gems/3.2.2 --no-document --ignore-dependencies --no-user-install
Successfully installed safe_ruby-1.0.4
1 gem installed
Compiled js-processor: tmp/js-processor.js
== 20230820010101 EnableEmbeddingExtension: migrating =========================
-- enable_extension(:embedding)

I, [2023-09-15T14:11:46.731576 #1]  INFO -- : Terminating async processes
I, [2023-09-15T14:11:46.731720 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
I, [2023-09-15T14:11:46.731821 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 111
2023-09-15 14:11:46.731 UTC [42] LOG:  received fast shutdown request
111:signal-handler (1694787106) Received SIGTERM scheduling shutdown...
2023-09-15 14:11:46.739 UTC [42] LOG:  aborting any active transactions
2023-09-15 14:11:46.746 UTC [42] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2023-09-15 14:11:46.747 UTC [46] LOG:  shutting down
111:M 15 Sep 2023 14:11:46.766 # User requested shutdown...
111:M 15 Sep 2023 14:11:46.766 * Saving the final RDB snapshot before exiting.
2023-09-15 14:11:46.828 UTC [42] LOG:  database system is shut down
111:M 15 Sep 2023 14:11:46.910 * DB saved on disk
111:M 15 Sep 2023 14:11:46.910 # Redis is now ready to exit, bye bye...
4

Read the OP carefully here:

There are new requirements for using Chatbot.

Do not remove it unless you follow the uninstall instructions first.

I will probably be simplifying this in a future version, but for now, those instructions must be followed.

5

It’s worked. But seems so complicated.
Could you make it more simple?

Do you have a table about restriction of bot’s reading topics? (I’m worried when you make it more smarter to index discourse content)

6

The bots “vision” is covered in the same article.