Build backend failed - Error: Command failed with ENOMEM: yarn --version about amplify-cli HOT 21 CLOSED

I got this too, but managed to work around it by fixing the Amplify CLI version to 12.10.1 in Build settings.

from amplify-cli.

I got this too, but managed to work around it by fixing the Amplify CLI version to 12.10.1 in Build settings.

Sadly encountered this too today. Rolling back to 12.10.1 worked, after rolling back to 12.10.2 didn't (current LATEST is 12.10.3). Funny thing is my build worked on 12.10.2 (I'm assuming) - 12 days ago, using LATEST, which was after 12.10.2 was released.

from amplify-cli.

from amplify-cli.

everything is building correctly today 🤷

from amplify-cli.

@DuncanHouston @kouz75 @duckbytes could you provide is the appId, region and failed build number to dive into the logs?

from amplify-cli.

@ykethan (sorry for all the edits...)
I have the same issue. I tried backend: 12.10.3 w/ frontend: nvm use 18. Build 230 on qranswers (dxm5h4ts57z1x), us-east-1. backend failed.
2024-04-04T00:00:45.231Z [INFO]: 🛑 Received error [Error: Command failed with ENOMEM: yarn --version spawn ENOMEM] running command [yarn --version]

rolled back to backend: 12.10.1 and frontend: nvm use 18 Build 231 - backend failed with socket timeout
2024-04-04T00:18:10.709Z [INFO]: 🛑 Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

rolled back to backend: 12.10.1 and frontend: nvm use 16, Build 232 - backend built fine, frontend built fine

231 seemed odd, so ... tried again - backend: 12.10.1 and frontend: nvm use 18, Build 233 - backend built fine, frontend built fine. So, the 'socket error' seems transient and not repeatable for Build 231 - since 233 and 231 were identical.

Build 230 has the issue with 12.10.3.

Let me know if you need further info to track this down

from amplify-cli.

@ykethan

dlkp8fs0a5r7s
eu-west-1
Build 19

There are more than one backend. The name of the one that failed is jobye.

from amplify-cli.

from amplify-cli.

hi,

sorry for the delay.
On my side, everything is working correctly now (I have switch back to default setting (use default nodejs version and default amplify version)).

from amplify-cli.

Hey folks, could you add AMPLIFY_ENABLE_DEBUG_OUTPUT as true, retry with the latest Amplify CLI version and provide us the stack trace?
Could you provide us information the build image being used?
Do you observe any errors on CloudFormation or on a local push?

from amplify-cli.

@ykethan, Sadly encountered this too from 3 days ago, also I'm running that you said.

Build image: Amazon Linux:2 image
Amplify CLI: latest
AMPLIFY_ENABLE_DEBUG_OUTPUT: true

I got this track trace:

