Bootstrap failed with exit code 128

do i perform step 5 in isolation, or do i need to do the previous steps again?

It looks like you missed out “stage 5”, but I would go through the whole thing and check.

1 Like

In this topic, I think the real issue was the deprecated plugin. I probably won’t go through DigitalOcean’s procedure, but someone else can. :slightly_smiling_face:

rebuilding without swap is not pleasant and risky.

even with 8GB of RAM

but then again, there will now be a lot more plugins i don’t need in core

you will likely get away with it, but it’s good practice to have some “run-off”

1 Like

i ran cp /etc/fstab /etc/fstab.bak but still

root@ubuntu:~# free -h
               total        used        free      shared  buff/cache   available
Mem:           7.7Gi       1.8Gi       5.0Gi        83Mi       964Mi       5.6Gi
Swap:             0B          0B          0B

after reboot

those are the lines that make the swap persist between boots.

the first adds it to /etc/fstab, the last makes the swappiness get sset at every boot.

1 Like

the single-session output on running your lines is

Last login: Wed Jul 23 13:16:35 2025
root@ubuntu:~# echo "/swapfile       swap    swap    auto      0       0" | tee                                                                                                                                                                              -a /etc/fstab
/swapfile       swap    swap    auto      0       0
root@ubuntu:~# sysctl -w vm.swappiness=10
vm.swappiness = 10
root@ubuntu:~# echo 'vm.swappiness = 10' > /etc/sysctl.d/30-discourse-swap.conf
root@ubuntu:~# free -h
               total        used        free      shared  buff/cache   available
Mem:           7.7Gi       3.0Gi       389Mi       671Mi       4.3Gi       3.7Gi
Swap:             0B          0B          0B
root@ubuntu:~#

i then ran reboot in a VNC, and free -h returned the desired 2GB of Swap space :slightly_smiling_face:

Got snagged by this. Did not expect the backup to fail. Thanks for this topic and the plugin one.

A tweak to communications via ADMIN would be good or at least a check on the ./launcher rebuild app execution, with stop output with a y/n break in terminal continue.

Eventually had to remove the discotoc plugin to get it to work here but not sure that was listed in the plugin that are now core.

Really appreciate that, thanks! I’ve been learning as I go too — glad some of my posts have helped others along the way.