Linux SSH Discovery Classification Issues

mguerrero
Kilo Contributor

‎04-11-2024 08:26 AM - edited ‎04-11-2024 08:28 AM

We currently use an SSH private key Credential to discover Linux Servers. The issue I keep seeing is there are Linux Servers that are not coming in through discovery. I checked with our Unix team and the credential is on the servers we are trying to bring in to the CMDB. The current Discovery error I see is "Active, couldn't classify". If I try running adhoc discovery 10 to 15 times, it may classify the device but not through a schedule and even at that it may take many manual attempts. I checked with our unix team and the credential is working as intended as it can discover other Linux servers. 

 

Has anyone had an issue similar to this or have any advice on fixing, trouble shooting this issue?

Labels:
0 Helpfuls
  • 545 Views
1 REPLY 1

Selva Arun
Mega Sage
Mega Sage

‎04-18-2024 10:56 AM

Hi,

Could you please provide the discovery log message? I'm having difficulty understanding the issue fully. The "Active, couldn't classify" message might appear if the credentials fail during the initial login to the device (UNIX-Classification probe) or while executing the pattern- Linux Server. Some steps in the pattern requires access to execute commands. Have you checked the input ECC_Queue for UNIX-Classify probes and SSHTerminalInteractiveCommand javascriptProbe? Does it pass the classification phase, is the Horizontal DiscoveryProbe Linux pattern launched or triggered?

 

Thank you.

0 Helpfuls