spawn ps enoent in cloud run service
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
previous i use below script in Dockerfile.
FROM node:16.16.0-slim
...
RUN sed -i 's/pidusage(pids, function retPidUsage(err, statistics) {/pidusage(pids, { usePs: true }, function retPidUsage(err, statistics) {/' ./node_modules/pm2/lib/God/ActionMethods.js
...
then i fixed issue(https://github.com/Unitech/pm2/issues/4360).
@Unitech i use google cloud run service. but it has problem now. it repeat forever....;;
2022-08-18 08:23:46.390 JST
2022-08-17T23:23:46: PM2 error: Error caught while calling pidusage
2022-08-18 08:23:46.488 JST
2022-08-17T23:23:46: PM2 error: Error: Error: spawn ps ENOENT
my pm2 library version is 5.2.0.
however it is still problem.
how can i do? anyone fix it?
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
The report names PM2 5.2.0, a Node 16.16.0-slim Docker image, Cloud Run, and the pidusage call using ps. Start by reproducing the repeated spawn ps ENOENT in that Docker and Cloud Run setup and inspect the PM2 process-statistics path; done means the error no longer repeats and process monitoring works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gcp, javascript, node.js
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100