Question
Deployment terminated suddenly when downloading and extracting Node v20.12.2
- Posted on April 15, 2024• Last validated on April 15, 2024
- DevOpsSoftware Development
Asked by Saw William Joseph
I was deploying my front end when all of a sudden, during the download and extraction of Node v20.12.2, the process suddenly terminated. There were no error messages or exceptions shown so I have no idea what went wrong. Could someone please help me with this? I would really appreciate it. Thank you. The following is the logs from the build logs.
[2024-04-15 12:36:26] │ => Checking out commit "5178ffe58886ee5f17a52753cc7fdd6c14247867"
[2024-04-15 12:36:26] │
[2024-04-15 12:36:26] │ ✔ cloned repo to /workspace
[2024-04-15 12:36:26] ╰────────────────────────────────────────╼
[2024-04-15 12:36:26]
[2024-04-15 12:36:26] › applying source directory foodProjectSpringBoot/src/main/webapp/app
[2024-04-15 12:36:27] ✔ using workspace root /workspace/foodProjectSpringBoot/src/main/webapp/app
[2024-04-15 12:36:27]
[2024-04-15 12:36:27] › configuring custom build command to be run at the end of the build:
[2024-04-15 12:36:27] │ npm run build
[2024-04-15 12:36:27]
[2024-04-15 12:36:27] ╭──────────── buildpack detection ───────────╼
[2024-04-15 12:36:27] │ › using Ubuntu 22.04 stack
[2024-04-15 12:36:28] │ Detected the following buildpacks suitable to build your app:
[2024-04-15 12:36:28] │
[2024-04-15 12:36:28] │ heroku/nodejs-engine v1.5.3
[2024-04-15 12:36:28] │ digitalocean/node v0.3.6 (Node.js)
[2024-04-15 12:36:28] │ digitalocean/procfile v0.0.4 (Procfile)
[2024-04-15 12:36:28] │ digitalocean/custom v0.1.2 (Custom Build Command)
[2024-04-15 12:36:28] │
[2024-04-15 12:36:28] │ For documentation on the buildpacks used to build your app, please see:
[2024-04-15 12:36:28] │
[2024-04-15 12:36:28] │ Node.js v0.3.6 https://do.co/apps-buildpack-node
[2024-04-15 12:36:28] ╰─────────────────────────────────────────────╼
[2024-04-15 12:36:28]
[2024-04-15 12:36:28] ╭──────────── app build ───────────╼
[2024-04-15 12:36:28] │ ---> Node.js Buildpack
[2024-04-15 12:36:28] │ ---> Installing toolbox
[2024-04-15 12:36:28] │ ---> - jq
[2024-04-15 12:36:30] │ ---> - yj
[2024-04-15 12:36:33] │ ---> Getting Node version
[2024-04-15 12:36:33] │ ---> Resolving Node version
[2024-04-15 12:36:35] │ ---> Downloading and extracting Node v20.12.2
[2024-04-15 13:36:04] Terminated
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hey!
There was some network maintenance last week that might have caused that issue, are you still seeing the problem?
If this is still happening, it is possible that your build process requires more memory, have you tried using a larger container size with more RAM as a test?
Best,
Bobby