2024-04-04T20:05:52.356Z [INFO]: �[K
2024-04-04T20:05:52.853Z [WARNING]: ✖ There was an error initializing your environment.
2024-04-04T20:05:52.855Z [INFO]: 🛑 Received error [Error: Command failed with ENOMEM: yarn --version
spawn ENOMEM] running command [yarn --version]
2024-04-04T20:05:52.855Z [INFO]: Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
ShellCommandExecutionError: Received error [Error: Command failed with ENOMEM: yarn --version
spawn ENOMEM] running command [yarn --version]
at execWithOutputAsString (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-cli-core/lib/utils/shell-utils.js:38:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getYarnPackageManager (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-cli-core/lib/utils/packageManager.js:131:36)
at async getLayerGlobs (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/layerHelpers.js:305:36)
at async hashLayerVersion (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/layerHelpers.js:345:32)
at async hashLayerResource (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/layerHelpers.js:275:12)
at async isBackendDirModifiedSinceLastPush (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:408:26)
at async /snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:266:45
at async asyncForEach (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:454:9)
at async /snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:255:9
at async asyncForEach (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:454:9)
at async getResourcesToBeUpdated (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:253:5)
at async AmplifyToolkit.getResourceStatus (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:122:32)
at async getAuthResourceName (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-auth/lib/utils/getAuthResourceName.js:5:30)
at async updateAppClientWithGeneratedSecret (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-auth/lib/provider-utils/awscloudformation/utils/generate-cognito-app-client-secret.js:13:38)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/push-resources.js:274:5)

from amplify-cli.

Sorry, where do I put the AMPLIFY_ENABLE_DEBUG_OUTPUT true setting. My yaml file looks like this for the backend.
version: 1.4
backend:
phases:
preBuild:
commands:
- npm i -g @aws-amplify/[email protected]
build:
commands:
- '# Execute Amplify CLI with helper script'
- amplifyPush --simple

I have continuous deployment setup from GitHub.

from amplify-cli.

Sorry, where do I put the AMPLIFY_ENABLE_DEBUG_OUTPUT true setting. My yaml file looks like this for the backend. version: 1.4 backend: phases: preBuild: commands: - npm i -g @aws-amplify/[email protected] build: commands: - '# Execute Amplify CLI with helper script' - amplifyPush --simple

I have continuous deployment setup from GitHub.

Into App settings > Environment variables > Manage Variables > Add Variable

from amplify-cli.

@ykethan
Build image: Amazon Linux:2 image
Amplify CLI: 12.10.3
AMPLIFY_ENABLE_DEBUG_OUTPUT: true
Build 234
dxm5h4ts57z1x
The local push works fine.

same issue as above:
2024-04-04T23:38:13.541Z [INFO]: �[K
2024-04-04T23:38:14.648Z [WARNING]: ✖ There was an error initializing your environment.
2024-04-04T23:38:14.649Z [INFO]: 🛑 Received error [Error: Command failed with ENOMEM: yarn --version
spawn ENOMEM] running command [yarn --version]
2024-04-04T23:38:14.650Z [INFO]: Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
ShellCommandExecutionError: Received error [Error: Command failed with ENOMEM: yarn --version
spawn ENOMEM] running command [yarn --version]
at execWithOutputAsString (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-cli-core/lib/utils/shell-utils.js:38:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getYarnPackageManager (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-cli-core/lib/utils/packageManager.js:131:36)
at async getLayerGlobs (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/layerHelpers.js:305:36)
at async hashLayerVersion (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/layerHelpers.js:345:32)
at async hashLayerResource (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-function/lib/provider-utils/awscloudformation/utils/layerHelpers.js:275:12)
at async isBackendDirModifiedSinceLastPush (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:408:26)
at async /snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:266:45
at async asyncForEach (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:454:9)
at async /snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:255:9
at async asyncForEach (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:454:9)
at async getResourcesToBeUpdated (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:253:5)
at async AmplifyToolkit.getResourceStatus (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/resource-status-data.js:122:32)
at async getAuthResourceName (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-auth/lib/utils/getAuthResourceName.js:5:30)
at async updateAppClientWithGeneratedSecret (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-category-auth/lib/provider-utils/awscloudformation/utils/generate-cognito-app-client-secret.js:13:38)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/push-resources.js:274:5)
2024-04-04T23:38:14.665Z [INFO]:
2024-04-04T23:38:14.666Z [INFO]: Session Identifier: 09d4832f-0780-40ef-9b30-93aa075052b9

from amplify-cli.

Hey folks, thank you for providing the information. The Amplify team is currently investigating this issue. We will provide an update here as soon as we get some additional information.
Marking as bug for further investigation.

from amplify-cli.

We have what we believe to be the proper fix for the issue (aws-amplify/amplify-category-api#2426). We are having trouble reproducing the issue to properly test the fix. If anyone can provide the reproduction steps from a new project that would be very useful to us.

from amplify-cli.

We have created a tagged release with the fix mentioned above. If anyone can use this to confirm this resolves the issue that would be greatly appreciated. However, please do not use this version in a production environment. This tagged release has not gone through the normal battery of tests. @aws-amplify/[email protected].

from amplify-cli.

@ggcespia, thank you for testing the tagged release. We will continue to investigate the root cause of this issue.

from amplify-cli.

I got this too, but managed to work around it by fixing the Amplify CLI version to 12.10.1 in Build settings.

Sadly encountered this too today. Rolling back to 12.10.1 worked, after rolling back to 12.10.2 didn't (current LATEST is 12.10.3). Funny thing is my build worked on 12.10.2 (I'm assuming) - 12 days ago, using LATEST, which was after 12.10.2 was released.

Hi, Confirming successful build execution using Amplify CLI version 12.10.1 as previously mentioned.

from amplify-cli.

The fix for this was shipped in version 12.11.1

from amplify-cli.

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from amplify-cli.