Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PM2 won't start at initial deploy #19

Closed
xcambar opened this issue Aug 3, 2017 · 14 comments · May be fixed by #20
Closed

PM2 won't start at initial deploy #19

xcambar opened this issue Aug 3, 2017 · 14 comments · May be fixed by #20
Labels
help wanted

Comments

@xcambar
Copy link

xcambar commented Aug 3, 2017

Hi,

I've noticed that, with my setup (below), during the initial deployment, the execution of the update PM2 handler stops the process but does not restart it.

I don't really know what to do with it, except ask for your help :)

Maybe you will find some piece of relevant info below, or event better, reproduce the situation...

Here's the info:

ansible-pm2 config:

pm2_apps:
  - run: pm2.config.js
    path: /opt/
    env: '{{ app_secrets }}'
pm2_service_name: pm2-root

The relevant ansible logs:

2017-08-03 18:52:24,732 p=39088 u=xav |  TASK [weareinteractive.pm2 : Install packages] ***************************************************************************************************************
2017-08-03 18:52:46,420 p=39088 u=xav |  changed: [REDACTED_IP]
2017-08-03 18:52:46,440 p=39088 u=xav |  TASK [weareinteractive.pm2 : Looking up user home] ***********************************************************************************************************
2017-08-03 18:52:47,486 p=39088 u=xav |  ok: [REDACTED_IP]
2017-08-03 18:52:47,497 p=39088 u=xav |  TASK [weareinteractive.pm2 : Installing startup script] ******************************************************************************************************
2017-08-03 18:52:51,763 p=39088 u=xav |  changed: [REDACTED_IP]
2017-08-03 18:52:51,776 p=39088 u=xav |  TASK [weareinteractive.pm2 : Executing commands] *************************************************************************************************************
2017-08-03 18:52:54,011 p=39088 u=xav |  changed: [REDACTED_IP] => (item={u'run': u'delete all'})
2017-08-03 18:52:54,026 p=39088 u=xav |  TASK [weareinteractive.pm2 : Managing apps] ******************************************************************************************************************
2017-08-03 18:52:56,383 p=39088 u=xav |  changed: [REDACTED_IP] => (item={u'path': u'/opt/', u'run': u'pm2.config.js', u'env': {REDACTED}})
2017-08-03 18:52:56,392 p=39088 u=xav |  TASK [weareinteractive.pm2 : Configuring service] ************************************************************************************************************
2017-08-03 18:52:57,830 p=39088 u=xav |  ok: [REDACTED_IP]
2017-08-03 18:52:57,832 p=39088 u=xav |  RUNNING HANDLER [weareinteractive.pm2 : update pm2] **********************************************************************************************************
2017-08-03 18:53:03,102 p=39088 u=xav |  changed: [REDACTED_IP]
2017-08-03 18:53:03,105 p=39088 u=xav |  PLAY RECAP ***************************************************************************************************************************************************
2017-08-03 18:53:03,106 p=39088 u=xav |  138.197.191.239            : ok=53   changed=42   unreachable=0    failed=0

And a slice of Syslog to complete:

Aug  3 16:52:54 digitalocean ansible-command: Invoked with warn=True executable=None chdir=/opt/ _raw_params=pm2 start pm2.config.js  removes=None creates=None _uses_shell=True
Aug  3 16:52:57 digitalocean ansible-systemd: Invoked with no_block=False name=pm2-root enabled=True daemon_reload=False state=started user=False masked=None
Aug  3 16:52:58 digitalocean ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=pm2 updatePM2 removes=None creates=None chdir=None
Aug  3 16:53:00 digitalocean systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Aug  3 16:53:02 digitalocean pm2[20673]: [PM2] Stopping PM2...
Aug  3 16:53:02 digitalocean pm2[20673]: [PM2] Applying action deleteProcessId on app [all](ids: 0,1)
Aug  3 16:53:03 digitalocean pm2[20673]: [PM2] [robert](0) ✓
Aug  3 16:53:03 digitalocean pm2[20673]: [PM2] [valid-users](1) ✓
Aug  3 16:53:03 digitalocean pm2[20673]: [PM2] All processes have been stopped and deleted
Aug  3 16:53:03 digitalocean pm2[20673]: [PM2] PM2 stopped
Aug  3 16:59:38 digitalocean systemd[1]: Starting Cleanup of Temporary Directories...
@xcambar xcambar mentioned this issue Aug 3, 2017
Open
@franklinkim
Copy link
Member

Hi,

