[圖片] Rebake all posts? rake posts:rebake On a new Ubuntu 18 host, I’m having a problem with this step: # cd /var/discourse/ # ./launcher enter app # rake posts:rebake Rebaking post markdown for 'default' 5 / 2950 ( 0.2%)/usr/local/bin/rake: line 2: 6788 Killed RAILS…

You mentioned it’s a 2GB server, but does it have swap? [圖片] Create a swapfile for your Linux server Self-Hosting bulb For servers with <= 4GB of RAM, running ./discourse-setup will prompt for and automatically create a 2GB swapfile. Most cloud virtual machi…

Do you still have both servers up? Can you compare folders? Maybe rsync between old and new and see the differences?

The old server is gone (the process seemed to go so smoothly, I didn’t think to check images before shutting the old one down) Would rebaking re-create the missing images? Any thoughts as to why it’s failing?

This evening I rebooted the host (though it’s uptime was under 2 weeks) rebaking succeeded # rake posts:rebake Rebaking post markdown for 'default' 2950 / 2950 (100.0%) 2950 posts done! ------------------------- but, as you suggested, this didn’t bring back the images. Ill start a new thread…

I tried recover_from_tombstone. The command exited without warnings, and so I’m trying to rebuild. That process fails at random places. I’ve tried rebooting the host, rebuilding the app, and it fails anywhere from 5-55% of the way through the rebake process. Note that there are only ~2950 posts.. …

I’ve tried a couple of times, and still had errors. Since I posted, the missing images were fixed, and I’ve rebuilt the container. The rebake still failed, but after a reboot of the host I was able to get the rebake to succeed. # ./launcher enter app root@community-2019-app:/var/www/discourse# rak…

[圖片] watchmanmonitor: Killed FYI this nearly always means “ran out of memory or some other hard limit” You can probably see a log entry in your kernel ring buffer (dmesg) saying something got killed to free memory.

Now that you mention it, no. root@community-2019:~# swapon --show root@community-2019:~# free -h total used free shared buff/cache available Mem: 1.9G 1.4G 193M 70M 317M 273M Swap: 0B 0B 0…

[圖片] Stephen: You mentioned it’s a 2GB server, but does it have swap? I’ve added swap via Digital Ocean’s guide . Will see how this goes.

That’s it, without a doubt. On 1GB it’s mandatory, on anything more than 1GB it’s only a matter of time before processes are killed when the system runs low on free memory: [圖片] Worker process is more than defined? Self-hosting Our recommended configuration is…

Sure, makes sense. I just did a rebake again, and sure enough, it was eating in to the new swap. CPU[||||||||||||||||||||||||||||||||||||||||||||100.0%] Tasks: 77, 84 thr; 1 running Mem[|||||||||||||||||||||||||||||||||||||||1.58G/1.95G] Load average: 2.05 1.51 1.15 Swp[||||||||||||||||…

运行 rake posts:rebake 时出现错误“Killed”

支持安装

Stephen (Stephen) 2019年五月11日 00:39 12

You mentioned it’s a 2GB server, but does it have swap?

話題		回覆	觀看
Rebake failing: how to diagnose and fix? Support	6	248	2025年十二月14日
Rebake aborts with error message Self-hosting server-resources	4	1204	2022年三月12日
Rake:rebake crashes with errors: PG::ConnectionBad: PQsocket Self-hosting server-resources	11	1609	2023年二月28日
Rebake all posts? Self-hosting	14	9229	2019年五月13日
My journey into a massive posts rebake job Self-hosting	35	4708	2024年七月10日

运行 rake posts:rebake 时出现错误“Killed”

相關主題