Oops - after an update from 3.3.0.beta1-dev

Support
1

Hi guys.
I’ve updated to the latest version - I think - and now I get the infamous ‘Ooops’
The only thing - while being an amateur - I could find, thinking it might be important, is:

URGENT: Failed to initialize site default: ActiveRecord::StatementInvalid PG::UndefinedTable: ERROR:  relation "flags" does not exist
LINE 10:  WHERE a.attrelid = '"flags"'::regclass

above is from unicorn.stderr.log
To a coder/devel that probably says something - would it be possible to “fix” this installation of mine?
All thoughts shared are much appreciated! Thanks.

2

If you try doing a rebuild, does this still occur?

3

When I try bootstrap - for container was removed on build box - but that should not be different from ‘rebuild’ - that original/old version/release now, always fails with:

I, [2025-07-05T03:22:21.183304 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
error discourse@: The engine "node" is incompatible with this module. Expected version ">= 20". Got "18.17.1"
error discourse@: The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19"
warning discourse@: The engine "pnpm" appears to be invalid.
error Found incompatible module.
I, [2025-07-05T03:22:21.330613 #1]  INFO -- : yarn install v1.22.19
info No lockfile found.
[1/5] Validating package.json...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.



FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' failed with return #<Process::Status: pid 206 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "cmd"=>["if [ \"$version\" != \"tests-passed\" ]; then\n  rm -rf app/assets/javascripts/node_modules\nfi", "su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'"]}
bootstrap failed with exit code 1

That was why I git a new, bootstrapped this new/latest release and got this issue.
btw Is it possible to git &| launcher a specific version/release?

1 Like