This is all I found ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGKILL (Forced termination): ember build -prod Ideas?

It ran too long. Try increasing swap or ram.

I’m a bit sceptical. 8 GB RAM, it dyed right away and something like this has never happened before. What can be changed so that that memory is not enough today, but was enough day before yessterday and when I upgraded database :thinking:

I appreciate your skepticism. That’s been the solution when I’ve had that error. A (very) quick internet search says the same.

I’ll try it anyway, of course. Adding swap isn’t that big job. But I can’t understand why it happened :man_shrugging:

I usually grep /var/discourse/discourse-setup and copy/paste the part that makes the swap. I don’t understand either.

2-container, and when I first stopped web_only and then did both containers, it went through. So it can be lack of memory in deed.

30 years ago the recommendation was to have as much swap as you had RAM. I don’t know what the rule of thumb is now, but I think with 8GB, adding 2 or even 4 isn’t a bad idea.

I added 2 gigas. I don’t know why I’m trying to save disk space, though. Because if I’m ever in situation where I’m in troubles because I’m few gigas short I have bigger things to think than size of my swap.

I did rebuilding (2-container) just few minutes ago and I got this: Environment: production The setting 'staticAddonTrees' will default to true in the next version of Embroider and can't be t…

I had feeling I’ve seen this before. [Bild] Rebuild fails with exit 1: ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Support This is all I found ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGKILL (Forced termination): ember build -prod Ideas? …

Well, I changed swap from 2G to 4G, and rebuilding went thru. So mayby it was again matter of amount of RAM. Or it was a fluke. And then we are back in FAQ-topic: how much RAM does Discourse really need — because swapfile is de facto part of total amount RAM, and now it looks like the actual need i…

Neuer Aufbau schlägt fehl mit Exit 1: ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL

Unterstützung

mcdanlj (Michael K Johnson) 2. März 2025 um 03:27 16

Das lag an einer bestimmten Eigenschaft des alten Speichermanagement-Codes und gilt heute nicht mehr für Linux. Jetzt gibt es keine wirkliche Faustregel mehr; es ist nur eine Frage, wie viel Sie brauchen.

Thema		Antworten	Aufrufe
Failed new install Self-hosting	7	337	19. März 2025
Have Discourse's requirements changed recently? Self-hosting	7	358	4. April 2025
Rebuild failed because there was no swap Support	2	330	10. September 2024
High rebuild memory requirements: April 2025 edition Self-hosting hosting	32	914	15. Februar 2026
Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory Self-hosting server-resources	18	1593	6. Februar 2024

Neuer Aufbau schlägt fehl mit Exit 1: ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL

Verwandte Themen