10 Replies Latest reply on Dec 17, 2009 11:57 AM by forestial

    Policy.client.invoker.exe - CPU and Memory usage

    Apprentice

      Hi all,

       

      It seems that the latest patch of policy.client.invoker has a memory leak and is still using excessive CPU.  See screenshots below:

      CPU.PNG

      System is XP SP2 and we are running LDMS 8.8 SP3

      FileVersion.PNG

       

      This is after installing the SWD-2808788.3-2 patch.

       

      Anyone else with the same issue?

        • 1. Re: Policy.client.invoker.exe - CPU and Memory usage
          mrspike SSMMVPGroup

          We have seen this as well, what I have done is to run a script (below) to delete the database on the client system and let it recreate, this seems to have helped, not sure if solves the issue or not. (We did install the patch first)

           

           

          : This script will delete the clients landesk database, recreate it, validate it and clean up
          : old xml files/  Any xml files that are still required will repopulate as needed
          : this is also good at fixing portal and other policy issues
          :
          cmd /c del "c:\documents and settings\all users\application data\landesk\managementsuite\database" /q
          del "C:\Documents and Settings\All Users\Application Data\LANDesk\ManagementSuite\landesk\files" /q
          del "C:\Documents and Settings\All Users\Application Data\vulScan\*.xml" /q
          del "C:\Program Files\LANDesk\LDClient\sdmcache\landesk\files\*.xml" /q
          net stop "Landesk Policy Invoker"
          "c:\program files\landesk\ldclient\clientdbutil.exe" /create
          "c:\program files\landesk\ldclient\clientdbutil.exe" /validate
          net start "Landesk Policy Invoker"
          "c:\program files\landesk\ldclient\policy.sync.exe"
          "c:\program files\landesk\ldclient\policy.client.invoker.exe"
          EXIT /B 0

          1 of 1 people found this helpful
          • 2. Re: Policy.client.invoker.exe - CPU and Memory usage
            SupportEmployee

            I would be interested in looking at the policy.client.invoker.log, policy.sync.exe.log, and the client database file. While James suggestion below "fixes" the problem, I would like to figure out why we are doing this in the first place.

             

            The SWD-2808788.3-2 patch addressed an issue where the xml reference in the client database came up missing. There are several scenarios that caused us to get into this state.

             

            Thanks for you help in advance.

            • 3. Re: Policy.client.invoker.exe - CPU and Memory usage
              technobabble Apprentice

              This is also causing a major headache at thye same I am currently working at. I will gather the log filles the next time this problem occurs and the post them as well as send them to you. This is notice primarily whena machine has been re-imaged and the agent is installed new. The patch to address this issue has been applied to the core server so the agent contains the new code.

              • 4. Re: Policy.client.invoker.exe - CPU and Memory usage
                Apprentice

                gashby wrote:

                 

                I would be interested in looking at the policy.client.invoker.log, policy.sync.exe.log, and the client database file. While James suggestion below "fixes" the problem, I would like to figure out why we are doing this in the first place.

                 

                The SWD-2808788.3-2 patch addressed an issue where the xml reference in the client database came up missing. There are several scenarios that caused us to get into this state.

                 

                Thanks for you help in advance.

                 

                Hi Gerald,

                 

                I sent you the files requested a few days ago.  Where you able to figure out what is causing this?

                • 5. Re: Policy.client.invoker.exe - CPU and Memory usage
                  SupportEmployee

                  This doesn't seem to be related to the root cause that the above mentioned patch addresses. Having investigated this issue for a couple of customers now we have not yet been able to determine a root cause. I does have to do with the client database becoming corrupted for some reason. Using the script that James has graciously provided will "fix" the issue. However, if you would like to get to the root cause you'll have to open a support incident so we can address the proper.

                  • 6. Re: Policy.client.invoker.exe - CPU and Memory usage
                    Specialist

                    Would anyone care to take a stab and create a custom definition of the script and export the XML so we can all have it?

                    • 7. Re: Policy.client.invoker.exe - CPU and Memory usage
                      mrspike SSMMVPGroup

                      I use a .bat file with the script and use Software Dist. to push it out.

                      • 8. Re: Policy.client.invoker.exe - CPU and Memory usage
                        SupportEmployee

                        I would agree that using a batch file is probably the best approach... not sure what the detection logic would look like on this in the form of a custom def.

                        • 9. Re: Policy.client.invoker.exe - CPU and Memory usage
                          mrspike SSMMVPGroup

                          Finding affected systems is hard, often times it is only discovered when a user or tech finds an issue.

                           

                          One of the ways I have used that is fairly accurate is to go to some of your Software Deployment Portal tasks, go into the "pending" group and sort by "Status", the ones that are listed as "waiting" are suspect.

                           

                          I have found that if it is "waiting" that the system has not either checked in since the task was created or the database is corrupt.  You can right client on some of these systems (sadly not from this view, but up in the device view) and check the "scheduled tasks and policies" there you will see your policies for the portal and other tasks, if the system is checking in regularly and yet has "waiting" and "not specified" mixed in there, my experience finds that database is corrupt.

                           

                           

                          So what I do from time to time is create the software dist. job (push) with the bat file to delete the client database and then I go into a random number of my portal tasks, sort them and drag the "waiting" systems to the task.  I repeat this in several of the portal tasks as not all systems will show corrupt for the same task.

                           

                          I then run the job (I use a silent, never reboot, push delivery method).

                           

                          If the reason the systems was in "waiting" was because it had never checked in, no biggie, no harm, and the system is likely offline any ways.

                           

                          I will LANDesk would do a better job of being able to detect a corrupt database, but this gets me through it until then

                          • 10. Re: Policy.client.invoker.exe - CPU and Memory usage
                            Rookie

                            I modified the CMD file for use on a Vista x64 machine (directory names change on Vista vs. XP/2003), in case it helps someone else:

                             

                            : This script will delete the clients landesk database, recreate it, validate it and clean up
                            : old xml files/  Any xml files that are still required will repopulate as needed
                            : this is also good at fixing portal and other policy issues
                            :
                            cmd /c del "c:\ProgramData\landesk\managementsuite\database" /q
                            del "C:\ProgramData\LANDesk\ManagementSuite\landesk\files" /q
                            del "C:\ProgramData\vulScan\*.xml" /q
                            del "C:\Program Files (x86)\LANDesk\LDClient\sdmcache\landesk\files\*.xml" /q
                            net stop "Landesk Policy Invoker"
                            "c:\program files (x86)\landesk\ldclient\clientdbutil.exe" /create
                            "c:\program files (x86)\landesk\ldclient\clientdbutil.exe" /validate
                            net start "Landesk Policy Invoker"
                            "c:\program files (x86)\landesk\ldclient\policy.sync.exe"
                            "c:\program files (x86)\landesk\ldclient\policy.client.invoker.exe"
                            EXIT /B 0