# Error "Killed" while running rake posts:rebake
**URL:** https://meta.discourse.org/t/error-killed-while-running-rake-posts-rebake/111943
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [March 18, 2019, 4:53pm UTC](https://meta.discourse.org/t/error-killed-while-running-rake-posts-rebake/111943 "2019-03-18T16:53:37Z")
**Posts on this page:** 3
**Page:** 2
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 13, 2019, 3:07am UTC](https://meta.discourse.org/t/error-killed-while-running-rake-posts-rebake/111943/23 "2019-05-13T03:07:35Z")
You absolutely want swap. It is super cheap insurance. Even if you never use it, it’s _easily_ worth the minor cost in disk space.
Unless, of course, you enjoy processes being randomly terminated when you go exactly one byte over the total system memory at any given time..
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 13, 2019, 6:53pm UTC](https://meta.discourse.org/t/error-killed-while-running-rake-posts-rebake/111943/24 "2019-05-13T18:53:02Z")
> [@Stephen](#):
>
> What would be useful would be a way to pipe a migrated app.yml into discourse-setup, so that site-specific stuff could be treated as a default and preserved, while the other stuff would be configured for the system for the first time.
You can re-run `discourse-setup`, but it’s fragile, so if you changed it by hand, it’s possible to make a change that will break it. I suspect that in this case it would have created the swap and set the memory parameters just fine.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [June 12, 2019, 6:53pm UTC](https://meta.discourse.org/t/error-killed-while-running-rake-posts-rebake/111943/25 "2019-06-12T18:53:05Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
[Previous page](https://meta.discourse.org/t/error-killed-while-running-rake-posts-rebake/111943.md?page=1)