Difference between revisions of "Error Command failed with exit code 137"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
<code>[[containerd]] Task XXXXXXXX [[deleted with exit code 137]]</code> | <code>[[containerd]] Task XXXXXXXX [[deleted with exit code 137]]</code> | ||
| + | == [[yarn build]] == | ||
| + | - info Creating an optimized production build ...Killed | ||
| + | error Command failed with [[exit code 137]]. | ||
| + | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. | ||
| + | |||
| + | Solution: increase memory of machine running your [[yarn build]] process | ||
Latest revision as of 09:40, 7 December 2023
error Command failed with exit code 137
terminated
Amazon CloudWatch Logs Insights example:[edit]
fields @timestamp, @message | filter @message like "error Command failed with exit code 137" | sort @timestamp asc
containerd[edit]
containerd Task XXXXXXXX deleted with exit code 137
yarn build[edit]
- info Creating an optimized production build ...Killed error Command failed with exit code 137. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Solution: increase memory of machine running your yarn build process
Related[edit]
SIGKILL- Kubernetes
elasticsearch --versionOOMKilled- Killing
Reason: OOMKilled - exit code: 137- exited with code 137
See also[edit]
- Killing
- OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s),
systemd-oomd, OOMKilled, oom-killer, memcpy,sar -r,Exit code: 137
Advertising:
