-
Notifications
You must be signed in to change notification settings - Fork 36
Facebook Community Cellular Manager CLOUD errors = [DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user #20
Comments
I don't think the 'become/sudo' stuff is the cause of your problems, since those are ostensibly just warnings (but we will fix them). What's the output of |
9muir, Thank you for replying. Here is the output for your requested command: ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo vagrant ssh-config db The issues I'm having are the same anyone would have if they simply followed the instructions per https://github.com/facebookincubator/CommunityCellularManager/tree/master/cloud |
What's the command you ran to try to provision the database VM? |
9muir, Your correct I issued the command from the "client" directory mistakenly. But as you can see below, sometimes you HAVE to issue the "sudo" command BEFORE vagrant because not all vagrant commands work alone without "sudo". Per your instructions, I've tried the following commands from the "Cloud" directory: ubuntu@ubuntu:~/CommunityCellularManager/cloud$ sudo vagrant ssh-config db ubuntu@ubuntu:~/CommunityCellularManager/cloud$ vagrant status The home directory you specified is not accessible. The home You specified: /home/ubuntu/.vagrant.d ubuntu@ubuntu:~/CommunityCellularManager/cloud$ sudo vagrant status web aborted (virtualbox) This environment represents multiple VMs. The VMs are all listed ubuntu@ubuntu:~/CommunityCellularManager/cloud$ sudo vagrant up db Bringing machine 'db' up with 'virtualbox' provider... ubuntu@ubuntu:~/CommunityCellularManager/cloud$ sudo vagrant up db --provision Bringing machine 'db' up with 'virtualbox' provider... PLAY [db] ********************************************************************** TASK [Gathering Facts] ********************************************************* PLAY RECAP ********************************************************************* Ansible failed to complete successfully. Any error output should be ubuntu@ubuntu:~/CommunityCellularManager/cloud$ sudo vagrant ssh-config db Host db ubuntu@ubuntu:~/CommunityCellularManager/cloud$ |
One thing to try: you don't usually have to download and install the base OS manually when using Vagrant, so something funky may be happening there. |
Sorry, that comment was meant for your other issue. GitHub not a great mobile UI |
Running vagrant as root is going to cause a lot of weird issues. SSH keys are going to be all over the place and it shouldn't be necessary to do that. |
faced same issue on going through error logs I tried changing in postgres.dev.yml: |
Submit a patch!
…On Wed, Nov 22, 2017 at 11:38 PM, Sagar Sharma ***@***.***> wrote:
faced same issue on going through error logs I tried changing in
*postgres.dev.yml*:
*sudo: yes* to *become : true* ,
and *sudo_user* with *become_user* and this fixed my issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_rn6yK4VTxQEl7VYiPDejsUv8_7fPyks5s5SDdgaJpZM4LTb-F>
.
|
Summary: I encountered this error when setting the cloud VMs up on a new computer. ``` TASK [Add Endaga DB] *********************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OperationalError: FATAL: Peer authentication failed for user "postgres" fatal: [db]: FAILED! => {"changed": false, "msg": "unable to connect to database: FATAL: Peer authentication failed for user \"postgres\"\n"} to retry, use: --limit @/home/sago/Documents/PCARI/DEV3/CCM_20171212/CommunityCellularManager/cloud/ansible/postgres.dev.retry PLAY RECAP ********************************************************************* db : ok=2 changed=1 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again. ``` Replacing sudo/sudo_user with become/become_user fixed this and the DB vm was completed without any hiccups. This is also partially mentioned in #20 Closes #90 Differential Revision: D6544987 Pulled By: 9muir fbshipit-source-id: 20d639a581f9e8fc455d9706282f7a2a3832fa67
Summary: I encountered this error when setting the cloud VMs up on a new computer. ``` TASK [Add Endaga DB] *********************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OperationalError: FATAL: Peer authentication failed for user "postgres" fatal: [db]: FAILED! => {"changed": false, "msg": "unable to connect to database: FATAL: Peer authentication failed for user \"postgres\"\n"} to retry, use: --limit @/home/sago/Documents/PCARI/DEV3/CCM_20171212/CommunityCellularManager/cloud/ansible/postgres.dev.retry PLAY RECAP ********************************************************************* db : ok=2 changed=1 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again. ``` Replacing sudo/sudo_user with become/become_user fixed this and the DB vm was completed without any hiccups. This is also partially mentioned in #20 Closes facebookarchive#90 Differential Revision: D6544987 Pulled By: 9muir fbshipit-source-id: 20d639a581f9e8fc455d9706282f7a2a3832fa67
Summary: I encountered this error when setting the cloud VMs up on a new computer. ``` TASK [Add Endaga DB] *********************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OperationalError: FATAL: Peer authentication failed for user "postgres" fatal: [db]: FAILED! => {"changed": false, "msg": "unable to connect to database: FATAL: Peer authentication failed for user \"postgres\"\n"} to retry, use: --limit @/home/sago/Documents/PCARI/DEV3/CCM_20171212/CommunityCellularManager/cloud/ansible/postgres.dev.retry PLAY RECAP ********************************************************************* db : ok=2 changed=1 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again. ``` Replacing sudo/sudo_user with become/become_user fixed this and the DB vm was completed without any hiccups. This is also partially mentioned in facebookarchive#20 Closes facebookarchive#90 Differential Revision: D6544987 Pulled By: 9muir fbshipit-source-id: 20d639a581f9e8fc455d9706282f7a2a3832fa67
Hello,
Following the instructions per Facebook's CommunityCellularManager for CLOUD, I am getting errors
I did a git checkout of the following Facebook Community Cellular Manager:
buntu@ubuntu:~/CommunityCellularManager$ sudo git log -n1
commit 9e5415d
Author: Steve Muir muir@fb.com
Date: Mon Dec 19 11:31:50 2016 -0800
Here is what I'm running:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
I have the following installed:
ubuntu@ubuntu:~/CommunityCellularManager/cloud$ pip3 --version
pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)
ubuntu@ubuntu:~/CommunityCellularManager/cloud$ pip --version
pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)
ubuntu@ubuntu:~/CommunityCellularManager/cloud$ vagrant --version
Vagrant 1.8.7
VBoxManage --version
4.3.36_Ubuntur105129
ansible --version
ansible 2.3.0
Here is the error message I receive:
**DEBUG ssh: Checking key permissions: /home/ubuntu/CommunityCellularManager/cloud/.vagrant/machines/db/virtualbox/private_key
INFO interface: detail: Running ansible-playbook...
INFO interface: detail: db: Running ansible-playbook...
db: Running ansible-playbook...
INFO interface: detail: PYTHONUNBUFFERED=1 ANSIBLE_NOCOLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --connection=ssh --timeout=30 --limit="db" --inventory-file=/home/ubuntu/CommunityCellularManager/cloud/.vagrant/provisioners/ansible/inventory -v ansible/postgres.dev.yml
PYTHONUNBUFFERED=1 ANSIBLE_NOCOLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --connection=ssh --timeout=30 --limit="db" --inventory-file=/home/ubuntu/CommunityCellularManager/cloud/.vagrant/provisioners/ansible/inventory -v ansible/postgres.dev.yml
INFO subprocess: Starting process: ["/usr/local/bin/ansible-playbook", "--connection=ssh", "--timeout=30", "--limit=db", "--inventory-file=/home/ubuntu/CommunityCellularManager/cloud/.vagrant/provisioners/ansible/inventory", "-v", "ansible/postgres.dev.yml"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Using /home/ubuntu/CommunityCellularManager/cloud/ansible.cfg as config file
INFO interface: detail: Using /home/ubuntu/CommunityCellularManager/cloud/ansible.cfg as config file
Using /home/ubuntu/CommunityCellularManager/cloud/ansible.cfg as config file
DEBUG subprocess: stderr: [DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and
make sure become_method is 'sudo' (default).
This feature will be removed in a
future release. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
INFO interface: detail: [DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and
make sure become_method is 'sudo' (default).
This feature will be removed in a
future release. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and
make sure become_method is 'sudo' (default).
This feature will be removed in a
future release. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
DEBUG subprocess: stdout:
PLAY [db] **********************************************************************
INFO interface: detail:
PLAY [db] **********************************************************************
PLAY [db] **********************************************************************
DEBUG subprocess: stdout:
TASK [Gathering Facts] *********************************************************
INFO interface: detail:
TASK [Gathering Facts] *********************************************************
TASK [Gathering Facts] *********************************************************
DEBUG subprocess: stdout: fatal: [db]: UNREACHABLE! => {"changed": false, "msg": "SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh", "unreachable": true}
INFO interface: detail: fatal: [db]: UNREACHABLE! => {"changed": false, "msg": "SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh", "unreachable": true}
fatal: [db]: UNREACHABLE! => {"changed": false, "msg": "SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh", "unreachable": true}
DEBUG subprocess: stdout: to retry, use: --limit @/home/ubuntu/CommunityCellularManager/cloud/ansible/postgres.dev.retry
PLAY RECAP *********************************************************************
db : ok=0 changed=0 unreachable=1 failed=0
INFO interface: detail: to retry, use: --limit @/home/ubuntu/CommunityCellularManager/cloud/ansible/postgres.dev.retry
PLAY RECAP *********************************************************************
db : ok=0 changed=0 unreachable=1 failed=0
PLAY RECAP *********************************************************************
db : ok=0 changed=0 unreachable=1 failed=0
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 4
ERROR warden: Error occurred: Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.**
I've tried to add become/become_user to the Ansible.cfg file all with the same error.
Any assistance would be greatly appreciated!
The text was updated successfully, but these errors were encountered: