Debugging a nextjs build (Static worker unexpectedly exited with code: null and signal: SIGTERM)

[neilgd]

Summary

Hi,

I have a nextjs app that runs fine in dev mode on my laptop, but when I try to deploy it I get the following error right at the end of the build:

Static worker unexpectedly exited with code: null and signal: SIGTERM

It seems to run successfully despite this error.

I was wondering if there was any way of troubleshooting this? I am not using eg getStaticProps anywhere, and I suspect it is a third party component that is causing this.

Thanks!

Neil

Additional information

No response

Example

No response

[sofiennenabli]

Hello im also having this issue any solution ?

[sofiennenabli]

I just killed the port used and restart the build and it works.

[neilgd]

That doesn't work for me unfortunately :(

[sofiennenabli]

did you try to delete .next folder and rebuild
rm -rf .next

[neilgd]

@sofiennenabli - thank you, that seems to have worked! Any idea why?

[MadaShindeInai]

#14 55.43 - info Generating static pages (21/29)

#14 55.78 Static worker unexpectedly exited with code: null and signal: SIGSEGV

Faced the same issue during deployment to railway / fly.io
Approved solution did not help

[fukemy]

any solution now sir?

[chukwumaokere]

Im getting this very error today on Vercel deployments.

[sinapirani]

i have this error
i deleted .next folder but still have this error

[israel0x7CF]

hey, i do not know if this is still relevant but you should remove your node_modules and package-lock.json as well. then rebuild after npm install

[anuran-roy]

hey, i do not know if this is still relevant but you should remove your node_modules and package-lock.json as well. then rebuild after npm install

This worked, thanks a lot!

[ZentaChainAdmin]

Update Dependencies:

Ensure that all your third-party dependencies are up-to-date. You can do this by going to your package.json file check and updating the version numbers of your dependencies. Once you've done this, run npm install or yarn install (depending on your package manager) to update your node_modules. In some cases, a dependency might be incompatible with others, so you might need to check the documentation of each dependency and see if they have any known issues with the versions you're using. You don't need to update next version if you are already using a stable version. Before Updating any dependencies make sure you check the documentation and update your code also with the version you are using. I recommend using node v.18 and the build error on local or even on Vercel should be fixed.

In order to assist more efficiently conservation with the build issue it would be very helpful if people could share package.json file. to find out which dependencies gives the build error.

[emmabasseyokon]

[anttiriski]

Also had this problem today. Updated all the packages and now the build finished successfully.

I don't really know if that was the problem thought. I tried to redeploy a build from yesterday that was successful and today it gave the SIGTERM error. Weird stuff.

[vmarnauza]

Suddenly started having this error today for one of my deploy environments.

I was able to solve it by switching Node version to 16 in Project Settings. I then redeployed the app and it worked. Switched back to Node 18 and it still works.

[sinapirani]

I was able to identify the problem. The issue was located in the getInitialProps function in the _app.ts file. If there are any bugs present in that function, it will cause this error to be thrown.

[yunsii]

Encounter these warnings use App.getInitialProps function without any bugs. code: https://github.com/yunsii/nextjs-antd/blob/32addc413a15342504f8d0003d37c42e722e69ad/src/pages/_app.tsx#L17

[BhavyaCodes]

The error message disappeared for me after switching from node version 16 to 18.16.1

[chen-rn]

Running into this error as well w/ Next13 app directory, by build work fine locally but can't seem to work on Vercel.
I'm not using any getServerSideProps(directly at least)

I've tried:

• upgrading all packages
• node 16/18
• changing timeout duration to 1000

[chen-rn]

I realized that the error I was getting was SIGSEGV instead of SIGTERM. Anyhow, I couldn't get it to deploy on Vercel, while Railway.app worked.

I later made a completely new repo and just copy + pasted my code over and for some reason it worked. The only 2 library I didn't install this time were encoding + canvas, which is actually throwing an error in my vercel deployment.

Really not sure what the issue was... But at least it's working now?

[Allen-Wyatt]

I've had this error for a couple weeks now and none of the suggestions here have helped. Any ideas?

[evanwinter]

I'm experiencing this too, deploying on Render, with Node 20.3.0 and Next.js ^13.4.10. It's happened before in the last few weeks, but seems to just go away all by itself. Removing .next does not always fix it.

[Coderamrin]

I'm using next 13 with app dir
just removing the .next and rebuilding it worked on local env

[a110605]

Same error after upgrade Next.js to v13.5.2 and run yarn build under Node v16.14.0.
Removing .next folder does not help. Any suggestion to avoid / fix this error ?

Static worker unexpectedly exited with code: null and signal: SIGINT

[Redskinsjo]

if you want to build pages, first push your models, schema, queries. Then push your pages in a second step. Because your instant build will certainly match the build in place (previous). Without your architecture in place, page generation fails. I just resolved it again.

[maipato10]

I have the same issue and none of the provided solutions work I get ⨯ Static worker exited with code: 130 and signal: null, npm run dev work fine but npm run start gives web socket connection fail , I am using trpc and other API calls other API call pass but trpc fails on npm run start

"engines": {
"node": ">=20.0.0"
},

"next": "^14.2.4",

"@prisma/client": "^4.14.1",
"@tailwindcss/forms": "^0.5.3",
"@tanstack/react-query": "^4.18.0",
"@trpc/client": "^10.4.1",
"@trpc/next": "^10.4.1",
"@trpc/react-query": "^10.4.1",
"@trpc/server": "^10.4.1",

binaryTargets = ["native", "darwin", "darwin-arm64", "debian-openssl-3.0.x"]

[SarthakSKumar]

Hi.

Error: Static worker unexpectedly exited with code: null and signal: SIGTERM,

Here's a solution that worked for me:

Solution

1. Delete the lock files: This includes package-lock.json (if you're using npm) and pnpm-lock.yaml (if you're using pnpm).
2. Remove the node_modules folder: This will ensure that all your dependencies are reinstalled fresh.
3. Delete the .next folder: This will clear any cached builds.

Steps to Resolve

1. Remove lock files and folders:

   rm -f package-lock.json pnpm-lock.yaml
   rm -rf node_modules .next

2. Reinstall dependencies:
   If you're using npm:

   npm install

   If you're using pnpm:

   pnpm install

3. Rebuild your project:

   npm run build

   or

   pnpm build

Background

The issue occurred after making numerous changes across multiple files in the directory simultaneously. This approach I believe kinda resets the environment, ensuring there are no useless artefacts from previous builds or stale dependencies that could cause such issues.

Environment

I was running Next.js v.14.0.4 when I encountered and resolved this issue.

I hope this helps resolve the issue for y'all as well.

[chertik77]

still hapens, tried everything above

[justinherrera]

In my case, I fixed this error, when my database is from Google Cloud Platform and the error happens when the build is trying to fetch a data from my database but my deployment is not authorized to connect into it or it cannot reach the database server. I just went to GCP Connections and authorized my network / ip and it works now.

[ammarhairiHD]

I deleted and reinstalled .next, node_modules and package-lock.json, the result is still the same,
Error fetching beta testers: Error: Failed to fetch beta testers or invalid content type
at Object.c [as generateStaticParams] (/vercel/path0/young_guards/.next/server/app/(beta-tester)/beta-tester/[securepass]/page.js:1:4492)

Try to deploy Next.js using Vercel, I would be glad if anyone can explain and fix the error.

[badmagick329]

started having this issue a few days ago. sometimes it just randomly works. then it stops working again. i've tried everything listed above

[fukemy]

found solution but not remember the the I solved this. Because npm run build seem run the project in production mode and check if any error => break build. All you need to do is make sure how to resolve all problem show in the terminal

[tarikwaleed]

the way i solved the problem is that i stopped the pm2 process that runs the previous build

pm2 stop <process_name>

[krishmarsonia]

I did 2 things to resolve

1. delete the node_modules, package-lock.json and .next folder and files
2. I ran npm cache clean --force command

[eddkalosha]

Just try to go across your pages list and check for server side props (i.e. getServerSideProps, getStaticProps, getStaticPaths or similar calls for data retrieving). One of the page seems incorrect processing that or have no return in render or prepared props. Try to comment that pages one by one, after some tricky work you will have the success. That approach helped to me, one of my pages was built incorrect and wasn't even used. After removed my build has successfully run.

[TeemuKoivisto]

It probably just means your machine has run out of memory. I received first this one https://github.com/orgs/vercel/discussions/5360

If you're building on your own computer, try reinstalling and rebooting to purge your swap and all. For me that fixed it on M1 MBP. If you're on remote machine, probably the same or increase the memory.

[abhishekkovuritw]

Tried all the above things, but still facing the issue.

I have created this issue
#74972

[RonAlmog]

This might sound stupid, but it worked for me, so i'll just put it here anyways: make sure you have a loading.tsx in the root folder.
in my case it's a search page that is using useSearchParams, and there is something with searchParam that needs to be inside a Suspense, and if it's not, then you get that dreaded error. not too friendly or helpful. Anyways, bottom line: if the page that is giving you the trouble is using searchParams, make sure you have that loading page.

[ben519]

Great find! This solved the issue for me. A few notes for the record..

1. (Before implementing this fix) npm run build only failed for me on the second build after deleting .next (i.e. the re-build).

2. The error I got was massive and cryptic, but this was at the tail end of it

   TypeError: Cannot read properties of undefined (reading 'length')
       at WasmHash._updateWithBuffer (/Users/bgorman/Projects/Satxuma/repos/satxuma-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:1425886)
       at WasmHash.update (/Users/bgorman/Projects/Satxuma/repos/satxuma-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:1425221)
       at BatchedHash.update (/Users/bgorman/Projects/Satxuma/repos/satxuma-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:1421582)
       at /Users/bgorman/Projects/Satxuma/repos/satxuma-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:302368
       at processQueue (/Users/bgorman/Projects/Satxuma/repos/satxuma-app/node_modules/next/dist/compiled/webpack/bundle5.js:28:1439460)
       at process.processTicksAndRejections (node:internal/process/task_queues:85:11)
   
   Node.js v22.13.1
   Static worker exited with code: 1 and signal: null
   

3. Adding loading.tsx to my app root solved the issue, but I still needed to delete my corrupted .next folder beforehand.

Here's a simple loading.tsx file that fixed the problem for me.

// app/loading.tsx

export default function Loading() {
  return <div>Loading...</div>
}

[beemee-p]

in my case, fetching data is fetching during build time. this make failure to build.
just add { cache: 'no-store' } to fetch function and it worked!
it changes static to dynamic rendering ...

fetch('/api/example', {cache: "no-store")