error when installing apache on ubuntu

1,309 views
Skip to first unread message

Daley Okuwa

unread,
Jun 1, 2017, 2:16:49 PM6/1/17
to Ansible Project
This is my playbook apache.yml
---
- hosts: all
  tasks:
    - name:  install apache2
      apt: name=apache2 state=present update_cache=yes


This is my command including specifying su

ansible-playbook -u dokuwa1 --ask-pass  --become-method=su --ask-su-pass playbook/apache.yml


error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "cmd": "apt-get update", "failed": true, "msg": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)\nE: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)\nE: Unable to lock the administration directory (/var/lib/dpkg/), are you root?", "rc": 100, "stderr": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches 

This is obvious a permission issue of sudo 

Matt Martz

unread,
Jun 1, 2017, 2:28:38 PM6/1/17
to ansible...@googlegroups.com
--become-method does not imply that ansible should actually "become"

You will also need to add `--become`

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7dbc2826-d974-414b-b5a9-e22dc3fff0c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Matt Martz
@sivel
sivel.net

Daley Okuwa

unread,
Jun 1, 2017, 2:59:33 PM6/1/17
to ansible...@googlegroups.com
Matt,

Thanks

I now used this command 
ansible-playbook -u dokuwa1 --ask-pass  --become  playbook/apache.yml

i get another error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 192.168.85.129 closed.\r\n", "module_stdout": "sudo: a password is required\r\n", "msg": "MODULE FAILURE", "rc": 1}
 [WARNING]: Could not create retry file '/etc/ansible/playbook/apache.retry'.
[Errno 13] Permission denied: u'/etc/ansible/playbook/apache.retry'


Is there anything i am doing wrong 

Daley

From: Matt Martz <ma...@sivel.net>
To: ansible...@googlegroups.com
Sent: Thursday, 1 June 2017, 19:28
Subject: Re: [ansible-project] error when installing apache on ubuntu

Matt Martz

unread,
Jun 1, 2017, 3:05:33 PM6/1/17
to ansible...@googlegroups.com
You initially had --become-method=su and --ask-su-pass

You needed to additionally specify --become

So (using the newer param):

ansible-playbook -u dokuwa1 --ask-pass --become-method=su --ask-become-pass --become playbook/apache.yml

On Thu, Jun 1, 2017 at 1:59 PM, 'Daley Okuwa' via Ansible Project <ansible...@googlegroups.com> wrote:
Matt,

Thanks

I now used this command 
ansible-playbook -u dokuwa1 --ask-pass  --become  playbook/apache.yml

i get another error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 192.168.85.129 closed.\r\n", "module_stdout": "sudo: a password is required\r\n", "msg": "MODULE FAILURE", "rc": 1}
 [WARNING]: Could not create retry file '/etc/ansible/playbook/apache.retry'.
[Errno 13] Permission denied: u'/etc/ansible/playbook/apache.retry'


Is there anything i am doing wrong 

Daley

From: Matt Martz <ma...@sivel.net>
Sent: Thursday, 1 June 2017, 19:28
Subject: Re: [ansible-project] error when installing apache on ubuntu
--become-method does not imply that ansible should actually "become"

You will also need to add `--become`
On Thu, Jun 1, 2017 at 1:16 PM 'Daley Okuwa' via Ansible Project <ansible-project@googlegroups.com> wrote:
This is my playbook apache.yml
---
- hosts: all
  tasks:
    - name:  install apache2
      apt: name=apache2 state=present update_cache=yes


This is my command including specifying su

ansible-playbook -u dokuwa1 --ask-pass  --become-method=su --ask-su-pass playbook/apache.yml


error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "cmd": "apt-get update", "failed": true, "msg": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)\nE: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)\nE: Unable to lock the administration directory (/var/lib/dpkg/), are you root?", "rc": 100, "stderr": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches 

This is obvious a permission issue of sudo 

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
--
Matt Martz
@sivel
sivel.net
--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.


--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/436988991.1205471.1496343552387%40mail.yahoo.com.

For more options, visit https://groups.google.com/d/optout.

Daley Okuwa

unread,
Jun 1, 2017, 3:30:39 PM6/1/17
to ansible...@googlegroups.com
Hello Matt,

i now got this error message again


PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [192.168.85.129]: FAILED! => {"failed": true, "msg": "Timeout (12s) waiting for privilege escalation prompt: "}
 [WARNING]: Could not create retry file '/etc/ansible/playbook/apache.retry'.