I looked in to this but I think this one might be pm2 related:
I provisioned the vagrant box with notify updatecommented out, sshed into the box and ran the update command manually. Somehow pm2 can't restart the processes correctly on first update. I resurrected them and updated again => works fine

Would be great if you could take the time and report this at pm2.

The full process looks like:

  1. Provision (with notify updatecommented out)
root@ubuntu-xenial:/home/ubuntu# pm2 l
┌───────────────┬────┬──────┬───────┬────────┬─────────┬────────┬─────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid   │ status │ restart │ uptime │ cpu │ mem       │ user │ watching │
├───────────────┼────┼──────┼───────┼────────┼─────────┼────────┼─────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 14040 │ online │ 0       │ 9m     │ 0%  │ 25.7 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 13986 │ online │ 0       │ 9m     │ 0%  │ 25.6 MB   │ root │ disabled │
└───────────────┴────┴──────┴───────┴────────┴─────────┴────────┴─────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
  1. Run update
root@ubuntu-xenial:/home/ubuntu# pm2 update
Be sure to have the latest version by doing `npm install pm2@latest -g` before doing this procedure.
[PM2] Saving current process list...
[PM2] Stopping PM2...
[PM2] Applying action deleteProcessId on app [all](ids: 0,1)
[PM2] [console_log](0) ✓
[PM2] [console_error](1) ✓
[PM2] All processes have been stopped and deleted
[PM2] PM2 stopped
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] Restoring processes located in /root/.pm2/dump.pm2
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_log.js restored
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_error.js restored
>>>>>>>>>> PM2 updated
┌───────────────┬────┬──────┬───────┬────────┬─────────┬────────┬─────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid   │ status │ restart │ uptime │ cpu │ mem       │ user │ watching │
├───────────────┼────┼──────┼───────┼────────┼─────────┼────────┼─────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 14879 │ online │ 0       │ 0s     │ 66% │ 22.7 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 14874 │ online │ 0       │ 0s     │ 37% │ 20.9 MB   │ root │ disabled │
└───────────────┴────┴──────┴───────┴────────┴─────────┴────────┴─────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
  1. List
root@ubuntu-xenial:/home/ubuntu# pm2 ls
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] PM2 Successfully daemonized
┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────┬──────────┐
│ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
└──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
  1. Resurrect previously dumped processes
root@ubuntu-xenial:/home/ubuntu# pm2 resurrect
[PM2] Resurrecting
[PM2] Restoring processes located in /root/.pm2/dump.pm2
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_log.js restored
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_error.js restored
┌───────────────┬────┬──────┬───────┬────────┬─────────┬────────┬──────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid   │ status │ restart │ uptime │ cpu  │ mem       │ user │ watching │
├───────────────┼────┼──────┼───────┼────────┼─────────┼────────┼──────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 14957 │ online │ 0       │ 0s     │ 50%  │ 21.2 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 14952 │ online │ 0       │ 0s     │ 150% │ 21.2 MB   │ root │ disabled │
└───────────────┴────┴──────┴───────┴────────┴─────────┴────────┴──────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
  1. Update again
root@ubuntu-xenial:/home/ubuntu# pm2 update
Be sure to have the latest version by doing `npm install pm2@latest -g` before doing this procedure.
[PM2] Saving current process list...
[PM2] Stopping PM2...
[PM2] Applying action deleteProcessId on app [all](ids: 0,1)
[PM2] [console_error](1) ✓
[PM2] [console_log](0) ✓
[PM2] All processes have been stopped and deleted
[PM2] PM2 stopped
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] Restoring processes located in /root/.pm2/dump.pm2
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_log.js restored
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_error.js restored
>>>>>>>>>> PM2 updated
┌───────────────┬────┬──────┬───────┬────────┬─────────┬────────┬──────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid   │ status │ restart │ uptime │ cpu  │ mem       │ user │ watching │
├───────────────┼────┼──────┼───────┼────────┼─────────┼────────┼──────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 15059 │ online │ 0       │ 0s     │ 33%  │ 20.3 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 15054 │ online │ 0       │ 0s     │ 600% │ 22.7 MB   │ root │ disabled │
└───────────────┴────┴──────┴───────┴────────┴─────────┴────────┴──────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
  1. List
