PM2 restart app button missing?

Server provisioning and management
#1

Hey there,

it seems pm2 is getting stuck on one of our servers.

How to know?

Any help is very much appreciated

#2

Maybe the following .logs from pm2 can help with this

/opt/pm2/logs/<domain.tld>-error-9.log last 15 lines:
9|front.st |     at WriteStream.<anonymous> (/usr/lib/node_modules/pm2/lib/Utility.js:186:13)
9|front.st |     at WriteStream.emit (events.js:400:28)
9|front.st |     at internal/fs/streams.js:340:12
9|front.st |     at FSReqCallback.oncomplete (fs.js:179:23)
9|front.st | Error: ENOENT: no such file or directory, chdir '/' -> '/home/cleavr/<domain.tld>/current'
9|front.st |     at wrappedChdir (internal/bootstrap/switches/does_own_process_state.js:116:14)
9|front.st |     at process.chdir (internal/worker.js:96:5)
9|front.st |     at /usr/lib/node_modules/pm2/lib/ProcessContainer.js:298:13
9|front.st |     at wrapper (/usr/lib/node_modules/pm2/node_modules/async/internal/once.js:12:16)
9|front.st |     at next (/usr/lib/node_modules/pm2/node_modules/async/waterfall.js:96:20)
9|front.st |     at /usr/lib/node_modules/pm2/node_modules/async/internal/onlyOnce.js:12:16
9|front.st |     at WriteStream.<anonymous> (/usr/lib/node_modules/pm2/lib/Utility.js:186:13)
9|front.st |     at WriteStream.emit (events.js:400:28)
9|front.st |     at internal/fs/streams.js:340:12
9|front.st |     at FSReqCallback.oncomplete (fs.js:179:23)

cleavr@customer-production-shared-01:~$ cd <domain.tld>/
cleavr@customer-production-shared-01:~/<domain.tld>$ ls -l
total 12
lrwxrwxrwx 1 cleavr cleavr   74 Jan 24 09:19 current -> /home/cleavr/<domain.tld>/releases/20220124091909/.nuxt

EDIT:

The above log fixed our “pm2 stuck issue”

But the Status Box is still missing.

1 Like
#3

Hello @sebbler,

We just found out an issue that we believe is hiding the App Status option.

We’ll be quickly rolling out the new changes. In the meantime, you can also restart PM2 by SSHing into the server itself. Do let us know if you want any help with that.

#4

Thank you for this @Houbsi. Sorry about the hiding of App Status, we’ll bring that back in no time. :wink:

#5

Hello @sebbler and @Houbsi,

Due to some reason, we’re not able to deploy the new changes right now. Will probably have to wait a few hours before we make the next deployment since some changes are going through QA/QC.

But if you really need to restart PM2, here’s something that can be helpful:

  1. SSH into the server.
  2. Run pm2 status
  3. Run pm2 restart process_id

process_id is shown while executing pm2 status

We’re extremely sorry for the inconvenience caused because of this.

#6

Hello @sebbler and @Houbsi,

The app status is back to its place.

Thank you.

2 Likes