Next build hanging forever when deployed

[StephanMukete]

Summary

Next build works fine when running it locally, but when I deploy, it gets to the level of - info Using external babel configuration

• info Creating an optimized production build
• info Compiled successfully
• info Collecting page data
• info Generating static pages (3/3)

and then stays there with no error generated . I've updated to the latest version of Next and using Node 20 but still facing same issue

Additional information

No response

Example

No response

[icyJoseph]

Hi,

Can you make a build locally? Like, next build && next start? It is not the same as doing next dev, and hopefully, it reproduces the issue you see when deploying, so that we can debug it.

[StephanMukete]

I'm definitely able to make a build on local. here's a sample

> acq-bankreader-server@0.1.13 start
> npm run build && PORTFOLIO=Acquisition APP_NAME=bank-reader NODE_ENV=production node ./app.js


> acq-bankreader-server@0.1.13 build
> next build

- warn You are using a non-standard "NODE_ENV" value in your environment. This creates inconsistencies in the project and is strongly advised against. Read more: https://nextjs.org/docs/messages/non-standard-node-env
- info Skipping linting
- info Checking validity of types  
- info Creating an optimized production build  
- info Compiled successfully
- info Collecting page data  
- info Generating static pages (3/3)
- info Finalizing page optimization  

Route (pages)                              Size     First Load JS
┌ ○ /404                                   193 B          80.2 kB
├ λ /api/v1/demo                           0 B              80 kB
├ λ /api/v1/log                            0 B              80 kB
├ λ /api/v1/prepare                        0 B              80 kB
└ ○ /widget                                13.2 kB        93.2 kB
+ First Load JS shared by all              80 kB
  ├ chunks/framework-7dc8a65f4a0cda33.js   45.3 kB
  ├ chunks/main-478e6dd0acce829b.js        33.7 kB
  ├ chunks/pages/_app-7e46b4b1cf27d28c.js  201 B
  └ chunks/webpack-9b312e20a4e32339.js     840 B

λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)

CaaS Refreshed{"ns":null,"configName":"laas.json","configVer":"9.0","content":"{\r\n    \"CallingClassDepth\": \"3\",\r\n    \"LogFormat\": \"JSON\",\r\n    \"tcpSocketPoolCount\": \"1\",\r\n    \"supressSysoutFallback\": false,\r\n    \"RequestContextLogging\": {\r\n        \"active\": \"true\"\r\n    },\r\n    \"handler\": {\r\n        \"class\": \"com.americanexpress.log.handler.LaasTcpHandler\",\r\n        \"poolSize\": \"3\"\r\n    },\r\n    \"DebugEvent\": {\r\n        \"active\": false\r\n    },\r\n    \"InfoEvent\": {\r\n        \"active\": false\r\n    },\r\n    \"WarningEvent\": {\r\n        \"active\": true\r\n    },\r\n    \"ErrorEvent\": {\r\n        \"active\": true\r\n    },\r\n    \"ExternalCall\": {\r\n        \"active\": true\r\n    },\r\n    \"Report\": {\r\n        \"active\": true\r\n    },\r\n    \"Clickstream\": {\r\n        \"active\": true\r\n    },\r\n    \"MetricsEvent\": {\r\n        \"active\": true\r\n    },\r\n   \"InteractiveAuditEvent\": {\r\n\t\"active\": true\r\n   },\r\n    \"TraceEvent\" : {\r\n        \"active\" : false\r\n    },\r\n  \"RegSvcAuditEvent\": {\r\n\t\"active\": true\r\n  }\r\n}\r\n","env":"E3","active":true,"refreshActive":true,"refreshInterval":10,"hosts":"","lastUpdateAt":"Fri Feb 12 01:46:37 MST 2021","lastUpdateBy":"Meenasha J Vijaya","createdAt":"Mon Sep 25 10:54:12 MST 2017","createdBy":"Hyginous N Selvadhason"}
Listening on http://0.0.0.0:8080```

[icyJoseph]

What's up with this line?

You are using a non-standard "NODE_ENV" value in your environment. This creates inconsistencies in the project and is strongly advised against

Could that be the issue?

[StephanMukete]

Have fixed this but still experiencing same issue

[StephanMukete]

It's been solved. This is caused by Memory setting in the production environment.

[h4rkl]

For anyone who got here via search looking for the descriptive answer to this - memory for heap for the build can be raised using env var:

NODE_OPTIONS="--max_old_space_size=6144"