This is all I found
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGKILL (Forced termination): ember build -prod
Ideas?
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 ![]()
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 ![]()
בדרך כלל אני משתמש ב-grep /var/discourse/discourse-setup ומעתיק ומדביק את החלק שמייצר את ה-swap.
אני גם לא מבין.
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.
הוספתי 2 גיגה. אני לא יודע למה אני מנסה לחסוך במקום בדיסק, למרות זאת. כי אם אי פעם אמצא את עצמי במצב שבו יש לי בעיות בגלל שאני חסר כמה גיגות, יש לי דברים חשובים יותר לחשוב עליהם מאשר גודל הזיכרון החליפי שלי.
עשיתי בנייה מחדש (2-הקטנים) לפני כמה דקות וקיבלתי את ההודעה הבאה:
סביבת עבודה: פרודקשן
ההגדרה 'staticAddonTrees' תעבור לברירת מחדל של true בגרסה הבאה של Embroider ולא ניתן לכבות אותה. כדי להתכונן לכך, עליך להגדיר 'staticAddonTrees: true' בקונפיגורציה של Embroider.
ההגדרה 'staticAddonTestSupportTrees' תעבור לברירת מחדל של true בגרסה הבאה של Embroider ולא ניתן לכבות אותה. כדי להתכונן לכך, עליך להגדיר 'staticAddonTestSupportTrees: true' בקונפיגורציה של Embroider.
בנייה...
undefined
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL הפקודה נפסקה ב-SIGKILL (סיום בכוח): ember build -prod
מה הצעד הבא?
I had feeling I’ve seen this before.
I had 8 GB RAM and swap is 2 GB — how much do I really need nowadays, if that comes from lack of memory?
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 is 11+ GB for small forum ![]()
Have you got the two kernel tunables set? They will affect how much virtual memory is needed.
I would answer no, because I don’t have any idea what you are talking about ![]()
I’m sure then, you haven’t set them!
Unfortunately tweaking the Linux kernel isn’t part of the official Discourse installation, but my understanding is that these two simple tricks will help your server run well and use less memory. Or, of course, you can do without but you might find you need more RAM+swap than you would like.
See MKJ’s Opinionated Discourse Deployment Configuration if you want more tips.
That was due to a particular characteristic of old memory management code, and doesn’t apply to Linux today. Now there is no real rule of thumb; it’s just a question of how much you need.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.