# After 'Got a signal from the OS: "terminated"' container had to restart manually

**URL:** <https://forum.storj.io/t/after-got-a-signal-from-the-os-terminated-container-had-to-restart-manually/11929>\
**Category:** troubleshooting\
**Created:** [February 22, 2021, 10:11pm UTC](https://forum.storj.io/t/after-got-a-signal-from-the-os-terminated-container-had-to-restart-manually/11929 "2021-02-22T22:11:16Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [March 9, 2021, 4:13pm UTC](https://forum.storj.io/t/after-got-a-signal-from-the-os-terminated-container-had-to-restart-manually/11929/6 "2021-03-09T16:13:18Z")

</div>

It happened today again. I will try now if these settings will help:

> **[Runtime options with Memory, CPUs, and GPUs](https://docs.docker.com/config/containers/resource_constraints/)**
>
> Specify the runtime options for a container

or this:

> [@OOM Killer invoked due to slow disk I/O](https://forum.storj.io/t/oom-killer-invoked-due-to-slow-disk-i-o/7783/11):
>
> I was having an issue with my rock64 (similar to pi4) having huge IOwaits under heavy load. What seemed to happen is some operation would hit the HDD (garbage collection perhaps), and then the requests would start piling up. When there was a heavy load on the network, this backlog would eventually overwhelm the system and OOM killer would kick in. I found that setting the max concurrent requests to 40 alleviated this problem. You would need to add this line to your config.yaml file (or un-commen…

Do you know if `--memory` or `--memory-swap` have to be at a specific position of the run command?

---

_[View the full topic](https://forum.storj.io/t/after-got-a-signal-from-the-os-terminated-container-had-to-restart-manually/11929)._