pm2 stuck on full fetch
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
react-box@0.1.0 deploy ~~
pm2 deploy ecosystem.config.js production
--> Deploying to production environment
--> on host ec2~~.us-east-2.compute.amazonaws.com
○ deploying origin/master
○ executing pre-deploy-local
○ hook pre-deploy
○ fetching updates
○ full fetch
Stuck at full fetch.
Nothing written in the log files?...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the deployment command shown in ecosystem.config.js: pm2 deploy ecosystem.config.js production, and trace the deployment flow at the “full fetch” step. Reproduce the production deployment if possible, inspect why it remains stuck and why no log output is written, and consider the issue done when the fetch completes or reports a useful failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100