Unitech / Unitech/pm2

SOAWN SH ENOENT

Open
#3,970 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Description

Hello,

Excuse me, when I try to deploy my api with pm2 I receive this error:
spawn sh ENOENT
I know the problem come from my ecosystem file but i don't know why.

Please help me with this. Thank you

this is my ecosystem file 👍

{
"apps": [{
"name": "API",
"script": "server.js",
"args": "one two",
"instances": 1,
"autorestart": true,
"watch": false,
"max_memory_restart": "1G",
"env": {
"NODE_ENV": "development"
},
"env_production": {
"NODE_ENV": "production"
}
}],

"deploy": {
"production": {
"user": "node",
"host": "300.84.447.141",
"ref": "origin/master",
"repo": "https://github.com/Jesuyon/noti_serve.git",
"path": "/root/var/www/production",
"pre-setup" : "apt-get install git",
"post-deploy": "npm install && pm2 reload ecosystem.config.js --env production"
}
}
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the deployment described in the issue with the supplied ecosystem file, using server.js as the application entry point. Inspect the PM2 deployment path and environment around the reported “spawn sh ENOENT” error; done means the deployment completes without that error and the production process reloads successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.