# Automated backups not being triggered because cannot allocate memory
**URL:** https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265
**Category:** Support
**Created:** [6월 9, 2017, 8:59오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265 "2017-06-09T20:59:33Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@yanokwa](https://meta.discourse.org/u/yanokwa)
#### Post date: [6월 9, 2017, 8:59오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/1 "2017-06-09T20:59:34Z")
Manual backups (local and to S3) work great, but automated backups don’t seem to work. Any ideas why?
**Settings**
**Errors ~ 6 minutes after trigger**
```plaintext
Job exception: Cannot allocate memory - fork(2)
/var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:15:in `backup!'
/var/www/discourse/app/jobs/regular/create_backup.rb:8:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'
```
**Ram**
```plaintext
root@discourse-app:/var/www/discourse# free -mh
total used free shared buff/cache available
Mem: 992M 664M 72M 137M 255M 50M
Swap: 2.0G 1.0G 1.0G
```
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [6월 9, 2017, 9:05오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/2 "2017-06-09T21:05:28Z")
> [@yanokwa](#):
>
> Job exception: Cannot allocate memory - fork(2)
If you are constantly swapping 1GB, you need more memory on this server.
---
### Author:  [@robbyoconnor](https://meta.discourse.org/u/robbyoconnor)
#### Post date: [6월 9, 2017, 9:13오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/3 "2017-06-09T21:13:06Z")
you probably are big enough that more memory is needed..1GB is enough.
---
### Author:  [@yanokwa](https://meta.discourse.org/u/yanokwa)
#### Post date: [6월 9, 2017, 9:22오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/4 "2017-06-09T21:22:27Z")
If it’s a RAM issue, why do manual backups work then?
---
### Author:  [@robbyoconnor](https://meta.discourse.org/u/robbyoconnor)
#### Post date: [6월 9, 2017, 9:35오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/5 "2017-06-09T21:35:59Z")
> [@yanokwa](#):
>
> If it’s a RAM issue, why do manual backups work then?
I’m not entirely sure but that error is due to insufficient memory available.
---
### Author:  [@yanokwa](https://meta.discourse.org/u/yanokwa)
#### Post date: [6월 10, 2017, 12:07오전 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/6 "2017-06-10T00:07:15Z")
I upgraded from 1 GB to 2 GB box and backups seem to be working now.
```plaintext
total used free shared buff/cache available
Mem: 2.0G 1.2G 276M 141M 544M 498M
Swap: 2.0G 28M 2.0G
```
If anyone else has this problem, I’d try a reboot first because the Ubuntu box had also recently had kernel upgrades, so maybe that was the issue.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [6월 10, 2017, 1:34오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/7 "2017-06-10T13:34:47Z")
If you run discourse-setup it will tweak the memory settings to take advantage of the additional memory.
---
### Author:  [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [6월 10, 2017, 1:38오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/8 "2017-06-10T13:38:30Z")
> [@pfaffman](#):
>
> If you run discourse-setup it will tweak the memory settings
Interesting - I didn’t realise that running discourse-setup could be done on an install which was already up and running.
---
### Author:  [@yanokwa](https://meta.discourse.org/u/yanokwa)
#### Post date: [6월 10, 2017, 1:42오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/9 "2017-06-10T13:42:25Z")
Hmm. Running the setup again sounds dangerous to my existing app.yml. Any idea what the tweaks are?
---
### Author:  [@yanokwa](https://meta.discourse.org/u/yanokwa)
#### Post date: [6월 10, 2017, 2:01오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/10 "2017-06-10T14:01:53Z")
I answered my own question 😂. According to [discourse\_docker/discourse-setup at master · discourse/discourse\_docker · GitHub](https://github.com/discourse/discourse_docker/blob/master/discourse-setup), the tweaks to app.yml are:
```plaintext
# db_shared_buffers: 128MB for 1GB, 256MB for 2GB, or 256MB * GB, max 4096MB
# UNICORN_WORKERS: 2 * GB for 2GB or less, or 2 * CPU, max 8
```
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [6월 8, 2024, 12:44오후 UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/11 "2024-06-08T12:44:43Z")
이 주제는 2555일 후 자동으로 닫혔습니다. 더 이상 답변을 작성할 수 없습니다.