hello all,
i have dynamically generated inventory like below, i want to establish ssh
conenction to all the ips for istiotst and coremediaprod servers. I have
ssh keys configured in the .ssh folder:
when i run: ansible all -i inventory-ccp.ini -m ping
i get connection 'success' only for is
Hi
$ vagrant ssh-config
Host default
HostName 127.0.0.1
User vagrant
Port 2200
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /mnt/c/temp/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
On Wednesday, September 30, 2
On 9/30/20 10:36 PM, Keith Mills wrote:
> Hi Dick
>
>
> Ran vagrant ssh in WSL2.
>
>
> So then I tried using raw SSH:
>
What does "vagrant ssh-config" say?
Regards
Racke
>
>
>
> On Tuesday, September 29, 2020 at 9:57:38 AM UTC-5 dick@geant.org wrote:
>
> On Tue, 29 Se
Hi Dick
Ran vagrant ssh in WSL2.
So then I tried using raw SSH:
On Tuesday, September 29, 2020 at 9:57:38 AM UTC-5 dick@geant.org wrote:
> On Tue, 29 Sep 2020 at 15:19, Keith Mills wrote:
> >
> > Hello All,
> >
> > Running ansible but keep getting failed to connect to host via ssh.
On Tue, 29 Sep 2020 at 15:19, Keith Mills wrote:
>
> Hello All,
>
> Running ansible but keep getting failed to connect to host via ssh.
>
> Vagrant Version: 2.2.10
>
> Host OS: Windows 10 (+ virtualbix)
>
> Guest OS: bento/ubuntu-18.04
>
> WSL version: 2
>
> Vagrantfile:
>
> Vagrant.configure("2")
Hello All,
Running ansible but keep getting failed to connect to host via ssh.
Vagrant Version: 2.2.10
Host OS: Windows 10 (+ virtualbix)
Guest OS: bento/ubuntu-18.04
WSL version: 2
Vagrantfile:
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.synced
Hi everybody,
I have some problems to use ansible.
I use ansible version 2.4.3.0 i
I testing just one host with IP and port (I have port fowarding).
I copying ssh pub key (ssh-copy-id).
I try to install Git on the target serveur.
tasks:
- name: Installation de Git
apt: name=git update_cache=ye
Hi All,
New to Ansible. New to the group.
Trying to run some basic commands against my VMware environment and thought
I would start with vmware_facts.
ansible 2.4.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules',
u'/usr/share/a
FYI, I am seeing that on AWS as well. Very intermittent but happens every
50 deployments or so for us.
In our case it's all Debian running against other Debian machines all
within AWS.
On Monday, August 22, 2016 at 11:41:24 AM UTC-7, Aaron Bernardino wrote:
>
> Thanks for the feedback. I tried
Thanks for the feedback. I tried from my CentOS vagrant box and it worked.
Provisioning using Cygwin does work though when I am just using Vagrant on
Cygwin to create and configure a VM locally.
On Saturday, August 20, 2016 at 6:30:05 AM UTC-4, Dick Davies wrote:
>
> This is running under Cygw
This is running under Cygwin by the look of it, that's not supported.
Can you install a small VM to run Ansible from?
On 19 August 2016 at 22:28, Aaron Bernardino
wrote:
> I'm running a playbook where tasks are failing with error message -> "SSH
> Error: data could not be sent to the remote host
I'm running a playbook where tasks are failing with error message -> "SSH
Error: data could not be sent to the remote host. Make sure this host can
be reached over ssh", "unreachable": true
The weird thing is that I have around 11 tasks in the play and I'd get the
error on the 1st, sometimes on
On 13/04/16 07:57, selvam vasu wrote:
Hi,
I have playbook which has 4 tasks on that. The task are running on more
than 10 remote hosts. The first two tasks are ever running without any
problem. But when the third task is running, The am getting error like
"SSH Error: mux_client_hello_exchange: w
Hi,
I have playbook which has 4 tasks on that. The task are running on more
than 10 remote hosts. The first two tasks are ever running without any
problem. But when the third task is running, The am getting error like "SSH
Error: mux_client_hello_exchange: write packet: Broken pipe". It is not
Hello Guys,
Can someone of you help me with this strange case? I have host running
CentOS 6.7 x86_64. My ansible management host is CentOS 7.2 x86_64, ansible
version 1.9.4. When I try to run playbook against my host I'm getting this
message:
GATHERING FACTS
*
> On Feb 2, 2016, at 01:01, Milet Francis wrote:
>
> Hi..
> I want to establish a ssh connection between 10 servers at the same
> time.Is it possible to use ansible to automate this process.If not do u have
> any other option.
I'm not totally clear on what you mean. Do you want to open an
Hi..
I want to establish a ssh connection between 10 servers at the same
time.Is it possible to use ansible to automate this process.If not do u
have any other option.
Regards,
Milet
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To u
When attempting to run an ansible module on a remote host, the SSH
connection never fully completes...
[myhost myusername 11:46:23]~ $ ansible -v -m setup -i
~/dave_ansible/ansible/hosts.txt remotehost -u user -k -K --sudo
SSH password:
SUDO password[defaults to SSH password]:
ESTABLI
After going from 1.7.1 to 1.9.1 I'm getting "ssh connection closed waiting
for a privilege escalation password prompt" errors. I tried switching to
using the new become directives, but I'm still having problems.
Here's the simplest test case I've come up with:
*test.yml:*
---
- hosts: my.serv
Filed here for reference:
https://github.com/ansible/ansible/issues/9470
On Mon, Nov 3, 2014 at 9:28 AM, Michael DeHaan wrote:
> "Ansible 1.8 now chooses paramiko as the "smart" transport when running
> from Mac. If this is your case, you will need to set transport = ssh under
> defaults as wel
"Ansible 1.8 now chooses paramiko as the "smart" transport when running
from Mac. If this is your case, you will need to set transport = ssh under
defaults as well."
Actually it doesn't.
Darwin has a somewhat common error where "askpass" for SSH can occasionally
kernel panic the machine (I'm almo
What is your control machine (machine you are running ansible from)?
Ansible 1.8 now chooses paramiko as the "smart" transport when running from
Mac. If this is your case, you will need to set transport = ssh under
defaults as well.
You can verify if you are using ssh or paramiko by running with
Hi there!
I've these options in my ansible.cfg:
[ssh_connection]
pipelining=True
ssh_args=-o ForwardAgent=yes -o ControlMaster=auto -o ControlPersist=7200s
On an older version (Ansible 1.6 development, shortly before 1.7 was
final), these settings make deploying relatively fast.
On Ansible 1.8
Yes I did mean "transport = ssh", sorry for the confusion there.
On Fri, May 16, 2014 at 9:43 AM, Adam Morris wrote:
>
>
> On Friday, May 16, 2014 6:24:55 AM UTC-7, James Cammarata wrote:
>>
>>
>> You can make this permanent by changing the "transport = " setting in
>> your ansible.cfg to "tran
On Friday, May 16, 2014 7:57:10 AM UTC-7, Michael DeHaan wrote:
>
> smart will select "ssh" if you have ControlMaster capability on our
> control machine, and will default to paramiko only if it does not.
>
>
Yes, but if he's passing -c ssh and it fixes the issue then he might want
to change fr
smart will select "ssh" if you have ControlMaster capability on our control
machine, and will default to paramiko only if it does not.
On Fri, May 16, 2014 at 10:43 AM, Adam Morris wrote:
>
>
> On Friday, May 16, 2014 6:24:55 AM UTC-7, James Cammarata wrote:
>>
>>
>> You can make this permane
On Friday, May 16, 2014 6:24:55 AM UTC-7, James Cammarata wrote:
>
>
> You can make this permanent by changing the "transport = " setting in your
> ansible.cfg to "transport = smart".
>
>
Did you mean "transport = ssh"?
Adam
--
You received this message because you are subscribed to the Googl
The instances are already created - it probably doesn't help that I masked
all the IPs, but the EC2 instance ansible is trying to connect to is the
same one I can successfully SSH to.
Just tried "-c ssh" which Michael mentioned - that fixed it, but I'm still
not sure why it fails if I don't pro
Please show the output from that first task as it's trying to connect with
"-" on the command line, and also the SSH debug from the other so we
can see what ports it is trying to talk to there, etc.
It also doesn't matter here I'm guessing, but it's always useful to
indicate your ansible versi
Hi
I'm having some issues getting ansible to connect using SSH, but it only
seems to affect one particular playbook. The odd thing is I can connect
manually using ssh, but ansible fails with a timed out error. Other
playbooks/hosts work absolutely fine with exactly the same config.
Here's the
30 matches
Mail list logo
