I wound up just calling out to rsync and living with the complexity that
brings. In future, I expect I'll probably remove the .svn and .git
directories as part of staging the content; then I can use a straight copy
instead of synchronize or rsync.
I'm not convinced it's the io.c problem Michael mentions though. Both
sides of the rsync are centos 6.4. Given the ssh "Permission denied"
complaints that preceed the io.c error, I'm inclined to suspect the --rsh
option is somehow not retaining quotes around its arguments, so missing
ssh's -i argument. Baffling...
On Friday, April 25, 2014 2:37:44 PM UTC-6, Michael DeHaan wrote:
>
> io.c errors are beyond our control as far as I'm aware.
>
> You may wish to just use the recursive copy options instead.
>
>
>
>
> On Thu, Apr 24, 2014 at 6:06 PM, Brian Grossman
> <brian.g...@gmail.com<javascript:>
> > wrote:
>
>> Both sides are running centos 6.4.
>>
>> Would that io.c problem apply if rsync by itself works?
>>
>> Brian
>>
>> On Wednesday, April 23, 2014 7:06:01 AM UTC-6, Michael DeHaan wrote:
>>
>>> "This is with ansible 1.5.3 on centos 6.4. Using paramiko for
>>> transport. "
>>>
>>> What OS are you running from?
>>>
>>> Ubuntu 14.04 has/had a known bug in rsync's io.c (not ansible) where it
>>> can't talk to older hosts.
>>>
>>> Search google for the io.c error and you'll see a few references.
>>>
>>>
>>> On Mon, Apr 21, 2014 at 5:42 PM, Brian Grossman <brian.g...@gmail.com>wrote:
>>>
>>>> I have a synchronize task and an rsync command task that I think should
>>>> be equivalent. The rsync works, but the synchronize doesn't. Can anyone
>>>> help me make synchronize work?
>>>>
>>>> This is with ansible 1.5.3 on centos 6.4. Using paramiko for
>>>> transport. TTY-less sudo works.
>>>>
>>>> I don't want to use the copy module because I want to skip over .svn
>>>> directories, and it doesn't have anything like the .rsync-filter file.
>>>>
>>>> (Loving ansible, BTW.)
>>>>
>>>>
>>>> rsync task:
>>>>
>>>> - name: my copy in bin dir
>>>> sudo: no
>>>> local_action: >
>>>> command
>>>> rsync
>>>> --delay-updates -FF --compress --timeout=10 --delete-after
>>>> --archive --no-owner --no-group
>>>> --rsh 'ssh -i /home/mumble/.ansible/keys/mumble-id_rsa -o
>>>> stricthostkeychecking=no'
>>>> --rsync-path 'sudo rsync'
>>>> --out-format='<<CHANGED>>%i %n%L'
>>>> {{ inventory_dir }}/working/mumble-bin/
>>>> admin@{{ inventory_hostname }}:/mumble/bin
>>>>
>>>>
>>>> synchronize task:
>>>>
>>>> - name: copy in bin dir
>>>> synchronize: >
>>>> owner=no group=no delete=yes
>>>> src={{ inventory_dir }}/working/digimarc-bin/
>>>> dest=/digimarc/bin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Here's the ansible-playbook -vvv output from them. I notice that the
>>>> rsync local_action task splits the cmd into an array, while the
>>>> synchronize
>>>> task doesn't. Aside from that, I'm utterly mystified. If I copy the
>>>> synchronize cmd to my terminal it works just fine.
>>>>
>>>>
>>>> rsync:
>>>>
>>>> TASK: [mumble-bin | my copy in bin dir] ******************************
>>>> *******
>>>> <127.0.0.1> REMOTE_MODULE command rsync --delay-updates -FF --compress
>>>> --timeout=10 --delete-after --archive --no-owner --no-group --rsh 'ssh -i
>>>> /home/mumble/.ansible/keys/mumble-id_rsa -o stricthostkeychecking=no'
>>>> --rsync-path 'sudo rsync' --out-format='<<CHANGED>>%i %n%L'
>>>> /home/mumble/.ansible/PB-dpc/working/mumble-bin/
>>>> ad...@ops001.mumble.com:/mumble/bin
>>>> <127.0.0.1> EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-
>>>> tmp-1398114848.9-199337421744003 && chmod a+rx
>>>> $HOME/.ansible/tmp/ansible-tmp-1398114848.9-199337421744003 && echo
>>>> $HOME/.ansible/tmp/ansible-tmp-1398114848.9-199337421744003']
>>>> <127.0.0.1> PUT /tmp/tmpFEn0En TO /home/mumble/.ansible/tmp/
>>>> ansible-tmp-1398114848.9-199337421744003/command
>>>> <127.0.0.1> EXEC ['/bin/sh', '-c', '/usr/bin/python
>>>> /home/mumble/.ansible/tmp/ansible-tmp-1398114848.9-199337421744003/command;
>>>>
>>>> rm -rf /home/mumble/.ansible/tmp/ansible-tmp-1398114848.9-199337421744003/
>>>> >/dev/null 2>&1']
>>>> changed: [ops001.mumble.com] => {"changed": true, "cmd": ["rsync",
>>>> "--delay-updates", "-FF", "--compress", "--timeout=10", "--delete-after",
>>>> "--archive", "--no-owner", "--no-group", "--rsh", "ssh -i
>>>> /home/mumble/.ansible/keys/mumble-id_rsa -o stricthostkeychecking=no",
>>>> "--rsync-path", "sudo rsync", "--out-format=<<CHANGED>>%i %n%L",
>>>> "/home/mumble/.ansible/PB-dpc/working/mumble-bin/",
>>>> "ad...@ops001.mumble.com:/mumble/bin"], "delta": "0:00:00.348326",
>>>> "end": "2014-04-21 14:14:09.299270", "item": "", "rc": 0, "start":
>>>> "2014-04-21 14:14:08.950944", "stderr": "", "stdout": ""}
>>>>
>>>>
>>>>
>>>> synchronize:
>>>>
>>>> TASK: [mumble-bin | copy in bin dir] ******************************
>>>> **********
>>>> <127.0.0.1> ESTABLISH CONNECTION FOR USER: admin on PORT 22 TO
>>>> 127.0.0.1
>>>> <127.0.0.1> EXEC /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-
>>>> tmp-1398114849.46-137775062175503 && chmod a+rx
>>>> $HOME/.ansible/tmp/ansible-tmp-1398114849.46-137775062175503 && echo
>>>> $HOME/.ansible/tmp/ansible-tmp-1398114849.46-137775062175503'
>>>> <127.0.0.1> PUT /tmp/tmp3awrHX TO /home/admin/.ansible/tmp/
>>>> ansible-tmp-1398114849.46-137775062175503/synchronize
>>>> <127.0.0.1> EXEC /bin/sh -c '/usr/bin/python /home/admin/.ansible/tmp/
>>>> ansible-tmp-1398114849.46-137775062175503/synchronize; rm -rf
>>>> /home/admin/.ansible/tmp/ansible-tmp-1398114849.46-137775062175503/
>>>> >/dev/null 2>&1'
>>>> failed: [ops001.mumble.com] => {"cmd": "rsync --delay-updates -FF
>>>> --compress --timeout=10 --delete-after --archive --no-owner --no-group
>>>> --rsh 'ssh -i /home/mumble/.ansible/keys/mumble-id_rsa -o
>>>> StrictHostKeyChecking=no' --rsync-path 'sudo rsync'
>>>> --out-format='<<CHANGED>>%i %n%L'
>>>> /home/mumble/.ansible/PB-dpc/working/mumble-bin/
>>>> ad...@ops001.mumble.com:/mumble/bin", "failed": true, "item": "",
>>>> "rc": 255}
>>>> msg: Permission denied, please try again.
>>>> Permission denied, please try again.
>>>> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>>>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>>>> rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
>>>>
>>>>
>>>>
>>>>
>>>> Brian
>>>>
>>>> --
>>>> 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/0573f27b-16af-4759-a27b-
>>>> a8e0498eaaf0%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/0573f27b-16af-4759-a27b-a8e0498eaaf0%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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-proje...@googlegroups.com <javascript:>.
>> To post to this group, send email to ansible...@googlegroups.com<javascript:>
>> .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/7fa00305-2340-47de-90b8-7e35715640bb%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/7fa00305-2340-47de-90b8-7e35715640bb%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> 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+unsubscr...@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/a586021a-d826-42d6-8920-8f0bc7bbaf50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
