Unitech / Unitech/pm2

Issue with pm2 statup: PM2 error: Cancelling versioning data parsing

Open
#5,909 0 comments 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

What's going wrong?

When I add a dependency with version having character like "json-server": "^1.0.0-beta.3" , pm2 process is not starting the application

How could we reproduce this issue?

Install "json-server": "^1.0.0-beta.3" as dependency with a sample node project , and start application using pm2.

Supporting information

# Run the following commands
$ pm2 report

PM2 | 2024-10-31T14:46:19: PM2 log: PM2 version : 5.4.2
PM2 | 2024-10-31T14:46:19: PM2 log: Node.js version : 20.11.1
PM2 | 2024-10-31T14:46:19: PM2 log: Current arch : x64
PM2 | 2024-10-31T14:46:19: PM2 log: PM2 home : C:\Users<>.pm2
PM2 | 2024-10-31T14:46:19: PM2 log: PM2 PID file : C:\Users<>.pm2\pm2.pid
PM2 | 2024-10-31T14:46:19: PM2 log: RPC socket file : \.\pipe\rpc.sock
PM2 | 2024-10-31T14:46:19: PM2 log: BUS socket file : \.\pipe\pub.sock
PM2 | 2024-10-31T14:46:19: PM2 log: Application log path : C:\Users<>.pm2\logs
PM2 | 2024-10-31T14:46:19: PM2 log: Worker Interval : 30000
PM2 | 2024-10-31T14:46:19: PM2 log: Process dump file : C:\Users<>.pm2\dump.pm2
PM2 | 2024-10-31T14:46:19: PM2 log: Concurrent actions : 2
PM2 | 2024-10-31T14:46:19: PM2 log: SIGTERM timeout : 1600
PM2 | 2024-10-31T14:46:19: PM2 log: ===============================================================================
PM2 | 2024-10-31T14:46:19: PM2 log: App [p1:0] starting in -cluster mode-
PM2 | 2024-10-31T14:46:20: PM2 log: App [p1:0] online
PM2 | 2024-10-31T14:46:22: PM2 log: App name:p1 id:0 disconnected
PM2 | 2024-10-31T14:46:22: PM2 log: App [p1:0] exited with code [0] via signal [SIGINT]
PM2 | 2024-10-31T14:46:22: PM2 error: Cancelling versioning data parsing
PM2 | 2024-10-31T14:46:22: PM2 error: Error caught while calling pidusage
PM2 | 2024-10-31T14:46:22: PM2 error: Error: No matching pid found

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

Reproduce the issue in a sample Node.js project by adding json-server at ^1.0.0-beta.3 and starting it with PM2. Run pm2 report and inspect the startup output around “Cancelling versioning data parsing” and the pidusage error. Done means the application starts normally without these errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.