5 Replies Latest reply on Jun 3, 2016 1:33 PM by phoffmann

    Extended Device Discovery Service Restarting

    Rookie

      Is it normal behavior for the LANDesk Extended device discovery service on our workstations to stop and start repeatedly?

      It is stopping and starting every, 5, 10 or 15 minutes.

        • 1. Re: Extended Device Discovery Service Restarting
          phoffmann SupportEmployee

          Not overly - it usually just stays running.

           

          A bit more information would be helpful - what version of LANDesk are you using / what version is the client on? Have you got anything immediately useful in the logs for the service / is there stuff in the event log about the service actually crashing / bailing in some form?

           

          Assuming you're on LANDesk 2016, XDD can be used via the self-electing client mode -- where essentially a client performs a check in its broadcast domain about "hey - does anyone have XDD up and running" and if need be, a poll takes place to take over from the (probably shut down) previous XDD device.

           

          So - it's not "normal" as such, but it may not necessarily be something to immediately worry about, if that helps a bit. Having a bit more information about & from the device / service would help along .

           

          If you're on LANDesk Management 9.6 or newer, the logs are usually written to -- %ProgramData%\LANDesk\Log\ -- if there's nothing in the NT event log (which I wouldn't expect unless you're seeing actual crashes) your best bet is to start there.

           

          You can also enable debug-logging as per this article here -- https://community.landesk.com/support/docs/DOC-32532 -- to get more information about what the device is getting up to.

           

          Hope this helps you to get started / further along .

          • 2. Re: Extended Device Discovery Service Restarting
            Rookie

            We implemented 2016 in March so I am new to LANDesk.

            This issue was found by a Windows Server Admin on his workstation in the Windows Event Log.

            After looking in the LANDesk Logs, this workstation is an 'XDD Client'.

             

            Here is the contents for the past hour in the XDDClient.log file:

            Tue, 31 May 2016 12:56:18 4800: Service shutdown has been requested, setting shutdown event

            Tue, 31 May 2016 12:56:18 4800: Shutdown event set

            Tue, 31 May 2016 12:56:18   4800   8636 Service is shutting down

            Tue, 31 May 2016 12:56:18 4800 Main: Exiting

            Tue, 31 May 2016 12:56:18   4800   6592 Service stopped

            Tue, 31 May 2016 12:56:37   6236   8244 Windows Platform 2, version 6.1 Service Pack 1

            Tue, 31 May 2016 12:56:37   6236   1448 Service started

            Tue, 31 May 2016 12:56:37 6236[1448]: Starting XDD Service Main

            Tue, 31 May 2016 12:57:07 CreateClientThread: about to call CreateThread, ThreadState=0

            Tue, 31 May 2016 13:04:52 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

            Tue, 31 May 2016 13:11:17 6236: Service shutdown has been requested, setting shutdown event

            Tue, 31 May 2016 13:11:17 6236: Shutdown event set

            Tue, 31 May 2016 13:11:17   6236   8244 Service is shutting down

            Tue, 31 May 2016 13:11:17 6236 Main: Exiting

            Tue, 31 May 2016 13:11:17   6236   1448 Service stopped

            Tue, 31 May 2016 13:11:35   6416    212 Windows Platform 2, version 6.1 Service Pack 1

            Tue, 31 May 2016 13:11:35   6416   6888 Service started

            Tue, 31 May 2016 13:11:35 6416[6888]: Starting XDD Service Main

            Tue, 31 May 2016 13:12:05 CreateClientThread: about to call CreateThread, ThreadState=0

            Tue, 31 May 2016 13:26:15 6416: Service shutdown has been requested, setting shutdown event

            Tue, 31 May 2016 13:26:15 6416: Shutdown event set

            Tue, 31 May 2016 13:26:15   6416    212 Service is shutting down

            Tue, 31 May 2016 13:26:15 6416 Main: Exiting

            Tue, 31 May 2016 13:26:15   6416   6888 Service stopped

            Tue, 31 May 2016 13:26:46   8476   9004 Windows Platform 2, version 6.1 Service Pack 1

            Tue, 31 May 2016 13:26:46   8476   8408 Service started

            Tue, 31 May 2016 13:26:46 8476[8408]: Starting XDD Service Main

            Tue, 31 May 2016 13:27:16 CreateClientThread: about to call CreateThread, ThreadState=0

            Tue, 31 May 2016 13:41:26 8476: Service shutdown has been requested, setting shutdown event

            Tue, 31 May 2016 13:41:26 8476: Shutdown event set

            Tue, 31 May 2016 13:41:26   8476   9004 Service is shutting down

            Tue, 31 May 2016 13:41:26 8476 Main: Exiting

            Tue, 31 May 2016 13:41:26   8476   8408 Service stopped

            Tue, 31 May 2016 13:41:44   7848    648 Windows Platform 2, version 6.1 Service Pack 1

            Tue, 31 May 2016 13:41:44   7848   8416 Service started

            Tue, 31 May 2016 13:41:44 7848[8416]: Starting XDD Service Main

            Tue, 31 May 2016 13:42:14 CreateClientThread: about to call CreateThread, ThreadState=0

            Tue, 31 May 2016 13:45:58 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

            Tue, 31 May 2016 13:47:18 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

            Tue, 31 May 2016 13:49:24 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

            Tue, 31 May 2016 13:56:24 7848: Service shutdown has been requested, setting shutdown event

            Tue, 31 May 2016 13:56:24 7848: Shutdown event set

            Tue, 31 May 2016 13:56:24   7848    648 Service is shutting down

            Tue, 31 May 2016 13:56:24 7848 Main: Exiting

            Tue, 31 May 2016 13:56:24   7848   8416 Service stopped

            Tue, 31 May 2016 13:56:42   3724   5668 Windows Platform 2, version 6.1 Service Pack 1

            Tue, 31 May 2016 13:56:42   3724   8124 Service started

            Tue, 31 May 2016 13:56:42 3724[8124]: Starting XDD Service Main

            Tue, 31 May 2016 13:57:13 CreateClientThread: about to call CreateThread, ThreadState=0

            • 3. Re: Extended Device Discovery Service Restarting
              phoffmann SupportEmployee

              Interesting.

               

              Can you cross-check against the "SelfElectController.log" log-file (same location)?

               

              Prior to LANDesk 2016, XDD used to be something that you'd statically install on a device. With 2016, we've got this concept of "self electing" among clients for XDD (and possibly other components).

               

              The idea being that you just define an agent as "enabled" (in the client connectivity agent behaviour) and they then check every few minutes "Hey - does anyone in my subnet/broadcast domain have XDD up and running?" ... if they get an answer, fine - if no one responds, an election is held to determine who should be the new XDD agent.

               

              So that's why I'm pointing you at the Self-electing log to see if there's anything of interest there (for instance - constant flip-flop of "I lost the election => I won the election and do XDD again => I lost the election...) type situation that could bring about symptoms like you're seeing. That SHOULDN'T happen (there's a whole

              algorithm around the elections to prevent it from being a problem), but I'm just trying to explain logically how things you're seeing could happen.

               

              I've had multiple agents running for hours / days and the XDD-enabled client's log didn't show any kind of flip-flop'ing like you're seeing it - so it's not normal behaviour and push come to shove, you may want to open up something with support.

               

              So it's not down to something you've done, in case you're concerned . You can just enable XDD being a thing for devices ...

               

              Interesting - not normal - but interesting.

               

              Let me know if you get any insight out of the self-electing log (it's fairly easy to read). Essentially the "winning" of an election will look something like this (most of the other minute-ish interval checks will not be that interesting I think):

              Thu, 02 Jun 2016 10:05:11 Election Results: WON for XDD_ARP with a score of 25

               

              Hope that helps a bit .

              • 4. Re: Extended Device Discovery Service Restarting
                Rookie

                After looking at the SelfElectController.log on one of the workstations, the election is happening every 15minutes. Looks like the scenario you said SHOULDN'T be happening, is!

                 

                We have a LANDesk Consultant coming on site next week, I will bring this up with him to see if he can help but here is part of the log file for an example:

                 

                Thu, 02 Jun 2016 13:31:03   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:32:03   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:32:18 Election Results: LOST for XDD_ARP with a score of 25

                Thu, 02 Jun 2016 13:32:36 Election Results: WON for XDD_ARP with a score of 25

                Thu, 02 Jun 2016 13:32:36 Posting report to the core with coreserver = servername, deviceID = {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, serviceName = XDD_ARP, subnets = xxx.xxx.xxx.x--23

                Thu, 02 Jun 2016 13:32:37 Posting report to the core with coreserver = servername, deviceID = {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, serviceName = XDD_ARP, subnets = xxx.xxx.xxx.x--23

                Thu, 02 Jun 2016 13:33:11   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:34:11   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:35:12   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:36:12   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:37:12   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:38:12   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:39:12   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:40:13   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:41:13   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:42:13   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:43:13   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:44:14   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:45:14   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:46:14   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:47:14   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:47:16 Election Results: LOST for XDD_ARP with a score of 25

                Thu, 02 Jun 2016 13:47:34 Election Results: WON for XDD_ARP with a score of 25

                Thu, 02 Jun 2016 13:47:34 Posting report to the core with coreserver = servername, deviceID = {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, serviceName = XDD_ARP, subnets = xxx.xxx.xxx.x--23

                Thu, 02 Jun 2016 13:47:36 Posting report to the core with coreserver = servername, deviceID = {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, serviceName = XDD_ARP, subnets = xxx.xxx.xxx.x--23

                Thu, 02 Jun 2016 13:48:22   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                Thu, 02 Jun 2016 13:49:22   CSEP_Enabled = true  XDD_ARP_PromoteDesktops = true  Services Enabled:  XDD_ARP

                • 5. Re: Extended Device Discovery Service Restarting
                  phoffmann SupportEmployee

                  Interesting.

                   

                  Doubt the consultant will be able to help in this situation, since I suspect this will require someone to go through code potentially. Depending on your specific level, there are updates for v10 available though that may already address this.

                   

                  The algorithm around the self-election is weighted - so clients who "already are" serving as XDD hosts get some bonus points. If this isn't something we've encountered so far, it'd probably be interesting to get detailed information on those two devices that "ping pong" XDD between each other.

                   

                  On the positive side, you've not to worry about XDD actually being down. There's some oddity in the continued bouncing around for certain - but XDD remains in your network and is (the oddity aside) working & really the problem is just the election process. The rest behaves "as it should" given the circumstances (i.e. - lost elections - stop running XDD).

                   

                  So it's a much lesser problem (as XDD continues to work) than you originally feared .