It’s not a frequent thing. It happened today and perhaps a month ago. That’s why I thought it might not be the control path issue (I am deploying to EC2 from a Mac laptop, but changed the host names on the EC2 box to be shorter and more readable).
I’ve been running the cron job without verbose logging. I’ve change the job to include -v logging in case it happens again. It’s not a big issue, but just want to be sure it’s not a configuration issue I should be aware of. Thanks, Jim McMahon On Dec 4, 2014, at 12:53 PM, James Cammarata <[email protected]> wrote: > Hi Jim, > > Does this happen frequently or just the one time? If the task re-ran without > issues, it's probably not a control path issue. It could be a transient > issue, for example if you just happened to catch the ControlPersist process > when it was shutting down due to a timeout, or it could be a ulimit issue > (too many open files, if a large number of forks are being used). > > > On Thu, Dec 4, 2014 at 10:38 AM, Jim McMahon > <[email protected]> wrote: > Not sure if my error is related to the control path (see link below) or not, > but I got a error about not being able to transfer a file in my logs. > > http://docs.ansible.com/intro_configuration.html#control-path > > 2014-12-04 10:02:47,137 p=1602 u=jmcmahon | TASK: [census.deploy | Copy > .ruby-gemset to releases] ************************* > 2014-12-04 10:07:21,740 p=1602 u=jmcmahon | fatal: > [mqa-cbeserver1.flatworldknowledge.com] => failed to transfer file to > /tmp/ansible-tmp-1417705367.85-253946577954926/copy: > > Read from socket failed: Connection reset by peer^M > Connection closed^M > > 2014-12-04 10:07:21,741 p=1602 u=jmcmahon | FATAL: all hosts have already > failed -- aborting > 2014-12-04 10:07:21,741 p=1602 u=jmcmahon | PLAY RECAP > ******************************************************************** > 2014-12-04 10:07:21,743 p=1602 u=jmcmahon | to retry, use: > --limit @/Users/jmcmahon/deploy-census.retry > > 2014-12-04 10:07:21,744 p=1602 u=jmcmahon | > mqa-cbeserver1.flatworldknowledge.com : ok=11 changed=7 unreachable=1 > failed=0 > > Any ideas on what happened? I was able to manually run the script again and > all worked fine. > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/e9d803eb-0be2-4e8b-a244-23109fd896b5%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/IHnjbmDPN0Y/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAMFyvFgnHCHiWmdFWAox0vG9cJuGL3hM%2BsntSm6c-6AQ8Y_ezw%40mail.gmail.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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1A2FC138-14B3-4406-BD2D-EF2C373967F2%40flatworldknowledge.com. For more options, visit https://groups.google.com/d/optout.
