Not able to discover Linux servers in ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2024 08:38 AM
Hi Community,
We have recently upgraded our ServiceNow instance to Vancouver. And after the upgrade we found that some of Linux server from specific region are not getting discover, these servers use dedicated "SSH Private Key" credential added in credential table for this region. While other Linux servers getting discovered successfully in ServiceNow which use different credentials.
We have already checked with Linux admin team and there is no issue in the credentials.
Please suggest us some further troubleshooting steps.
Thanks and regards,
Nikhil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2024 10:41 AM
Hi,
What errors are you getting in the logs? Have you tried testing the credentials against one of the machines?
Regards,
Nikals
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2024 10:45 AM
Hi Niklas,
We are authentication fail error when we test the credentials. and in discovery logs we are getting "Adding target to blacklist. No valid credential found for types [SSH Password,SSH Private Key,Azure SSH Certificate]"
Regards,
Nikhil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2024 11:32 AM
Hi,
Sounds like there is some issue with the credentials. SSH Private key needs to be in PEM format and correctly entered in the credential record. Look at these examples and double check your entry.
Regards,
Niklas

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2024 11:06 AM
@Nikhil kumar ma Open your ssh credential which you have configured in ServiceNow and try to test the Linux server IP with your mid server. see if that is successfully validated ? if not then probably you have credential issue.
Also try to add mid server parameter "mid.ssh.use_snc" as true and then do the quick discovery to test if its connecting or not.
Thanks,
Harsh