최근 Discourse 요구 사항이 변경되었나요?

2024년 9월 이후로, 서버의 RAM 용량이 1GB(심지어 4GB) 이상임에도 불구하고 command was killed with SIGKILL 오류와 함께 재빌드(rebuild)가 실패하는 문제를 겪는 사용자들이 많이 발생하고 있습니다.

https://meta.discourse.org/search?q=%22command%20was%20killed%20with%20SIGKILL%22

스와프 파일(swap file)을 생성하거나 용량을 늘리면 문제가 해결된다는 조언이 있었으며, 실제로 해당 방법으로 해결된 사례가 있습니다:

저 역시 RAM 용량이 2GB에서 4GB인 7개의 포럼 중 최소 2곳에서 이 문제를 경험했습니다.

요건이 변경된 것이라면 문서도 업데이트되어야 하고, 아니면 어딘가에 문제가 있는 것입니다.

(이 주제를 어디에 게시해야 할지 모르겠습니다. Contribute > Bug, #installation, Contribute > Site feedback 등을 고려해 보았습니다. 필요하시면 이동해 주세요 :smile:)

Agreed. Though the setup for the VM i was using really should have some swap, the machine should have had more than enough RAM to handle the build. Maybe just call out the need for a swap partition/file in the docs?

discourse-setup offers to create a swap file automatically if it detects 2GB or less of memory.

Hi gerhard,

I’m aware of this, but this doesn’t address the issue unfortunately. Instances with more than 2 GB RAM will experience the rebuild error, and even instances with < 2 GB RAM who already had a 2GB swap file created by discourse-setup experiences the issue as well, like @alltiagocom’s instance.

Plus, this problem seems quite recent and was never reported before September 2024, according to the search.

Yes, it does. But we are in a situation, where it should create at least 2 GB of cache every time there is less than 8 GB of RAM.

I would guess it comes from the fact that every single forum will use plugins. Or something, because I don’t understand mechanics of these things.

It should be made clearer that those values are real minimums in deed, and if an admin decides to use different plugins, more RAM and cache are needed. I mean, we have far too many topics where the reason for the issues is a lack of memory.

This seems to need to be increased. As @Canapin pointed out with my topic having 4g of ram was not sufficient.

And as I mentioned in my topic the instructions for adding a swap file should be added to git hub install instructions even if just an option if 4g of ram or less.

@david recently worked on this space, our memory bottleneck is during asset compilation and we now have a low memory mode as well.

My understanding is that 2gb should still be supported, this is something we will investigate.

Closing in favour of: