Unitech / Unitech/pm2

tcp port ESTABLISHED and LISTEN

Open
#4,833 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

--- PM2 report ----------------------------------------------------------------
Date                 : Mon Aug 31 2020 18:07:38 GMT+0800 (Taipei Standard Time)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version         : 4.4.1
node version         : 12.16.3
node path            : /usr/local/bin/pm2
argv                 : /volume2/@appstore/Node.js_v12/usr/local/bin/node,/usr/local/lib/node_modules/pm2/lib/Daemon.js
argv0                : node
user                 : root
uid                  : 0
gid                  : 0
uptime               : 4322min
===============================================================================
--- CLI ----------------------------------------------------
local pm2            : 4.4.1
node version         : 12.16.3
node path            : /usr/local/bin/pm2
argv                 : /volume2/@appstore/Node.js_v12/usr/local/bin/node,/usr/local/bin/pm2,report
argv0                : node
user                 : root
uid                  : 0
gid                  : 0
===============================================================================
--- System info --------------------------------------------
arch                 : x64
platform             : linux
type                 : Linux
cpus                 : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
cpus nb              : 4
freemem              : 1121468416
totalmem             : 1916854272
home                 : /root
===============================================================================
--- PM2 list -----------------------------------------------
┌─────┬────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name       │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0   │ tc_main    │ default     │ 1.0.0   │ fork    │ 32015    │ 15m    │ 1    │ online    │ 0.2%     │ 39.1mb   │ root     │ disabled │
└─────┴────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================

What's going wrong?

my script doesn't work after move to new server..
how can I debug it?

How could we reproduce this issue?

I'm not sure the following is normal when I run lsof -i tcp:3000

sometimes

COMMAND   PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
node    32015 root   19u  IPv6 14877433      0t0  TCP 192.168.1.22:3000->192.168.1.41:49580 (ESTABLISHED)
node    32015 root   20u  IPv6 14877411      0t0  TCP *:3000 (LISTEN)

and sometimes shows

COMMAND   PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
node    32015 root   19u  IPv6 14877433      0t0  TCP 192.168.1.22:3000->192.168.1.41:49580 (ESTABLISHED)
pm2    32015 root   20u  IPv6 14877411      0t0  TCP *:3000 (LISTEN)

Supporting information

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 with the PM2 report and the two lsof -i tcp:3000 outputs, comparing PID 32015 and the ESTABLISHED/LISTEN entries. Done means establishing whether the differing command names are expected and documenting a reproducible diagnosis or next debugging step.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, linux, node.js
Domain
devops, networking
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.