A build or install fails with "Resource temporarily unavailable"
Why a large build such as npm run build stops with "can't spawn worker thread", and how to raise the process limit.
A customer's build or install stops with a message such as OS can't spawn worker thread: Resource temporarily unavailable (os error 11). It happens with large JavaScript builds (npm run build, Next.js) and sometimes with Composer or an image tool.
What it means
Every account has a process limit, the most programs it may run at once. It protects the server from a runaway script. A large build starts many helper processes at the same moment and can need more than the limit allows, so the system refuses the next one.
Steps
- Open Users & Resellers, click Manage next to the account, and open the Limits tab.
- Raise the Process limit. For a one-off build, you can instead tick No limit at all. This removes the protection for that account.
- Click Save all changes and ask the customer to start the build again.
- When it has finished, put the limit back to a sensible figure, or untick No limit at all.
Tip: only remove the limit for an account you trust. With no limit, a runaway process can slow or crash the server for everyone. If the account's websites show a 502 error as well, see A website shows a 502 Bad Gateway error.
Each limit is explained in Setting resource limits.