root@ubuntu-xenial:/home/ubuntu# pm2 list
┌───────────────┬────┬──────┬───────┬────────┬─────────┬────────┬─────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid   │ status │ restart │ uptime │ cpu │ mem       │ user │ watching │
├───────────────┼────┼──────┼───────┼────────┼─────────┼────────┼─────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 15059 │ online │ 0       │ 19s    │ 0%  │ 26.6 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 15054 │ online │ 0       │ 19s    │ 0%  │ 26.9 MB   │ root │ disabled │
└───────────────┴────┴──────┴───────┴────────┴─────────┴────────┴─────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

Environment:

ubuntu 16.04
node: v5.12.0
pm2: 2.6.1

@xcambar
Copy link
Author

xcambar commented Aug 4, 2017

Unfortunately, following the same modifications as you did (ie, comment ou the notify: update pm2), I don't get the same results: the PM2 processes are well and alive.

See the following branch so you can (hopefully) reproduce: https://github.com/xcambar/ansible-pm2/tree/test_notify (diff: master...xcambar:test_notify).

After this branch is checked out (and the repo is clean), I run the following:

$ vagrant destroy -f
$ vagrant up
$ vagrant ssh

# in the VM
$ sudo su -
# pm2 ls

IMPORTANT!
The results vary whether you run sudo pm2 ls or is you login as root (sudo su -) then do a pm2 ls. This is mostly due to the way PM2 handles users. This is unfortunately misleading.

@xcambar
Copy link
Author

xcambar commented Aug 4, 2017 •
edited
Loading

As a side note, the configuration in the PR only works if the folder of the module/repository is named weareinteractive.pm2 instead of the default ansible-pm2.

@franklinkim
Copy link
Member

Hi, yeah, you need to switch to the root user to see the apps running.
So what do you see after running pm2 ls? You're seeing the running apps, right?
This would be step 1 in my description above. Please continue from there.

@xcambar
Copy link
Author

xcambar commented Aug 4, 2017

Sorry, I was unclear: I went through step 2 and 3 as well, and step 3 is where it differs.

Here's step 1: initial ls

vagrant@vagrant-ubuntu-trusty-64:~$ sudo su -
root@vagrant-ubuntu-trusty-64:~# pm2 ls
┌───────────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid  │ status │ restart │ uptime │ cpu │ mem       │ user │ watching │
├───────────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 4044 │ online │ 0       │ 6m     │ 0%  │ 17.9 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 4005 │ online │ 0       │ 6m     │ 0%  │ 17.9 MB   │ root │ disabled │
└───────────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

Step 2: update

root@vagrant-ubuntu-trusty-64:~# pm2 updatePM2
Be sure to have the latest version by doing `npm install pm2@latest -g` before doing this procedure.
[PM2] Saving current process list...
[PM2] Stopping PM2...
[PM2] Applying action deleteProcessId on app [all](ids: 0,1)
[PM2] [console_log](0) ✓
[PM2] [console_error](1) ✓
[PM2] All processes have been stopped and deleted
[PM2] PM2 stopped
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] Restoring processes located in /root/.pm2/dump.pm2
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_log.js restored
[PM2] Process /etc/ansible/roles/weareinteractive.pm2/tests/apps/console_error.js restored
>>>>>>>>>> PM2 updated
┌───────────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid  │ status │ restart │ uptime │ cpu │ mem       │ user │ watching │
├───────────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 4239 │ online │ 0       │ 0s     │ 28% │ 13.7 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 4234 │ online │ 0       │ 0s     │ 5%  │ 14.2 MB   │ root │ disabled │
└───────────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

Step 3: list applications

root@vagrant-ubuntu-trusty-64:~# pm2 ls
┌───────────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬───────────┬──────┬──────────┐
│ App name      │ id │ mode │ pid  │ status │ restart │ uptime │ cpu │ mem       │ user │ watching │
├───────────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼───────────┼──────┼──────────┤
│ console_error │ 1  │ fork │ 4239 │ online │ 0       │ 33s    │ 0%  │ 17.4 MB   │ root │ disabled │
│ console_log   │ 0  │ fork │ 4234 │ online │ 0       │ 33s    │ 0%  │ 17.4 MB   │ root │ disabled │
└───────────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴───────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

Hope this helps!

@xcambar
Copy link
Author

xcambar commented Aug 4, 2017 •
edited
Loading

Here are the system infos from the VM:

root@vagrant-ubuntu-trusty-64:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty
root@vagrant-ubuntu-trusty-64:~# uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-125-generic #174-Ubuntu SMP Mon Jul 10 18:51:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@vagrant-ubuntu-trusty-64:~# node -v
v5.12.0
root@vagrant-ubuntu-trusty-64:~# npm -v
3.8.6
root@vagrant-ubuntu-trusty-64:~# pm2 -v
2.6.1

@franklinkim
Copy link
Member

ah ok, that helps. so currently the only difference would be the ubuntu distribution. I updated my box to xenial. what system are u running where the actual problem occured? trusty or xenial?

@xcambar
Copy link
Author

xcambar commented Aug 4, 2017 •
edited
Loading

trusty, as per the Vagrantfile.

@xcambar
Copy link
Author

xcambar commented Aug 4, 2017

Debian Stretch 8.9 and 9.1

@franklinkim
Copy link
Member

ok, I added the stretch box:

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vbguest.no_remote = true

  config.vm.define 'xenial' do |instance|
    instance.vm.box = 'ubuntu/xenial64'
  end

  config.vm.define 'stretch' do |instance|
    instance.vm.box = 'debian/stretch64'
  end

  config.vm.provision "shell", inline: "sudo apt-get update"
  config.vm.provision "shell", inline: "sudo apt-get install -y python"
  config.vm.synced_folder '.', '/etc/ansible/roles/weareinteractive.pm2'

  # View the documentation for the provider you're using for more
  # information on available options.
  config.vm.provision "ansible" do |ansible|
    ansible.playbook = "tests/main.yml"
    ansible.verbose = 'vv'
    ansible.sudo = true
  end
end

uses:

$ vagrant up stretch
$ vagrant ssh stretch

and now I have the same behaviour as described above:

Seems this is related to ubuntu xenial and at least debian stretch

@franklinkim
Copy link
Member

So here's the pm2.log which shows that after running pm2 update it somehow stops and restarts again but without loading the applications...

2017-08-04 12:52:34: ===============================================================================
2017-08-04 12:52:34: --- New PM2 Daemon started ----------------------------------------------------
2017-08-04 12:52:34: Time                 : Fri Aug 04 2017 12:52:34 GMT+0000 (GMT)
2017-08-04 12:52:34: PM2 version          : 2.6.1
2017-08-04 12:52:34: Node.js version      : 5.12.0
2017-08-04 12:52:34: Current arch         : x64
2017-08-04 12:52:34: PM2 home             : /root/.pm2
2017-08-04 12:52:34: PM2 PID file         : /root/.pm2/pm2.pid
2017-08-04 12:52:34: RPC socket file      : /root/.pm2/rpc.sock
2017-08-04 12:52:34: BUS socket file      : /root/.pm2/pub.sock
2017-08-04 12:52:34: Application log path : /root/.pm2/logs
2017-08-04 12:52:34: Process dump file    : /root/.pm2/dump.pm2
2017-08-04 12:52:34: Concurrent actions   : 2
2017-08-04 12:52:34: SIGTERM timeout      : 1600
2017-08-04 12:52:34: ===============================================================================
2017-08-04 12:52:36: Starting execution sequence in -fork mode- for app name:console_log id:0
2017-08-04 12:52:36: App name:console_log id:0 online
2017-08-04 12:52:36: Starting execution sequence in -fork mode- for app name:console_error id:1
2017-08-04 12:52:36: App name:console_error id:1 online

Running pm2 update:

