Hi,
my old container still works, but i’m having trouble rebuilding. The same error appeared on both attempts before and after updating the ubuntu kernel by apt upgrade
regardless of the implementation of this
AI-generated summary
User Ethsim2 is troubleshooting a Discourse rebuild failure (exit code 128), which persists even after updating Ubuntu and attempting fixes from this thread. pfaffman suggests adding swap space, despite Ethsim2 having 8GB RAM and 100GB+ SSD, citing potential memory pressure during rebuilds. Ethsim2 follows swap setup instructions but initially fails due to a typo in the fallocate command post 9. After correction and reboot, swap is successfully persistent post 29. Meanwhile, merefield identifies the root cause: a deprecated plugin, discourse-reactions, which is now bundled in core and should be removed from app.yml — confirmed by Ethsim2 as the likely culprit. Jagster and merefield emphasize that swap, even with 8GB RAM, is good practice for rebuilds. agemo confirms the plugin removal fixed their rebuild and suggests better error handling during ./launcher rebuild app. Ethsim2 expresses gratitude for the community’s help and notes their own learning journey post 31.
I think you need to add swap.
I have over 100GB of SSD space available- how do i officially allocate swap?
what does free -h return?
Swap uses some of your SSD as (very slow) RAM.
install -o root -g root -m 0600 /dev/null /swapfile
fallocate -l 2G /swapfile
mkswap /swapfile
swapon /swapfile
echo "/swapfile swap swap auto 0 0" | tee -a /etc/fstab
sysctl -w vm.swappiness=10
echo 'vm.swappiness = 10' > /etc/sysctl.d/30-discourse-swap.conf
what directory do i run these 7 commands in?
Any directory.
WIth 8GB you shouldn’t need swap, but it can’t hurt.
What error do you get when you rebuild?
That’s an example of why copy/paste is so helpful. You missed a / before your swapfile in the fallocate command.
i do recall when first setting up the server on a contract with Ionos, their image of 22.04 Ubuntu didn’t work with .\discourse-setup so i had to modify the app.yml myself.
This was without Plesk, the Ionos data center designer self-image worked fine with .\discourse-setup beforehand
So this was a standard install and you created the app.yml with discourse-setup?
What error do you get when you rebuild?
Well, I needed. Perhaps a giga would be enough, but I gave 2 GB.
yes i installed docker through .\discourse-setup
i’ll reply here if i get a rebuild error after the already set up swap
Remove discourse reactions from the explicit clone
(Announcement here: Bundling more popular plugins with Discourse core)
Did you make it permanent?
See Step 5.