How to determine which discovery is running in Spectrum?

book

Article ID: 206640

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

Discoveries got locked up and we are looking for some way to know what discovery job is actually locked up.   Are there any ways to determine or see this?  I turned on debug, and I can confirm that things are locked, and something is discovering, but nothing is very clear.    Any ideas would be appreciated.

Environment

Release : 20.2

Component : Spectrum Discovery & Modeling

Resolution

Enable AutoDiscovery on all OneClick servers.  If you have multiple OneClick servers, only one of them actually processes the discovery thread.  To determine which discovery is running, you need to enable Autodsicovery debug on all OneClick servers. Navigate to the OneClick Administration web page - Debugging - Web Server Debug (Runtime) page -s set AutoDiscovery to On - scroll to the bottom of the page and click Apply.

Once enabled, review the $SPECROOT/tomcat/logs/stdout.log (Windows) or catalina.out (Linux) for Discover detail.  It will look like this:

Jan 14, 2021 06:15:12.034 (http-nio-8080-exec-147) (ADISC) - ClientConfig updated for [email protected]c0000, request = INITIAL, on landscape  (0x1000000), mh = 0x100007e
Jan 14, 2021 06:15:12.138 (http-nio-8080-exec-151) (ADISC) - ClientConfig updated for [email protected]c0000, request = 7, on landscape  (0x1000000), mh = 0x100007e
Jan 14, 2021 06:15:18.758 (http-nio-8080-exec-65) (ADISC) - ClientConfig updated for [email protected]c0000, request = 4, on landscape  (0x1000000), mh = 0x100007e
Jan 14, 2021 06:15:18.758 (http-nio-8080-exec-65) (ADISC) - writeConfigurations( config MH = 0x100007e, landscape =  ) starting
Jan 14, 2021 06:15:18.758 (http-nio-8080-exec-65) (ADISC) - writeConfigurations( mh = 0x100007e, landscape =  ) returning true
Jan 14, 2021 06:15:18.774 (http-nio-8080-exec-129) (ADISC) - ClientConfig updated for [email protected]c0000, request = DISCOVER, on landscape  (0x1000000), mh = 0x100007e
Jan 14, 2021 06:15:18.774 (http-nio-8080-exec-129) (ADISC) - writeConfigurations( config MH = 0x100007e, landscape =  ) starting
Jan 14, 2021 06:15:18.774 (http-nio-8080-exec-129) (ADISC) - writeConfigurations( mh = 0x100007e, landscape =  ) returning true
Jan 14, 2021 06:15:49.255 (PoolThread-48: GlobalPool => DiscoveryJob) (ADISC) - ConfigMonitor received JobCompleteEvent for 0x100007e, type = 0
Jan 14, 2021 06:15:49.255 (PoolThread-48: GlobalPool => DiscoveryJob) (ADISC) - writeResultSet( configMH = 0x100007e, landscape =  ) starting
Jan 14, 2021 06:15:49.255 (PoolThread-48: GlobalPool => DiscoveryJob) (ADISC) - writeResultSet( config = 0x100007e, landscape =  ) returning true
Jan 14, 2021 06:15:49.726 (PoolThread-51: GlobalPool => ModelingJob) (ADISC) - ConfigMonitor received JobCompleteEvent for 0x100007e, type = 1
Jan 14, 2021 06:15:49.726 (PoolThread-51: GlobalPool => ModelingJob) (ADISC) - writeResultSet( configMH = 0x100007e, landscape =  ) starting
Jan 14, 2021 06:15:49.726 (PoolThread-51: GlobalPool => ModelingJob) (ADISC) - writeResultSet( config = 0x100007e, landscape =  ) returning true

You can then search the Spectrum database for that model.  Log into the SpectroSERVER bash shell, and navigate to the vnmsh directory:

./connect


[email protected] /c/win32app/Spectrum/vnmsh
$ ./show models | grep -i adisc
0x1000081   Simdepot                          0x25e0004   AdiscConfig
0x100007e   Dev_2                             0x25e0004   AdiscConfig
0x1000068   Dev_lab                           0x25e0004   AdiscConfig
0x10001e5   Simdepot                          0x25e0005   AdiscResultSet
0x10000ad   Simdepot                          0x25e0005   AdiscResultSet
0x1000082   Simdepot                          0x25e0005   AdiscResultSet
0x1000080   Dev_2                             0x25e0005   AdiscResultSet
0x1000069   Dev_lab                           0x25e0005   AdiscResultSet

 
[email protected] /c/win32app/Spectrum/vnmsh
$ ./show models | grep 0x100007e
0x100007e   Dev_2                             0x25e0004   AdiscConfig

From this detail I can see that "Dev_2" discovery is running.