[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1160
  • Last Modified:

WSUS downstream replicas high CPU after deleting content folder and running wsusutil.exe reset

We noticed that our WSUS content folder was growing out of control on the master and downstream replicas.  The decision was made to delete everything in the content folders on all WSUS servers and issue a wsusutil.exe RESET command on all WSUS servers as well as change every patch to UNAPPROVED on the master server.

Everything worked great and very quickly on the master which appears to be functioning fine but the downstream replicas are stuck.  The CPU is maxed on a core and WSUS is running queries indefinately.  There is absolutely nothing in the wsus content folder on these replica servers now and we have not approved a single patch after setting them all back to unapproved.  What is going on and how do I fix this?

Here is what is running in SQL on SUSDB:

SUSDB.dbo.spResetStateMachineAndReEvaluate;1  This query is running

SUSDB.dbo.spGetRevisionInfo;1 This query is blocked by the first one

SUSDB.dbo.spGetRevisionIdListForCache;1 This query is blocked by the first one

The downstream replicas are also not able to sync with the master while this is going on now.

How do I fix the downstream replicas so they start syncing again and stop with the maxxed CPU and SUSDB queries running with all the locking?

We are running WSUS fully patched on 2008 R2 for both master and downstream servers.  The SUSDB is running on SQL 2008 R2 fully up to date not sql express or windows database.
Edited by davidb1234 2 hours 50 minutes ago
1 Solution
James HaywoodCommented:
The content folders will not fill up untill there are approved updates to download. In my experience once WSUS goes wrong its impossible to properly fix. Its much quicker to uninstall and reinstall.
NBFAuthor Commented:
That is what I did.  I uninstalled and reinstalled.  It still wouldn't sync. it had an error about a dependent update.  I repointed the replicas to Microsoft and did a manual sync and then back to the master server and now it is working.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now