[2.5b2, backend] could not fork new process for connection: Cannot allocate memory
Bug #1795903 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Unassigned |
Bug Description
MAAS UI becomes inaccessible with:
could not fork new process for connection: Cannot allocate memory
One I try to ssh into the machine, I'm unable to do several operations due to RAM exhaustion.
This is a VM with only 2gb of RAM. This issue has been seen after recent UI changes, but could also be related to backend changes.
I'm unable to grab any logs.
Changed in maas: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → 2.5.0rc1 |
description: | updated |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0 |
Changed in maas: | |
milestone: | 2.5.0 → 2.5.x |
tags: | added: ui |
tags: | removed: ui |
summary: |
- [2.5b2, UI, backend] could not fork new process for connection: Cannot + [2.5b2, backend] could not fork new process for connection: Cannot allocate memory |
To post a comment you must log in.
This could be that debug logging was enabled and that was causing increased memory usage, otherwise, something is leaking memory.