- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 06:31 AM
Discovery has been scheduled.
I received the errors like below snap attached.
Also received warnings as well:
Why should I received this type of logs.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 06:01 AM
hi @Selva Arun
From the discovery_credentials table, I've tested the credentials using ip address but the "Authentication Failed" popup appears. So using this way I've tested the credentials but I think the credentials were invalid. am I right?
And due to this all this errors are appeared.
One more thing is there any way to resolved this credentials issue and errors while discovery schedule?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 06:36 AM
Click on error, it will going to show where it failed. Share that screenshot here. Warnings you can avoid if the IP been discovered already.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 07:15 AM
ScreenShot 1 is reffering to the docker pattern failure. Looks like the base CI is already disovered based on your screenshot. Are there any docker services are you trying to discover?
ScreenShot2 is reffering to the linux/ unix server discovery. SSH Credentials are failing on the server you have run discovery. SSH credentails need access to Privileged commands. please refer to below kb article for more info. SSH Privileged Commands - Support and Troubleshooting (servicenow.com)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 12:41 AM
@Community Alums @Pratiksha
Warning:
1. Could not find any valid credentials to authenticate the target for type [Windows]
2. No results returned from probe.
3. SSHTerminalInteractiveCommand: failed to execute: all commands failed to execute from list cli_commands: show vmdevice
Why this warning occurred when discovery is scheduled?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 07:20 AM
Hi Aishwarya,
Error messages and warnings in the system are documented to allow users to recognize the issues they are having and to take steps to resolve their problems.
Please follow the below article how to fix the above errors:
Credentials & Permissions troubleshooting on Discovery, Service Mapping, Orchestration - Support and...
If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.
Thank you for your consideration.
Selva