Users shim and packman report bootstrap failures after upgrading their Discourse servers, with errors tied to bundle installation and plugin conflicts. packman initially suspects plugin issues but later shares a stack trace pointing to a gem conflict (ffi-1.15.5 vs 1.16.2) triggered by the discourse-migratepassword plugin. pfaffman confirms this plugin is broken and advises disabling it or reverting to an old container. shim clarifies their issue is unrelated to plugins, showing logs where services shut down cleanly but bootstrap fails at the final bundle step. merefield and merefield repeatedly urge users to scroll up for earlier, more revealing error messages — noting that the visible “FAILED” block is generic and not the root cause. RGJ later announces the discourse-migratepassword plugin has been updated. The thread highlights the importance of checking full logs and distinguishing between plugin-specific and core system issues during rebuilds.
im having issues rebuilding my forum after upgrading the server on linode
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle config --local deployment true' failed with return #<Process::Status: pid 505 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"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle config --local deployment true'", "su discourse -c 'bundle config --local without \"development test\"'", "su discourse -c 'bundle install --retry 3 --jobs 4'"]}
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.
I’m seeing a similar error. I’ve tried a rebuild with all but two plugins disabled (docker-manager and migrate passwords) so I don’t think it’s plugin related. I ran discourse-doctor but the only occurrence of ‘error’ is the description of how to search for the word error.
Unfortunately I have to go out to an appointment now but I’ll look for other issues when I get back.
OK, I wasn’t aware that the same error appeared for multiple causes. I just knew the errors looked very similar, if not identical when viewed on my phone and as they occurred from what appeared to be the same set of patches I assumed they might be related. I’ll start a new thread with my problems in it.
Actually the helpful nature of Discourse isn’t helpful here. When I started to report the problem I got the “Your post looks similat to this one” which encourages you not to create a new post.
Thank you I have the same issue on 2 forums and that happened after the patch update however the fix was suggested … I have no idea how to go about it. it would be helpful if they pushed the new PR so that we can update it via the console.
es:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
2023-09-27 16:50:33.227 UTC [42] LOG: received fast shutdown request
I, [2023-09-27T16:50:33.227763 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 111
111:signal-handler (1695833433) Received SIGTERM scheduling shutdown...
2023-09-27 16:50:33.252 UTC [42] LOG: aborting any active transactions
2023-09-27 16:50:33.262 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
2023-09-27 16:50:33.265 UTC [46] LOG: shutting down
2023-09-27 16:50:33.282 UTC [42] LOG: database system is shut down
111:M 27 Sep 2023 16:50:33.282 # User requested shutdown...
111:M 27 Sep 2023 16:50:33.283 * Saving the final RDB snapshot before exiting.
111:M 27 Sep 2023 16:50:33.295 * DB saved on disk
111:M 27 Sep 2023 16:50:33.296 # Redis is now ready to exit, bye bye...
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle config --local deployment true' failed with return #<Process::Status: pid 539 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"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle config --local deployment true'", "su discourse -c 'bundle config --local without \"development test\"'", "su discourse -c 'bundle install --retry 3 --jobs 4'"]}
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.
92863be4bda311c642a83b1afd97e58a64e9044ea2dc0e23f245fafb086851f7
it appears that everything builds fine but on the last exit part it fails
