soyuka / pidusage

Cross-platform process cpu % and memory usage of a PID
MIT License
512 stars 55 forks source link

pm2 app keeps stopping #147

Closed Gooperdooper closed 1 year ago

Gooperdooper commented 2 years ago

Hello everyone, I'm kind of new to using pm2 and it keeps stopping. If anyone could tell me what is wrong, I would appreciate it.

Here are the logs:

2022-05-24T07:47:26: PM2 log: ===============================================================================
2022-05-24T07:47:26: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
2022-05-24T07:47:26: PM2 log: Time                 : Tue May 24 2022 07:47:26 GMT+0200 (Central European Summer Time)
2022-05-24T07:47:26: PM2 log: PM2 version          : 5.2.0
2022-05-24T07:47:26: PM2 log: Node.js version      : 16.15.0
2022-05-24T07:47:26: PM2 log: Current arch         : x64
2022-05-24T07:47:26: PM2 log: PM2 home             : /mnt/web119/b0/65/511678265/htdocs/.pm2
2022-05-24T07:47:26: PM2 log: PM2 PID file         : /mnt/web119/b0/65/511678265/htdocs/.pm2/pm2.pid
2022-05-24T07:47:26: PM2 log: RPC socket file      : /mnt/web119/b0/65/511678265/htdocs/.pm2/rpc.sock
2022-05-24T07:47:26: PM2 log: BUS socket file      : /mnt/web119/b0/65/511678265/htdocs/.pm2/pub.sock
2022-05-24T07:47:26: PM2 log: Application log path : /mnt/web119/b0/65/511678265/htdocs/.pm2/logs
2022-05-24T07:47:26: PM2 log: Worker Interval      : 30000
2022-05-24T07:47:26: PM2 log: Process dump file    : /mnt/web119/b0/65/511678265/htdocs/.pm2/dump.pm2
2022-05-24T07:47:26: PM2 log: Concurrent actions   : 2
2022-05-24T07:47:26: PM2 log: SIGTERM timeout      : 1600
2022-05-24T07:47:26: PM2 log: ===============================================================================
2022-05-24T07:47:26: PM2 log: App [index:0] starting in -fork mode-
2022-05-24T07:47:26: PM2 log: App [index:0] online
2022-05-24T07:47:26: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:47:26: PM2 error: Error while calling "getconf CLK_TCK" Error: Command failed: getconf CLK_TCK
/bin/sh: getconf: command not found

    at ChildProcess.exithandler (node:child_process:398:12)
    at ChildProcess.emit (node:events:527:28)
    at ChildProcess.emit (node:domain:537:15)
    at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:527:28)
    at Socket.emit (node:domain:537:15)
    at Pipe.<anonymous> (node:net:709:12)
    at Pipe.callbackTrampoline (node:internal/async_hooks:130:17) {
  code: 127,
  killed: false,
  signal: null,
  cmd: 'getconf CLK_TCK'
}
2022-05-24T07:47:26: PM2 error: Error while calling "getconf PAGESIZE" Error: Command failed: getconf PAGESIZE
/bin/sh: getconf: command not found

    at ChildProcess.exithandler (node:child_process:398:12)
    at ChildProcess.emit (node:events:527:28)
    at ChildProcess.emit (node:domain:537:15)
    at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:527:28)
    at Socket.emit (node:domain:537:15)
    at Pipe.<anonymous> (node:net:709:12)
    at Pipe.callbackTrampoline (node:internal/async_hooks:130:17) {
  code: 127,
  killed: false,
  signal: null,
  cmd: 'getconf PAGESIZE'
}
2022-05-24T07:47:26: PM2 error: Error caught while calling pidusage
2022-05-24T07:47:26: PM2 error: Error: No matching pid found
2022-05-24T07:47:57: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:47:57: PM2 error: Error caught while calling pidusage
2022-05-24T07:47:57: PM2 error: Error: No matching pid found
2022-05-24T07:48:27: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:48:27: PM2 error: Error caught while calling pidusage
2022-05-24T07:48:27: PM2 error: Error: No matching pid found
2022-05-24T07:48:57: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:48:57: PM2 error: Error caught while calling pidusage
2022-05-24T07:48:57: PM2 error: Error: No matching pid found
2022-05-24T07:49:27: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:49:27: PM2 error: Error caught while calling pidusage
2022-05-24T07:49:27: PM2 error: Error: No matching pid found
2022-05-24T07:49:57: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:49:57: PM2 error: Error caught while calling pidusage
2022-05-24T07:49:57: PM2 error: Error: No matching pid found
2022-05-24T07:50:27: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:50:27: PM2 error: Error caught while calling pidusage
2022-05-24T07:50:27: PM2 error: Error: No matching pid found
2022-05-24T07:50:57: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:50:57: PM2 error: Error caught while calling pidusage
2022-05-24T07:50:57: PM2 error: Error: No matching pid found
2022-05-24T07:51:27: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:51:27: PM2 error: Error caught while calling pidusage
2022-05-24T07:51:27: PM2 error: Error: No matching pid found
2022-05-24T07:51:57: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:51:57: PM2 error: Error caught while calling pidusage
2022-05-24T07:51:57: PM2 error: Error: No matching pid found
2022-05-24T07:52:27: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:52:27: PM2 error: Error caught while calling pidusage
2022-05-24T07:52:27: PM2 error: Error: No matching pid found
2022-05-24T07:52:57: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:52:57: PM2 error: Error caught while calling pidusage
2022-05-24T07:52:57: PM2 error: Error: No matching pid found
2022-05-24T07:53:27: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2022-05-24T07:53:27: PM2 error: Error caught while calling pidusage
2022-05-24T07:53:27: PM2 error: Error: No matching pid found
2022-05-24T07:53:46: PM2 log: pm2 has been killed by signal, dumping process list before exit...
2022-05-24T07:53:46: PM2 log: Deleting process 0
2022-05-24T07:53:46: PM2 log: Stopping app:index id:0
2022-05-24T07:53:46: PM2 error: Error: spawn ps ENOENT
2022-05-24T07:53:46: PM2 log: App [index:0] exited with code [0] via signal [SIGTERM]
2022-05-24T07:53:46: PM2 log: pid=8885 msg=process killed
2022-05-24T07:53:46: PM2 log: Exited peacefully
soyuka commented 1 year ago

What is your OS ? Weird you don't have getconf I'd recommend switching to usePs: true somehow.