Error: ESPIPE: invalid seek, read
Open
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 Oct 12 2020 10:39:54 GMT+0000 (UTC)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version : 4.1.2
node version : 8.11.4
node path : /home/ubuntu/.nvm/versions/node/v8.11.4/bin/pm2
argv : /home/ubuntu/.nvm/versions/node/v8.11.4/bin/node,/home/ubuntu/.nvm/versions/node/v8.11.4/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : ubuntu
uid : 1000
gid : 1000
uptime : 6min
===============================================================================
--- CLI ----------------------------------------------------
local pm2 : 4.1.2
node version : 8.11.4
node path : /home/ubuntu/.nvm/versions/node/v8.11.4/bin/pm2
argv : /home/ubuntu/.nvm/versions/node/v8.11.4/bin/node,/home/ubuntu/.nvm/versions/node/v8.11.4/bin/pm2,report
argv0 : node
user : ubuntu
uid : 1000
gid : 1000
===============================================================================
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
cpus nb : 1
freemem : 473083904
totalmem : 1038749696
home : /home/ubuntu
===============================================================================
--- PM2 list -----------------------------------------------
┌────┬─────────────────────────┬─────────┬─────────┬──────────┬────────┬──────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
└────┴─────────────────────────┴─────────┴─────────┴──────────┴────────┴──────┴──────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/home/ubuntu/.pm2/pm2.log last 20 lines:
PM2 | 2020-10-12T09:30:06: PM2 error: Error caught while calling pidusage
PM2 | 2020-10-12T09:30:14: PM2 error: Error: ESPIPE: invalid seek, read
PM2 | 2020-10-12T09:33:36: PM2 log: App [ckka:1] exited with code [0] via signal [SIGKILL]
PM2 | 2020-10-12T09:33:36: PM2 log: App [ckka:1] starting in -cluster mode-
PM2 | 2020-10-12T09:33:36: PM2 log: App [ckka:1] online
PM2 | 2020-10-12T10:33:13: PM2 log: ===============================================================================
PM2 | 2020-10-12T10:33:13: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2 | 2020-10-12T10:33:13: PM2 log: Time : Mon Oct 12 2020 10:33:13 GMT+0000 (UTC)
PM2 | 2020-10-12T10:33:13: PM2 log: PM2 version : 4.1.2
PM2 | 2020-10-12T10:33:13: PM2 log: Node.js version : 8.11.4
PM2 | 2020-10-12T10:33:13: PM2 log: Current arch : x64
PM2 | 2020-10-12T10:33:13: PM2 log: PM2 home : /home/ubuntu/.pm2
PM2 | 2020-10-12T10:33:13: PM2 log: PM2 PID file : /home/ubuntu/.pm2/pm2.pid
PM2 | 2020-10-12T10:33:13: PM2 log: RPC socket file : /home/ubuntu/.pm2/rpc.sock
PM2 | 2020-10-12T10:33:13: PM2 log: BUS socket file : /home/ubuntu/.pm2/pub.sock
PM2 | 2020-10-12T10:33:13: PM2 log: Application log path : /home/ubuntu/.pm2/logs
PM2 | 2020-10-12T10:33:13: PM2 log: Process dump file : /home/ubuntu/.pm2/dump.pm2
PM2 | 2020-10-12T10:33:13: PM2 log: Concurrent actions : 2
PM2 | 2020-10-12T10:33:13: PM2 log: SIGTERM timeout : 1600
PM2 | 2020-10-12T10:33:13: PM2 log: ===============================================================================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 with the PM2 daemon log entries around pidusage and the reported ESPIPE read error, using the supplied PM2 4.1.2 and Node 8.11.4 Linux environment as context. Trace the process-monitoring path that emits this error and determine what evidence or regression test would show the issue is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100