1 Reply Latest reply on Sep 22, 2014 12:52 PM by Tanner Lindsay

    Slow OSD tasks due to perceived task status send delays

    Rookie

      Hi All,

       

      I have never posted a question on this community before so here goes!

       

      We are running LDMS 9.5 SP2

       

      I have been using LANDesk for a little while now, I am just looking for some guidance on an issue I am seeing. Periodically our OSD tasks are slowed down dramatically. Each time they are there are long delays between the task status being sent back to the core and the next stage of the task starting.

       

      Please see the selected part from an SDClient_Task log, can you all let me know if this a blatant delay with core receiving the status? Or if it is normal?

       

      Fri, 12 Sep 2014 10:39:52 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3526

      Fri, 12 Sep 2014 10:55:50 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\AcroReader\11.0.04\silent_install.cmd) is not in cache

       

      Fri, 12 Sep 2014 11:14:44 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3524

      Fri, 12 Sep 2014 11:26:17 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Flash\install_flash_11.9.900.170.cmd) is not in cache

       

      Fri, 12 Sep 2014 11:28:20 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3524

      Fri, 12 Sep 2014 11:44:26 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Flash\install_flash_11.9.900.170.cmd) is cached locally

       

      Fri, 12 Sep 2014 11:56:53 Sending task status, cmd line -coreandip=LONLDCP01003:10.193.248.89 -taskid=7822 -retcode=229392397 -pkgid=3525

      Fri, 12 Sep 2014 12:12:49 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Shockwave\12.0\sw_lic_full_installer_12.0.7.148.msi) is not in cache

       

      12:13:52 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3525

      Fri, 12 Sep 2014 12:25:01 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Shockwave\12.0\sw_lic_full_installer_12.0.7.148.msi) is cached locally

       

      Fri, 12 Sep 2014 12:25:03 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229965824 -complete -pkgid=3525

      Fri, 12 Sep 2014 12:37:23 processing of package is complete, result 229965824 (0x0db50000 - code 0)

       

      on, 15 Sep 2014 06:01:55 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=1778

      Mon, 15 Sep 2014 06:18:07 File (\\CORENAME\ldpackages\Software\Global Apps\Winzip\17.5\install_winzip.cmd) is cached locally

       

      Kind Regards,

       

      D

        • 1. Re: Slow OSD tasks due to perceived task status send delays
          Tanner Lindsay SupportEmployee

          Are those adjoining lines in the sdclient_task log? There are no lines between? Normally it shouldn't take that long to send the task status. More information might be needed to know for sure, but it could be that your Core Server is processing things slowly at those times. The task status is processed by the WSVulnerabilityCore web application in the LDAppVulerability application pool in IIS. You might find that it is really busy at that time.

           

          Depending on why it is busy (and slow) there could be a few different solutions. The most common reason for slowness in this area is database access/processing. Check your database for fragmented indexes or other potential performance problems. You can look in the WSVulnerabilityCore.dll.log on your Core server, and there will be some information about any queries that are taking a long time to resolve, as well as some summaries of the work that is being done.

           

          You might also be able to increase the number of worker processes used by LDAppVulnerability. This would give the IIS application pool another process and additional resources if that is the cause of the slow down. You shouldn't increase that drastically, just a bit at a time and it should never exceed the number of CPU cores you have - 1. For example, with a quad-core CPU, it should never be more than 3. (Well, never is not really a good word to use, but... probably shouldn't)