Score:0

PM2 - Process or Namespace not found when deploying with GitLab CI

ge flag

When deploying from CI, as the user who started PM2, pm2 restart appname always results in [PM2][ERROR] Process or Namespace appname not found

whoami/who on deployment shows the correct user.

Tried switching users, as well as PM2's location: /usr/local/bin/pm2 restart appname results in the same process not found.

CI command:

script:
- pm2 restart appname

or:

deploy: 'ssh -o StrictHostKeyChecking=no $DEPLOY_USER@$DEPLOY_IP "pm2 restart appname"'
script:
- "eval $deploy"
Klav avatar
ge flag
killing the processes via ssh, then ```pm2 restart ecosystem.config.js``` via CI, did the trick
Score:0
kn flag

If you receive [PM2][ERROR] Script not found: /root/appname

Run the following first: pm2 start npm --name "appname" -- run "start:dev"

Then, see/run above from Debapriya Das, pm2 start appname and pm2 save

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.