Skip to main content
Trailblazer
March 19, 2025
Question

Daily discovery scans are not working from last one week

  • March 19, 2025
  • 16 replies
  • 527 views

We recently rebooted the primary UVM server and since then the daily scans for discovering domain join servers are not working which is scheduled daily at night. Please suggest. 

16 replies

BeyondTrust Employee
March 19, 2025

If all are the previous commands are returning the Running/Ok, and show the expected scheduled scan job is present, try running the following and check if any scans of the previous scan jobs appear to be stuck running; you can run this from the same path as the other commands; this will output a potentially long list of previously completed scans - scroll through to see if any of them appear to be stuck running or showing some other unexpected state:

btdiscovery getj

AyanWSAuthor
Trailblazer
March 19, 2025

Thanks, I tried that as well and saw the the desired scan did ran every day but after 16th march is only shows (0 of 0 completed) and earlier it used to be (~430 of ~430 completed). It seems there are no assets found during the scans. Kindly suggest. 

 

 

BeyondTrust Employee
March 19, 2025

There does appear to be a scan stuck running from March 17th: “(432 of 433 completed) - Running”. It appears it may be hung up waiting for one specific target to complete.

 

I would suggest to open a case with the BeyondInsight support team and include all the details that we’ve found so far. They will also want Discovery scan logs for review; you can pack up the discovery scan logs by running the following command:

btdiscovery pack

 

This will place a zip file in the following path, which you can upload to the case for review:  C:\Program Files\BeyondTrust\Discovery\Support\

AyanWSAuthor
Trailblazer
March 19, 2025

Thank you, I will do that. :) Appreciate your help. 

GloriaB
BeyondTrust Employee
BeyondTrust Employee
March 25, 2025

For Linux scan issues, enable SSH debug and SSH text before getting a discovery pack: How to enable SSH text and SSH debug logs for the BeyondTrust Discovery Agent

 

Check for the error in the  ####_Phoenix.Service.<datestamp>.log file in C:\Program Files BeyondTrust\Discovery and review the following article: Discovery Scanner cannot connect to target system

AyanWSAuthor
Trailblazer
March 26, 2025

I would like to thank everyone and who has replied to my query. Let me share that this is now sorted and mostly the stuck scans are now processed after restarting the discovery service from the scanner system.