Thank you so much buddy. Actually, I'm working with Standard B2ms VMs (2 vCPUs, 8 GB RAM), but this time I'll try with a larger machine.
What seemed strange is the fact that CPU utilization was really low (almost 0%) during several minutes before Ansible failure appears. I got this info from Azure metrics for this VM. I'll share my results once I try again On Wed, Oct 23, 2019 at 11:38 AM 'J Hawkesworth' via Ansible Project < ansible-project@googlegroups.com> wrote: > I have had issues with single core machines when windows updates include > an upgrade to the dot net version. What happens is ngen recompiles all the > dot net code it can find and ties up an entire core until has finished > recompiling, which leaves no cpu time for winrm. Dual core boxes aren't as > badly affected as ngen only ties up one core. > > Even if it is not ngen, perhaps it would be worth trying to find out what > the vms are doing at the moment your connection fails. > > Hope this helps, > > Jon > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/d1149048-8568-4bc9-9741-0ed710d1f4b0%40googlegroups.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAA3McK9J3P%2BM-2NvcZhNFz9oshkWqfthJMusF9SHoTmUhTBj4w%40mail.gmail.com.
