Unitech / Unitech/pm2

bucket suddenly gone from pm2+

Open
#5,769 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

What's going wrong?

since a few months ago, my vps bucket suddenly vanished from pm2+ and i can't seem to upload it again or anything. pm2 plus doesn't show the bucket and pm2 link shows this:

[PM2.IO][ERROR] Wrong public key
[PM2.IO] Contact support contact@keymetrics.io and send us the error message

using pm2 5.3.1

the website shows an error and loads the bucket that's not my vps bucket

image

How could we reproduce this issue?

  • have a bucket suddenly disappear for some reason
  • watch

Supporting information

--- Daemon logs --------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2        | 2024-02-19T21:48:15: PM2 log: App [hee8-bot:1] exited with code [0] via signal [SIGINT]
PM2        | 2024-02-19T21:48:15: PM2 log: pid=3086210 msg=process killed
PM2        | 2024-02-19T21:48:15: PM2 log: pid=3086212 msg=process killed
PM2        | 2024-02-19T21:48:16: PM2 log: PM2 successfully stopped
PM2        | 2024-02-19T21:48:25: PM2 log: ===============================================================================
PM2        | 2024-02-19T21:48:25: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2        | 2024-02-19T21:48:25: PM2 log: Time                 : Mon Feb 19 2024 21:48:25 GMT+0100 (Central European Standard Time)
PM2        | 2024-02-19T21:48:25: PM2 log: PM2 version          : 5.3.1
PM2        | 2024-02-19T21:48:25: PM2 log: Node.js version      : 20.11.1
PM2        | 2024-02-19T21:48:25: PM2 log: Current arch         : x64
PM2        | 2024-02-19T21:48:25: PM2 log: PM2 home             : /root/.pm2
PM2        | 2024-02-19T21:48:25: PM2 log: PM2 PID file         : /root/.pm2/pm2.pid
PM2        | 2024-02-19T21:48:25: PM2 log: RPC socket file      : /root/.pm2/rpc.sock
PM2        | 2024-02-19T21:48:25: PM2 log: BUS socket file      : /root/.pm2/pub.sock
PM2        | 2024-02-19T21:48:25: PM2 log: Application log path : /root/.pm2/logs
PM2        | 2024-02-19T21:48:25: PM2 log: Worker Interval      : 30000
PM2        | 2024-02-19T21:48:25: PM2 log: Process dump file    : /root/.pm2/dump.pm2
PM2        | 2024-02-19T21:48:25: PM2 log: Concurrent actions   : 2
PM2        | 2024-02-19T21:48:25: PM2 log: SIGTERM timeout      : 1600
PM2        | 2024-02-19T21:48:25: PM2 log: ===============================================================================

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 reviewing the pm2 link entry point and the PM2+ bucket association, using the reported “Wrong public key” message and daemon logs as the reproduction context. Determine why the VPS bucket is missing or mismatched; done means the correct bucket is visible in PM2+ and pm2 link no longer reports the key error.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.