2017-08-04 13:04:18: 0
2017-08-04 13:04:18: Stopping app:console_log id:0
2017-08-04 13:04:18: 1
2017-08-04 13:04:18: Stopping app:console_error id:1
2017-08-04 13:04:18: App [console_log] with id [0] and pid [10126], exited with code [0] via signal [SIGINT]
2017-08-04 13:04:18: [HandleExit] PM2 is being killed, stopping restart procedure...
2017-08-04 13:04:18: App [console_error] with id [1] and pid [10165], exited with code [0] via signal [SIGINT]
2017-08-04 13:04:18: [HandleExit] PM2 is being killed, stopping restart procedure...
2017-08-04 13:04:18: pid=10126 msg=process killed
2017-08-04 13:04:18: pid=10165 msg=process killed
2017-08-04 13:04:19: ===============================================================================
2017-08-04 13:04:19: --- Stopping PM2 --------------------------------------------------------------
2017-08-04 13:04:19: Time                 : Fri Aug 04 2017 13:04:19 GMT+0000 (GMT)
2017-08-04 13:04:19: ===============================================================================
2017-08-04 13:04:19: RPC closed
2017-08-04 13:04:19: PUB closed
2017-08-04 13:04:19: PM2 successfully stopped
2017-08-04 13:04:19: ===============================================================================
2017-08-04 13:04:19: --- New PM2 Daemon started ----------------------------------------------------
2017-08-04 13:04:19: Time                 : Fri Aug 04 2017 13:04:19 GMT+0000 (GMT)
2017-08-04 13:04:19: PM2 version          : 2.6.1
2017-08-04 13:04:19: Node.js version      : 5.12.0
2017-08-04 13:04:19: Current arch         : x64
2017-08-04 13:04:19: PM2 home             : /root/.pm2
2017-08-04 13:04:19: PM2 PID file         : /root/.pm2/pm2.pid
2017-08-04 13:04:19: RPC socket file      : /root/.pm2/rpc.sock
2017-08-04 13:04:19: BUS socket file      : /root/.pm2/pub.sock
2017-08-04 13:04:19: Application log path : /root/.pm2/logs
2017-08-04 13:04:19: Process dump file    : /root/.pm2/dump.pm2
2017-08-04 13:04:19: Concurrent actions   : 2
2017-08-04 13:04:19: SIGTERM timeout      : 1600
2017-08-04 13:04:19: ===============================================================================
2017-08-04 13:04:19: Starting execution sequence in -fork mode- for app name:console_log id:0
2017-08-04 13:04:19: Starting execution sequence in -fork mode- for app name:console_error id:1
2017-08-04 13:04:19: App name:console_log id:0 online
2017-08-04 13:04:19: App name:console_error id:1 online
2017-08-04 13:04:19: 0
2017-08-04 13:04:19: Stopping app:console_log id:0
2017-08-04 13:04:19: 1
2017-08-04 13:04:19: Stopping app:console_error id:1
2017-08-04 13:04:19: App [console_log] with id [0] and pid [10303], exited with code [0] via signal [SIGINT]
2017-08-04 13:04:19: [HandleExit] PM2 is being killed, stopping restart procedure...
2017-08-04 13:04:19: App [console_error] with id [1] and pid [10308], exited with code [0] via signal [SIGINT]
2017-08-04 13:04:19: [HandleExit] PM2 is being killed, stopping restart procedure...
2017-08-04 13:04:19: pid=10303 msg=process killed
2017-08-04 13:04:19: pid=10308 msg=process killed
2017-08-04 13:04:19: ===============================================================================
2017-08-04 13:04:19: --- Stopping PM2 --------------------------------------------------------------
2017-08-04 13:04:19: Time                 : Fri Aug 04 2017 13:04:19 GMT+0000 (GMT)
2017-08-04 13:04:19: ===============================================================================
2017-08-04 13:04:19: RPC closed
2017-08-04 13:04:19: PUB closed
2017-08-04 13:04:19: PM2 successfully stopped
2017-08-04 13:04:23: ===============================================================================
2017-08-04 13:04:23: --- New PM2 Daemon started ----------------------------------------------------
2017-08-04 13:04:23: Time                 : Fri Aug 04 2017 13:04:23 GMT+0000 (GMT)
2017-08-04 13:04:23: PM2 version          : 2.6.1
2017-08-04 13:04:23: Node.js version      : 5.12.0
2017-08-04 13:04:23: Current arch         : x64
2017-08-04 13:04:23: PM2 home             : /root/.pm2
2017-08-04 13:04:23: PM2 PID file         : /root/.pm2/pm2.pid
2017-08-04 13:04:23: RPC socket file      : /root/.pm2/rpc.sock
2017-08-04 13:04:23: BUS socket file      : /root/.pm2/pub.sock
2017-08-04 13:04:23: Application log path : /root/.pm2/logs
2017-08-04 13:04:23: Process dump file    : /root/.pm2/dump.pm2
2017-08-04 13:04:23: Concurrent actions   : 2
2017-08-04 13:04:23: SIGTERM timeout      : 1600
2017-08-04 13:04:23: ===============================================================================

@xcambar
Copy link
Author

xcambar commented Aug 5, 2017

I'll take some time to try and see the behaviour manually (no Ansible) to confirm the results.

What would be your suggestion for the next steps?

@franklinkim
Copy link
Member

franklinkim commented Aug 7, 2017 •
edited
Loading

Next steps would be:

• If you can confirm this manually, it's probably a bug and needs to be reported / fixed by pm2 (this actually means, that this role works as it should and you should add a workaround like calling pm2 resurrect in your playbook till it got fixed)

• If it's not a but, we'll have to figure out why this is ansible related.

@franklinkim
Copy link
Member

Closing this due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ensures that the update of PM2 occurs right after install xcambar/ansible-pm2
2 participants
@franklinkim @xcambar