1 of 1 people found this helpful
This was a symptom I had after initially upgrading to UDT v3.3, but a hotfix seems to have taken care of it. There were some extra steps that support had me do, though. Here's the full Hotfix procedure they gave me:
1) Do the following for ALL POLLING ENGINES with UDT installed
Use an Administrator account to log in to the server that hosts your SolarWinds Orion installation.
Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
Run the SolarWinds-UDT-v3.3.0-HotFix1.msp file ON ALL POLLING ENGINES with UDT installed.
This hotfix can be installed through Falcon installer as well.
2) Execute SQL query
DELETE FROM udt_nodecapability
DELETE FROM udt_job
! THIS QUERY WILL UNMONITOR ALL UDT NODES (REMOVE ALL NODES FROM UDT MONITORING).
3) Clean up Collector 'sdf' data and JobEngine 'sdf' data on each Poller
JobEngine data: C:\ProgramData\Solarwinds\JobEngine.v2\Data
Collector data: C:\ProgramData\SolarWinds\Collector\Data
For clean up data file please do the next steps:
All SolarWinds services should be stopped on all polling engines;
Open up Programs and Features
Right click and uninstall on the Soalrwinds Job Engine, Solarwinds Job Engine V2, and the Solarwinds Collector.
Reinstall them by navigating to C:\ProgramData\Solarwinds\Installers and run the Job engines/Collector MSI files located there.
**NOTE: if you have issues getting the Job Engine to reinstall, you might need to open a command prompt as admin and then run the MSI file via the command line**
after cleaning up all UDT polling engines start all SolarWinds services for all engines.
Those are great notes. And they are exactly what SW Support did on the pollers that had their C drives filled. But Support did NOT do this on all pollers . . .