You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since updating from 0.2.2 to 0.3.0 we have had an issue where our existing code gets stuck on installing KBs. We found that for whatever reason one of our KBs was no longer valid (via GUI or powershell) so we removed it. However, the three KBs that are valid, and actually installed already on our windows image (the Puppet is an insurance factor) we are still getting locked up on the KB installation. This is an example of a catalog run I started over 8 hours ago:
The svchost (tying back to wuausrv aka windows update service), ruby, and underlying powershell processes are actually busy over the course of this 8 hours, but my assumption is we are stuck in some kind of loop.
Any thoughts?
The text was updated successfully, but these errors were encountered:
We've had the same problem with 2012R2 servers. It looks like the "Get-WUHistory" powershell command gets stuck somehow and the puppet run is just waiting for it. You can try and run this command manually on your server and see if you have the same problem.
For now we limit the Get-WUHistory output to only print the last update installed and this looks to be working fine. Get-WUHistory -Last 1
Hello,
Since updating from 0.2.2 to 0.3.0 we have had an issue where our existing code gets stuck on installing KBs. We found that for whatever reason one of our KBs was no longer valid (via GUI or powershell) so we removed it. However, the three KBs that are valid, and actually installed already on our windows image (the Puppet is an insurance factor) we are still getting locked up on the KB installation. This is an example of a catalog run I started over 8 hours ago:
The svchost (tying back to wuausrv aka windows update service), ruby, and underlying powershell processes are actually busy over the course of this 8 hours, but my assumption is we are stuck in some kind of loop.
Any thoughts?
The text was updated successfully, but these errors were encountered: