Deploy gets stuck issue

[Santhosh222]

I am trying to deploy the strapi application using AWS Amplify. The deploy is getting struck after the command "npm start". In logs after this line "/bin/sh: hostname: command not found", the deploy is getting struck.

App Details:
App Id: arn:aws:amplify:us-east-1:190647250537:apps/dt801vbzq7wqs
PFA the build settings YML file and log file in zip file.

Archive.zip

[extheory]

Deploys are hanging for me too.

Multiple frontend deploy got stuck here:

2020-12-15T12:53:04 [INFO]: Updating Edge config

[Santhosh222]

Just want to know, what is causing this error "/bin/sh: hostname: command not found". I am not getting this issue in Heroku. Anyone experienced this before in Amplify console?

[garyleefight]

What's the script for npm run start. Can you share more info on your app? From the yml file you sent, the backend is not an amplify backend

[Santhosh222]

Thanks for the reply @garyleefight

I am trying to deploy Strapi app which is an CMS app. For "npm run start", "strapi start" command runs and starts Strapi app at port 1337. The backend is not an amplify backend. I am just trying to start Strapi app.

I also tried YML like this (keeping all commands in frontend) but it didn't work too. Same error is occurring here /bin/sh: hostname: command not found.

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm install
    build:
      commands:
        - npm run build
    postBuild:
      commands:
        - npm start
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

[derrickmehaffy]

Adding a bit of information (I am a solutions engineer for Strapi).

We use the package node-machine-id to get a unique ID for our telemetry system, see:

https://github.com/strapi/strapi/blob/ea4a60777080d67a662c92bd65477909d50c841e/packages/strapi/lib/services/metrics/sender.js#L6

https://github.com/strapi/strapi/blob/ea4a60777080d67a662c92bd65477909d50c841e/packages/strapi/lib/services/metrics/sender.js#L25

https://github.com/strapi/strapi/blob/ea4a60777080d67a662c92bd65477909d50c841e/packages/strapi-generate-new/lib/index.js#L7

https://github.com/strapi/strapi/blob/ea4a60777080d67a662c92bd65477909d50c841e/packages/strapi-generate-new/lib/index.js#L42

https://github.com/strapi/strapi/blob/048e6fd3afe7e96bcf4e75ccff7ce78cd1bc89e9/packages/strapi/lib/utils/success.js#L8

https://github.com/strapi/strapi/blob/048e6fd3afe7e96bcf4e75ccff7ce78cd1bc89e9/packages/strapi/lib/utils/success.js#L24

---

Here is a link to the package on NPM: https://www.npmjs.com/package/node-machine-id

We currently have an open issue where we will look at replacing this package with something else if there is an alternative that meets our needs and will work with amplify: strapi/strapi#8893

[hxhieu]

@derrickmehaffy you may need to review Strapi telemetry policy.

Why do we need the machine ID? I thought the UUID was enough?
Pretty much a secured host will not give you that machine ID as the app will not have any elevated permissions on such host.

[ganipcanot]

@Santhosh222 it looks like you were running npm start in the build stage per the logs in the Archive.zip you attached.

Are you still experiencing an issue?

Also - how are you deploying your application? Are you doing a manual deploy by dragging and dropping a zip folder?

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.