[Errno 13] Permission denied: u'/etc/ansible/playbook/apache.retry'

thanks


From: Matt Martz <ma...@sivel.net>
To: "ansible...@googlegroups.com" <ansible...@googlegroups.com>
Sent: Thursday, 1 June 2017, 20:05

Subject: Re: [ansible-project] error when installing apache on ubuntu
You initially had --become-method=su and --ask-su-pass

You needed to additionally specify --become

So (using the newer param):

ansible-playbook -u dokuwa1 --ask-pass --become-method=su --ask-become-pass --become playbook/apache.yml
On Thu, Jun 1, 2017 at 1:59 PM, 'Daley Okuwa' via Ansible Project <ansible...@googlegroups.com> wrote:
Matt,

Thanks

I now used this command 
ansible-playbook -u dokuwa1 --ask-pass  --become  playbook/apache.yml

i get another error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 192.168.85.129 closed.\r\n", "module_stdout": "sudo: a password is required\r\n", "msg": "MODULE FAILURE", "rc": 1}
 [WARNING]: Could not create retry file '/etc/ansible/playbook/apache. retry'.
[Errno 13] Permission denied: u'/etc/ansible/playbook/ apache.retry'


Is there anything i am doing wrong 

Daley

From: Matt Martz <ma...@sivel.net>
To: ansible-project@googlegroups. com
Sent: Thursday, 1 June 2017, 19:28
Subject: Re: [ansible-project] error when installing apache on ubuntu
--become-method does not imply that ansible should actually "become"

You will also need to add `--become`
On Thu, Jun 1, 2017 at 1:16 PM 'Daley Okuwa' via Ansible Project <ansible-project@googlegroups. com> wrote:
This is my playbook apache.yml
---
- hosts: all
  tasks:
    - name:  install apache2
      apt: name=apache2 state=present update_cache=yes


This is my command including specifying su

ansible-playbook -u dokuwa1 --ask-pass  --become-method=su --ask-su-pass playbook/apache.yml


error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "cmd": "apt-get update", "failed": true, "msg": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)\nE: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)\nE: Unable to lock the administration directory (/var/lib/dpkg/), are you root?", "rc": 100, "stderr": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/ srcpkgcache.bin - RemoveCaches 

This is obvious a permission issue of sudo 

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@ googlegroups.com.
To post to this group, send email to ansible-project@googlegroups. com.
To view this discussion on the web visit https://groups.google.com/d/ msgid/ansible-project/ 7dbc2826-d974-414b-b5a9- e22dc3fff0c4%40googlegroups. com.
For more options, visit https://groups.google.com/d/ optout.
--
Matt Martz
@sivel
sivel.net
--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@ googlegroups.com.
To post to this group, send email to ansible-project@googlegroups. com.

For more options, visit https://groups.google.com/d/ optout.
--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@ googlegroups.com.
To post to this group, send email to ansible-project@googlegroups. com.

For more options, visit https://groups.google.com/d/ optout.



--
Matt Martz
@sivel
sivel.net
--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAD8N0v-O_b5XkaweY_Y_8LWNjGxWkmAkzKOpcO-hqC%2B39-%2Bo2Q%40mail.gmail.com.

Arvind Thatikonda

unread,
Nov 26, 2018, 10:13:54 AM11/26/18
to Ansible Project
Dear Friends,

I am new to ansible, just started to get my hands dirty with the playbooks, I am trying to install apache on ubuntu client machine. I am facing same issue in the email chain.


[DEPRECATION WARNING]: DEFAULT_SUDO_USER option, In favor of Ansible Become, which is a generic framework. 

See become_user. , use become instead. This feature will be removed in version 2.8. Deprecation warnings can

 be disabled by setting deprecation_warnings=False in ansible.cfg.


PLAY [client] ***********************************************************************************************


TASK [Gathering Facts] **************************************************************************************

fatal: [x.x.x.x]: FAILED! => {"changed": false, "module_stderr": "Shared connection to x.x.x.x closed.\r\n", "module_stdout": "sudo: a password is required\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

to retry, use: --limit @/home/ansible/playbooks/apache.retry


PLAY RECAP **************************************************************************************************

x.x.x.x                 : ok=0    changed=0    unreachable=0    failed=1   

Can someone please clarify what is the issue? 


here is my code :

--- # Plyabook Apache install on client

- hosts: client

  user: ansible

  become: yes

  become_method: sudo

  connection: ssh

  gather_facts: yes

  tasks:

  - name: install apache on client machine

    yum:

      name: apache2

      state: present

      update_cache: yes

Sent: Thursday, 1 June 2017, 19:28
Subject: Re: [ansible-project] error when installing apache on ubuntu
--become-method does not imply that ansible should actually "become"

You will also need to add `--become`
On Thu, Jun 1, 2017 at 1:16 PM 'Daley Okuwa' via Ansible Project <ansible...@googlegroups. com> wrote:
This is my playbook apache.yml
---
- hosts: all
  tasks:
    - name:  install apache2
      apt: name=apache2 state=present update_cache=yes


This is my command including specifying su

ansible-playbook -u dokuwa1 --ask-pass  --become-method=su --ask-su-pass playbook/apache.yml


error message 

fatal: [192.168.85.129]: FAILED! => {"changed": false, "cmd": "apt-get update", "failed": true, "msg": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)\nE: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)\nE: Unable to lock the administration directory (/var/lib/dpkg/), are you root?", "rc": 100, "stderr": "W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)\nE: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)\nE: Unable to lock directory /var/lib/apt/lists/\nW: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)\nW: Problem unlinking the file /var/cache/apt/ srcpkgcache.bin - RemoveCaches 

This is obvious a permission issue of sudo 

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@ googlegroups.com.
To post to this group, send email to ansible...@googlegroups. com.
--
Matt Martz
@sivel
sivel.net
--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@ googlegroups.com.
To post to this group, send email to ansible...@googlegroups. com.


--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@ googlegroups.com.
To post to this group, send email to ansible...@googlegroups. com.



--
Matt Martz
@sivel
sivel.net

John Foley

unread,
Nov 26, 2018, 12:20:56 PM11/26/18
to Ansible Project
First off, it looks like you have a sudo problem. Either you need to configure passwordless sudo on the target marchine, or you need to add a -K  to the ansible-playbook command to have it prompt for the become password.

Also, you are using the yum module for what you say is a Ubuntu host. You should be using the apt module.

Arvind Thatikonda

unread,
Nov 26, 2018, 6:54:37 PM11/26/18
to ansible...@googlegroups.com
Thanks John for your reply 
I did setup passwordless ssh connection to the client. 

I added the below line on both ansible server and client  in visudo file
ansible ALL=(ALL)  NOPASSWD: ALL

Is that correct?

Thanks for correcting me about the yum statement. I will change. 

Where do you want me to use -K to prompt for password in the playbook? 


To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/2dcb4ec1-c193-4dea-8896-39aacc21ce88%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
Thanks & Regards,
Arvind;

ameya agashe

unread,
Nov 26, 2018, 7:24:20 PM11/26/18
to ansible...@googlegroups.com
John might be able to rectify me if I am wrong. You can put it anywhere as long as its present after -K switch or --ask-become-pass.

Always good idea to execute ansible-playbook command to see different options/switches.

Kind Regards,
Ameya Agashe

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAPiXTetc4t5Gdui9h57HED6O0rDY%2BR3dFZ5bv2MSU5%2BnGPECNQ%40mail.gmail.com.

Arvind Thatikonda

unread,
Nov 26, 2018, 7:47:24 PM11/26/18
to ansible...@googlegroups.com
thanks Ameya, I used it after ansible-playbook -K , it promoted for Sudo Password , so I entered my 'ansible' user password 
but I get same error 
DEPRECATION WARNING]: DEFAULT_SUDO_USER option, In favor of Ansible Become, which is a generic framework. 
See become_user. , use become instead. This feature will be removed in version 2.8. Deprecation warnings can
 be disabled by setting deprecation_warnings=False in ansible.cfg.
SUDO password: 


PLAY [client] ***********************************************************************************************

TASK [Gathering Facts] **************************************************************************************
fatal: [x.x.x.x]: FAILED! => {"changed": false, "module_stderr": "Shared connection to x.x.x.x closed.\r\n", "module_stdout": "\r\nansible is not in the sudoers file.  This incident will be reported.\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

to retry, use: --limit @/home/ansible/playbooks/apache.retry

PLAY RECAP **************************************************************************************************
x.x.x.x             : ok=0    changed=0    unreachable=0    failed=1
I am trying to install apache on client node 10.138.0.7 
I have setup ansible user on both server and client
when it promoted for password I entered my ansible user password
I don't think it is asking for the root password
 

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAG9tf-9cdaTQ67RSqv60KEdwbOm%3D9a%3D0OmE-yj5s%3DXX%3DLH7u7w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Arvind Thatikonda

unread,
Nov 26, 2018, 7:51:48 PM11/26/18
to ansible...@googlegroups.com
here is the complete log -vvv debug option : 


<10.138.0.7> ESTABLISH SSH CONNECTION FOR USER: None

<10.138.0.7> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/ansible/.ansible/cp/4a2f76bb9f 10.138.0.7 '/bin/sh -c '"'"'echo ~ && sleep 0'"'"''

<10.138.0.7> (0, '/home/ansible\n', '')

<10.138.0.7> ESTABLISH SSH CONNECTION FOR USER: None

<10.138.0.7> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/ansible/.ansible/cp/4a2f76bb9f 10.138.0.7 '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430 `" && echo ansible-tmp-1543279730.75-165337335093430="` echo /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430 `" ) && sleep 0'"'"''

<10.138.0.7> (0, 'ansible-tmp-1543279730.75-165337335093430=/home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430\n', '')

Using module file /usr/lib/python2.7/dist-packages/ansible/modules/system/setup.py

<10.138.0.7> PUT /home/ansible/.ansible/tmp/ansible-local-2063N2QcuU/tmpCbzUzB TO /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430/AnsiballZ_setup.py

<10.138.0.7> SSH: EXEC sftp -b - -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/ansible/.ansible/cp/4a2f76bb9f '[10.138.0.7]'

<10.138.0.7> (0, 'sftp> put /home/ansible/.ansible/tmp/ansible-local-2063N2QcuU/tmpCbzUzB /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430/AnsiballZ_setup.py\n', '')

<10.138.0.7> ESTABLISH SSH CONNECTION FOR USER: None

<10.138.0.7> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/ansible/.ansible/cp/4a2f76bb9f 10.138.0.7 '/bin/sh -c '"'"'chmod u+x /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430/ /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430/AnsiballZ_setup.py && sleep 0'"'"''

<10.138.0.7> (0, '', '')

<10.138.0.7> ESTABLISH SSH CONNECTION FOR USER: None

<10.138.0.7> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/ansible/.ansible/cp/4a2f76bb9f -tt 10.138.0.7 '/bin/sh -c '"'"'sudo -H -S  -p "[sudo via ansible, key=fdpjpnhuuvzahtoagmnqvudarudpmuyd] password: " -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-fdpjpnhuuvzahtoagmnqvudarudpmuyd; /usr/bin/python /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430/AnsiballZ_setup.py'"'"'"'"'"'"'"'"' && sleep 0'"'"''

<10.138.0.7> (1, '\r\nansible is not in the sudoers file.  This incident will be reported.\r\n', 'Shared connection to 10.138.0.7 closed.\r\n')

<10.138.0.7> ESTABLISH SSH CONNECTION FOR USER: None

<10.138.0.7> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/ansible/.ansible/cp/4a2f76bb9f 10.138.0.7 '/bin/sh -c '"'"'rm -f -r /home/ansible/.ansible/tmp/ansible-tmp-1543279730.75-165337335093430/ > /dev/null 2>&1 && sleep 0'"'"''

<10.138.0.7> (0, '', '')

fatal: [10.138.0.7]: FAILED! => {

    "changed": false, 

    "module_stderr": "Shared connection to 10.138.0.7 closed.\r\n", 

    "module_stdout": "\r\nansible is not in the sudoers file.  This incident will be reported.\r\n", 

    "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", 

    "rc": 1

}

to retry, use: --limit @/home/ansible/playbooks/apache.retry


PLAY RECAP **************************************************************************************************

10.138.0.7                 : ok=0    changed=0    unreachable=0    failed=1 

ameya agashe

unread,
Nov 26, 2018, 8:02:12 PM11/26/18
to ansible...@googlegroups.com
That should be an easy fix. The user "ansible" on the remote machine is not in the sudoers file, fix that and I think you should be fine.

How to update sudoers file:

Kindly let me know how you go.

Kind regards
Ameya Agashe

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAPiXTevJ_vmJ9E613_Qufa%2B-MEJ7WK%3DDpKSGs_cg6jUzxhLL%2Bg%40mail.gmail.com.

Arvind Thatikonda

unread,
Nov 26, 2018, 8:14:25 PM11/26/18
to ansible...@googlegroups.com
Thanks Ameya, for your quick help. Yes that was the issue for it. I was playing around with sudoers file and forgot to change the ansible1 user to ansible



To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAG9tf--1rnZeYZy8hyUE5jR%2BqUJAP-av36qBTcH1%3D0dEhbrSAg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages