13 Replies Latest reply on Apr 16, 2015 7:24 AM by joebaggadonuts

    Odd behavior when downloading files for job...client thinks itself is a peer?

    Apprentice

      check this out. It's an excerpt from a sdclient log when it was downloading some files for a package. 192.168.253.150 is the client that's doing the downloading. It seems it wastes a few minutes per file, seemingly trying to get the file from itself.

       

      Anyone see this? Is is expected?

       

      This particular client is communicating through the gateway. I can't say I've seen the same logging on directly connected clients.

       

      Downloading file http://server/ldlogon/packages/WebSense EndPoint/v7.6.1045/x64/MSI_Reboot_Actions.mst (5A2gWwvnlVI2n7wsOwQt0g==, 6)
      Thu, 21 Jul 2011 19:56:50 Downloading file 9 of 29 from 'http://server/ldlogon/packages/WebSense EndPoint/v7.6.1045/x64/MSI_Reboot_Actions.mst'
      Thu, 21 Jul 2011 19:56:52 The file
      http://server/ldlogon/packages/WebSense EndPoint/v7.6.1045/x64/MSI_Reboot_Actions.mst (6 levels) was not in the TMC cache.
      Thu, 21 Jul 2011 19:56:52 ILdDownloading file to C:\Program Files (x86)\LANDesk\LDClient\sdmcache\ldlogon\packages\WebSense EndPoint\v7.6.1045\x64\MSI_Reboot_Actions.mst, attempt 0
      Thu, 21 Jul 2011 19:56:53 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 21 Jul 2011 19:56:54 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 21 Jul 2011 19:56:54 SAD ProcessNeedFileReply about to download ldlogon\packages\WebSense EndPoint\v7.6.1045\x64\MSI_Reboot_Actions.mst from peer 192.168.253.150
      Thu, 21 Jul 2011 19:57:25 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 21 Jul 2011 19:57:26 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 21 Jul 2011 19:57:26 SAD ProcessNeedFileReply about to download ldlogon\packages\WebSense EndPoint\v7.6.1045\x64\MSI_Reboot_Actions.mst from peer 192.168.253.150
      Thu, 21 Jul 2011 19:57:57 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 21 Jul 2011 19:57:57 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 21 Jul 2011 19:57:57 SAD ProcessNeedFileReply about to download ldlogon\packages\WebSense EndPoint\v7.6.1045\x64\MSI_Reboot_Actions.mst from peer 192.168.253.150
      Thu, 21 Jul 2011 19:58:28 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 21 Jul 2011 19:58:29 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 21 Jul 2011 19:58:29 SAD ProcessNeedFileReply about to download ldlogon\packages\WebSense EndPoint\v7.6.1045\x64\MSI_Reboot_Actions.mst from peer 192.168.253.150
      Thu, 21 Jul 2011 19:59:00 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 21 Jul 2011 19:59:00 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 21 Jul 2011 19:59:00 SAD ProcessNeedFileReply about to download ldlogon\packages\WebSense EndPoint\v7.6.1045\x64\MSI_Reboot_Actions.mst from peer 192.168.253.150
      Thu, 21 Jul 2011 19:59:42 ILdDownloadFile returned 0
      Thu, 21 Jul 2011 19:59:42

        • 1. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
          LANDeskWizrd SSMMVPGroup

          Normally the client will try to get the file from its local cache and if not there then it will try its peers. If the peers don't have it then it will try a Preferred Server and then the source of the install. That's pretty much the process. Does it actually download the file at all?

          • 2. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
            Apprentice

            I completely understand that .

             

            Reading the log, though, the machine spends a few minutes seemingly trying to get the file from itself. Doesn't that seem a bit odd?

            • 3. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
              Catalysttgj Expert

              It reads odd, but pretty much the way it behaves. That's what we see as well.

              • 4. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                LANDeskWizrd SSMMVPGroup

                Nope not odd at all, this is the way it functions. It has to check itself first just in case the file is already there from a possible previous deployment or if it has been staged. Still interested in knowing if it downloads fine.

                • 5. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                  Apprentice

                  Absolutely it has to check the cache first. That's the first stop. To my point, though, you'd think this line communicates that it did that:

                   

                  Thu, 21 Jul 2011 19:56:52 The file http://server/ldlogon/packages/WebSense EndPoint/v7.6.1045/x64/MSI_Reboot_Actions.mst (6 levels) was not in the TMC cache.

                  • 6. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                    LANDeskWizrd SSMMVPGroup

                    TMC to me and what I have seen is related to Targeted Multicast. What type of delivery method are you using?

                    • 7. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                      Apprentice

                      Policy.

                       

                      In all the documentation I've read, LANDesk will refer to the sdmcache as the tmc cache or just "the cache". I don't think there are multiple caches.

                      • 8. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                        LANDeskWizrd SSMMVPGroup

                        Is it just a default policy delivery method or did you change anything on it?

                         

                        Also, does the file actually download at all?

                        • 9. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                          Apprentice

                          We're using the out of the box "policy - required installation". Hasn't been changed since installation

                           

                          The files do eventually download, but it takes a while as each file takes 2-3 minutes instead of a few seconds.

                          • 10. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                            Employee

                            If you restart the TMC service on that machine does it still try and hang for a while?

                            • 11. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                              LANDeskWizrd SSMMVPGroup

                              Yeah I do think 2-3 minutes is excessive but since you are going through the Gateway, it's hard to say if that isn't normal. I really don't know how much the Gateway slows down this process.

                              • 12. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                                Apprentice

                                I know it has been a couple of years but I couldn't find an answer for this. I am also seeing this in anything that requires a download. Even in a simple policy sync as shown below. Seems that it checks itself 3 times waiting 30 seconds each time before giving up and going to the Preferred servers / core:

                                 

                                Mon, 07 Apr 2014 16:29:16 [START] Policy synchronization stated.

                                Mon, 07 Apr 2014 16:29:19 Sending policy request to core server.

                                Mon, 07 Apr 2014 16:29:19 Requesting policy for {B78C9E6F-2BA7-1741-A34F-C2599097330F}, user DOMAIN\FirstName.LastName, ldap user CN=LastName\, FirstName,OU=Users,OU=Office,OU=US,OU=AMER,OU=DOMAIN,DC=DOMAIN,DC=ds,DC=corp, ladp machine CN=XX1-ABC123,OU=Computers,OU=Office,OU=US,OU=AMER,OU=DOMAIN,DC=DOMAIN,DC=ds,DC=corp

                                Mon, 07 Apr 2014 16:29:23 Web request returned 0 The web request was successful.

                                Mon, 07 Apr 2014 16:29:23 Has Policy downloaded from core

                                Mon, 07 Apr 2014 16:29:26 Processing new and updated remote operations

                                Mon, 07 Apr 2014 16:29:26    In LoadNewAndUpdatedOperations

                                Mon, 07 Apr 2014 16:29:26    Out LoadNewAndUpdatedOperations

                                Mon, 07 Apr 2014 16:29:26    In ConvertDataTable

                                Mon, 07 Apr 2014 16:29:26    Out ConvertDataTable

                                Mon, 07 Apr 2014 16:29:26    In RemoteOperationDownload::Download

                                Mon, 07 Apr 2014 16:29:26 Preparing to download file SDClientTask.CORE-SERVER.3401.xml (hash dXw5L9XB/GUpYh1QjxomDg==)

                                Mon, 07 Apr 2014 16:29:26 Downloading files to C:\ProgramData\LANDesk\ManagementSuite\landesk\files\

                                Mon, 07 Apr 2014 16:29:27 8152 9276 Performing TCP connection with a timeout of -1 milliseconds

                                Mon, 07 Apr 2014 16:29:28 8152 17196 Performing TCP connection with a timeout of 2500 milliseconds

                                Mon, 07 Apr 2014 16:29:28 8152 17196 SAD ProcessNeedFileReply about to download SDClientTask.CORE-SERVER.3401.xml from peer 10.1.43.101

                                Mon, 07 Apr 2014 16:29:59 8152 17196 Performing TCP connection with a timeout of -1 milliseconds

                                Mon, 07 Apr 2014 16:29:59 8152 17196 Performing TCP connection with a timeout of 2500 milliseconds

                                Mon, 07 Apr 2014 16:29:59 8152 17196 SAD ProcessNeedFileReply about to download SDClientTask.CORE-SERVER.3401.xml from peer 10.1.43.101

                                Mon, 07 Apr 2014 16:30:30 8152 17196 Performing TCP connection with a timeout of -1 milliseconds

                                Mon, 07 Apr 2014 16:30:31 8152 17196 Performing TCP connection with a timeout of 2500 milliseconds

                                Mon, 07 Apr 2014 16:30:31 8152 17196 SAD ProcessNeedFileReply about to download SDClientTask.CORE-SERVER.3401.xml from peer 10.1.43.101

                                Mon, 07 Apr 2014 16:31:02 8152 17196 Performing TCP connection with a timeout of -1 milliseconds

                                Mon, 07 Apr 2014 16:31:02 8152 17196 Performing TCP connection with a timeout of 2500 milliseconds

                                Mon, 07 Apr 2014 16:31:02 8152 17196 SAD ProcessNeedFileReply about to download SDClientTask.CORE-SERVER.3401.xml from peer 10.1.43.101

                                Mon, 07 Apr 2014 16:31:33 8152 17196 Performing TCP connection with a timeout of -1 milliseconds

                                Mon, 07 Apr 2014 16:31:34 8152 17196 Performing TCP connection with a timeout of 2500 milliseconds

                                Mon, 07 Apr 2014 16:31:34 8152 17196 SAD ProcessNeedFileReply about to download SDClientTask.CORE-SERVER.3401.xml from peer 10.1.43.101

                                Mon, 07 Apr 2014 16:32:05 The remote operation file http://CORE-SERVER.DOMAIN.DS.CORP/landesk/files/SDClientTask.CORE-SERVER.3401.xml was downloaded to C:\ProgramData\LANDesk\ManagementSuite\landesk\files\\SDClientTask.CORE-SERVER.3401.xml.

                                Mon, 07 Apr 2014 16:32:05    Out RemoteOperationDownload::Download

                                Mon, 07 Apr 2014 16:32:05    In PolicyResponseData::ProcessExecuteOperations

                                Mon, 07 Apr 2014 16:32:05 Processing remote operation SDClientTask.CORE-SERVER.3401.xml

                                Mon, 07 Apr 2014 16:32:05 AddTargetedPolicy succeeded

                                Mon, 07 Apr 2014 16:32:05    Out PolicyResponseData::ProcessExecuteOperations

                                Mon, 07 Apr 2014 16:32:05 Processing deleted remote operations

                                Mon, 07 Apr 2014 16:32:05    In ConvertDataTable

                                Mon, 07 Apr 2014 16:32:05    Out ConvertDataTable

                                Mon, 07 Apr 2014 16:32:05    In WriteServerResponse

                                Mon, 07 Apr 2014 16:32:05    Out WriteServerResponse

                                Mon, 07 Apr 2014 16:32:05 Policy request has been processed.

                                Mon, 07 Apr 2014 16:32:05 Checking for rescheduled policies

                                Mon, 07 Apr 2014 16:32:05 [STOP] Policy Synchronization application complete.

                                • 13. Re: Odd behavior when downloading files for job...client thinks itself is a peer?
                                  joebaggadonuts Apprentice

                                  Well, allot has changed since July 2011 so this is a bit of a "necro post", but to the point, We had a slower experience in distribution past than we do now. Our fix, while a bit laborious and costly did give the speed and the flexibility that we sought; that is we added preferred servers and established a fixed set of MDCs - Multicast Domain Representatives beneath the "CONFIGURATION" | Multicast Domain Representatives" folder in the management console. In this we have each of the preferred servers setup to provide for their given subnet within the list. we select to not hold elections during the TMC phase and force the use of the specific device. additionally, we do not allow any distribution to be pulled from a peer or from the core. All distributions and patches come from the preferred server and they are set to use 90% of the bandwidth during the deployment. This, coupled with replacing our corrupted LDMS database and cleaning it up, gave us a near instant install capacity from any of the branches in the 5 states we support. All those points not withstanding, a delivery of 5 minutes to a given target is still rather good. Some of ours were taking 20 or 30 minutes to get there and even more if the speed of the download were set low enough and the file large in size. Simply put, LANDesk is about making it happen and NOT about speed of delivery. I dare say that is why an answer is not forthcoming.