Hi, (sorry, this turned out rather long) I had windows updates running using an ansible playbook.
I was using domain account, become, runas etc all working pretty well for the last 9 months... Then I upgraded ansible running on my centos 7.5 system to version 2.8 as I was working on the same system but was going to write a playbook to add a user account to aws instances... someone that used this same system and a playbook I wrote to run windows updates on their windows VMs then told me his playbook stopped working I looked at it and it seemed there might have been kerberos problems, or domain membership problems - I wasn't getting anywhere so.. I build a new ansible control server, joined to domain, setup pywinrm[kerberos] and more or less have a pristine system now with ansible 2.8, but I have the same problem, so it seems as though it is the uprgrade to 2.8 maybe that has caused this. basically, I run the playbook, it connects and gets to: TASK [Install Updates] **************************************************************************************************************** task path: /home/bi003do/Playbooks/WinUpdate/win-update-prod.yml:12 win_updates: running win_updates module Using module file /usr/lib/python2.7/site-packages/ansible/modules/windows/win_updates.ps1 Pipelining is enabled. <covmgrid83> ESTABLISH WINRM CONNECTION FOR USER: [email protected] on PORT 5986 TO covmgrid83 EXEC (via pipeline wrapper) and thats as far as it gets... on the VM itself I can see processes running under the mydomainuser ID in task manager, so I know it is connecting correctly, I have googled on this and found some info, but nothing that has helped yet... Unfortunately, the user that runs my playbook to update templates has a limited window each month to get this done before they start a long process that last several weeks and we can't run updates and if we don't the security team gets hot and bothered. The window is quickly closing for this month and I am at a loss. How can I troubleshoot this futher. Also I was able to do a win_ping on this server, but only using a local domain account, when I tried it with a domain account, it actually crashed - it goes by the sticking line above and I get this EXEC (via pipeline wrapper) The full traceback is: Exception of type 'System.OutOfMemoryException' was thrown. At line:13 char:1 + $module = [Ansible.Basic.AnsibleModule]::Create($args, $spec) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [], OutOfMemoryException + FullyQualifiedErrorId : System.OutOfMemoryException ScriptStackTrace: at <ScriptBlock>, <No file>: line 13 System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Runtime.CompilerServices.RuntimeHelpers._CompileMethod(IRuntimeMethodInfo method) at System.Reflection.Emit.DynamicMethod.CreateDelegate(Type delegateType, Object target) at System.Linq.Expressions.Compiler.LambdaCompiler.Compile(LambdaExpression lambda, DebugInfoGenerator debugInfoGenerator) at System.Linq.Expressions.Expression`1.Compile() at System.Runtime.CompilerServices.CallSiteBinder.BindCore[T](CallSite`1 site, Object[] args) at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2) at System.Management.Automation.Interpreter.DynamicInstruction`4.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) covmgrid83 | FAILED! => { "changed": false, "msg": "Unhandled exception while executing module: Exception of type 'System.OutOfMemoryException' was thrown." actually, this is now saying out of memory, which was different than before... is that really a memory errror? Well, any advice on what I should be checking next would be appreciated. Thanks Bill -- 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/f0b0781f-5968-466e-a373-b43c4845bb7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
