What I supposed to do with a long time no response Ansible playbook process?

[tivon zhang]

Hi guys,

I just start to use Ansible to provision my environment, the playbook yml is from my partner and it's undoubtedly workable.

Unfortunately, I have been trapped here for 14 hours with no more response: 

TASK [common : Install NodeJS 4.2.4] *******************************************

I guess I should kill the current process and add some log option to restart it. My questions:

1. Is there a way to check the current running ansible's status?

2. I guess ansible has already downloaded some files of nodejs, should I found and delete them for next clear installation?

Thanks!

[jpea...@sparkpost.com]

On Friday, July 15, 2016 at 7:59:19 PM UTC-4, tivon zhang wrote:

Unfortunately, I have been trapped here for 14 hours with no more response: 

TASK [common : Install NodeJS 4.2.4] *******************************************

I'll bet if you ran that same command in a shell yourself, it would be prompted for something (like 'Y').

John

[rup]

To find current process, run this to get PID to kill:

     ps -ef|grep ansible

A command I use to watch Ansible processes as they are running is:

     watch -n 3 'netstat -ta | egrep ":ssh +EST"'

So I can follow along with what's being run.

Kim