PM2 log giving output on the same file for scaled servies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone, today I found that no matter if cluster mode or fork mode, if I scale one of my processes,
even though each process has its own ID number, in the past the log of each one was separated in different files, but now the output goes to a single file, and I am afraid that only that process is being executed.
This is happening in pm2 version 5.2.0, it is happening since I upgraded to that version.
I would appreciate any help, thanks!
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 by reproducing the behavior with PM2 5.2.0 while scaling a process in both cluster and fork modes. Compare the generated log files and verify whether each process ID writes to a separate file; done means scaled processes produce distinct per-process logs as before.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100