8 days ago
Deployment has succeeded https://eoms-rapid.com/ but we can't access the website, is there any outage?
13 minutes since the deployment has passed.
7 Replies
8 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 8 days ago
8 days ago
Can you share the logs? I got an upstream error when trying to access the URL.
8 days ago
We specifically get this error
<--- Last few GCs --->
[33:0x1168b000] 209632 ms: Mark-Compact 4013.3 (4134.4) -> 3992.3 (4132.3) MB, pooled: 0 MB, 2018.21 / 0.01 ms (average mu = 0.256, current mu = 0.213) allocation failure; scavenge might not succeed
[33:0x1168b000] 212128 ms: Mark-Compact 4015.1 (4136.0) -> 3994.7 (4134.7) MB, pooled: 0 MB, 1937.75 / 0.01 ms (average mu = 0.241, current mu = 0.224) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xe46bbe node::OOMErrorHandler(char const*, v8::OOMDetails const&) [next-server (v15.4.10)]
2: 0x1244310 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [next-server (v15.4.10)]
3: 0x12445e7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [next-server (v15.4.10)]
4: 0x14734f5 [next-server (v15.4.10)]
5: 0x1473523 [next-server (v15.4.10)]
8: 0x1cf8351 [next-server (v15.4.10)]
6: 0x148c5fa [next-server (v15.4.10)]
7: 0x148f7c8 [next-server (v15.4.10)]
Aborted
npm warn config production Use --omit=dev instead.
eoms-rapid-development@0.1.0 start
next start
▲ Next.js 15.4.10
- Local: http://localhost:8080
- Network: http://10.250.11.127:8080
✓ Starting...
✓ Ready in 2s
[33:0x427c6000] 214845 ms: Mark-Compact 4008.2 (4126.8) -> 3988.5 (4129.7) MB, pooled: 0 MB, 1920.18 / 0.01 ms (average mu = 0.297, current mu = 0.296) allocation failure; scavenge might not succeed
[33:0x427c6000] 217224 ms: Mark-Compact 4011.1 (4131.9) -> 3989.7 (4130.0) MB, pooled: 0 MB, 1930.79 / 0.01 ms (average mu = 0.246, current mu = 0.188) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
----- Native stack trace -----
2: 0x1244310 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [next-server (v15.4.10)]
8 days ago
Try adding NODE_OPTIONS=--max-old-space-size=8192 in your environment variables and redeploy. (Make sure you have at least 8 GB allocated for the service)
0x5b62656e5d
Try adding `NODE_OPTIONS=--max-old-space-size=8192` in your environment variables and redeploy. (Make sure you have at least 8 GB allocated for the service)
8 days ago
We already did this-even have max-old-space-size=16384, currently looking for some errors on the code like unnecessary fetches without filtering per user
8 days ago
I'd check to make sure the code isn't doing something like SELECT * on database queries when it's supposed to be selecting one or a few.
You can also use node --inspect to help with debugging as well.