[2.5b2, backend] could not fork new process for connection: Cannot allocate memory

[Andres Rodriguez]

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.

[Andres Rodriguez (andreserl)]

This could be that debug logging was enabled and that was causing increased memory usage, otherwise, something is leaking memory.

[Blake Rouse (blake-rouse)]

Debug does leak memory, its documented in Django that enabling debug will store all the queries made in the DebugCursor.

[Mike Pontillo (mpontillo)]

Maybe we should consider a separate debugging option for logging all queries, so we can get MAAS debug logs without the potential clutter.

[Mike Pontillo (mpontillo)]

(and memory leaks)

[Blake Rouse (blake-rouse)]

I believe this issue is fixed in 2.6.