Dicovery scan go to a loop if the scanned device disconnects

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Discovery 3.2.1
    • Affects Version/s: 3.1.2, Discovery 3.1.8
    • Component/s: Assets Discovery
    • None
    • 2
    • Severity 2 - Major
    • 32

      Issue Summary

      If a discovery agent is disconnected and the connection is aborted, the assets scan will remain on a loop.

      Reconnecting/restarting the agent doesn't release the thread and the scan remains running.

      Only after restarting the service, the thread is released.

      Steps to Reproduce

      1. Execute a scan manual or schedule
      2. One of the devices disconnects during the scan 

      Expected Results

      The scan should continue if one of the devices is disconnected and proceed with the scan.

      Actual Results

      The below exception is thrown in the discovery log file:

      20/09/2023 01:34:49 : Exceptions:
      20/09/2023 01:34:49 : Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
      at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
      at System.IO.BinaryWriter.Write(String value)
      at Insight.Discovery.Tools.Networking.ServerClient.SendMessage(NetMessage netMessage) in C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE-BUILD\DiscoTools\Networking\ServerClient.cs:line 141
      20/09/2023 01:34:49 : An established connection was aborted by the software in your host machine 

      Workaround

      A possibility is to change the configuration to have the agents send the  files to a specified directory and have Discovery access the files from there, this can be accomplished with the below steps:

      The change may be deployed to all agents (if reachable) following this procedure:

      1. On the Host running the Discovery Tool - save a copy of the agent.cfg file (copy it over from any agent)
      2. In the Discovery Tool>Service Tab - click on "Agent File Transfer list" - click the green '+' and browse to add the Agent.cfg file you have just saved.
      3. Exit the tool.
      4. Update the Agent.cfg file with the File Transfer parameters (either for File Copy of for SFTP). You shall find more details on the below link:
        1. How to force agents to transfer data to a target path
      5. The next time the Discovery tool will trigger the Agents - it should also transfer over the agent.cfg file
      6. Once the file was transmitted - it will be picked up by the agent on its next service restart. so, within a day or two, the agents which got the file should start to transmit their scans to the shared location.

            Assignee:
            Zakhar Listiev (Inactive)
            Reporter:
            Sergio Soto Lopez (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: