2 Replies Latest reply on Dec 1, 2017 4:02 PM by rschroeder

    After  installing UDT, I frequently see this alert:  "New UDT polling jobs (388) are still running..."  Support can't fix it.  What's this mean?

    rschroeder

      A couple of months ago I upgraded NPM to 12.2, and all the other matching upgrades for NCM, NTA.  I also installed the recommended Hot Fixes.

       

      Then I bought IPAM and UDT and installed them, along with one more APE.

       

      They ran OK for a few weeks, but now I've got this message showing up in the Alerts part of NPM's home page:

       

      New UDT polling jobs (388) are still running...

       

      I searched for that message in Support & Thwack; haven't found the issue.  I was hoping it was something I could correct by changing UDT  polling timeouts, but although I've tried doubling them once, and doubling them a second time, there's been no improvement.

       

      Might you have an idea about what's going on here?  I've had reoccurring issues where the C drives on APE have filled, and SW Support seems to think the issue is possibly:

      • The C drives are sized too small (they're not, per SW recommendation)
      • Anti-Virus is stopping reports from getting to the main NPM instance (AV is configured to exempt the recommended directories, but the logs say communications are failing between the APE's and NPM)
      • I removed failing NetPath monitors in hopes that might fix it.  No luck.

       

      If you have ideas on what's going on with my UDT, based on this alert, I'd love to hear from you.

        • Re: After  installing UDT, I frequently see this alert:  "New UDT polling jobs (388) are still running..."  Support can't fix it.  What's this mean?
          nickzourdos

          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.

          1 of 1 people found this helpful