This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 92%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAZ%3C/text%3E%3C/svg%3E)
Hi everyone,
I have this error when I want to discover an Oracle Linux server 8.6:
[Failed during SSH discovery. Exit code: -1073479102
Standard Output:
Standard Error:
Exception Message:An exception (-1073479102) caused the SSH command to fail - Server's host key did not match the signature supplied.]
Is there any solution for this exception?
Regards,
Alireza
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
After installing UR4 for SCOM 2019, that error changed to this one:
Signed certificate verification operation was not successful.
Which is a common error. In my case, for oracle Linux 8.6, the error did not help at all. I checked agent's log path (/var/opt/omi/log) and found this error:
SSL: No server certificate found in /etc/opt/omi/ssl/omi.pem. error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small.
After some research about this error I found a command which shows the crypto policy configuration on the server:
update-crypto-policies --show
This command showed that the crypto policy on the server was FUTURE. So I changed it to DEFAULT and the server discovered without any error.
update-crypto-policies --set DEFAULT
Finally, I compared these two policies (FUTURE and DEFAULT) and found that they have a config file named opensslcnf.txt. If we have to keep our policy to FUTURE we can change @SECLEVEL=3 to @SECLEVEL=2 in this file and after that we can discover the server without any problem.
You can find that file in this path: /usr/share/crypto-policies/FUTURE
After discovering, you can change that parameter to its default.
Hi Alireza,
thanks for sharing that, it is very useful. I would encourage you to mark your own thread as answered, this will help others on the search for the same.
Thanks and Regards,
Stoyan
Hi Stoyan,
Sure, I will do that.
Thanks and Regards,
Alireza
Hi guys,
did you check this one out:
SSH discovery trouble (Reddit)
About the Oracle Linux 9.x version, I would say it is not supported as it is not lsited here:
Supported UNIX and Linux operating system versions
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Stoyan Chalakov
I think maybe we should enable ssh DSA algorithm in these servers but I couldn't find a solution for this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 34%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGP%3C/text%3E%3C/svg%3E)
If I run: update-crypto-policies --set DEFAULT:SHA1
I get this error:
Failed during SSH discovery. Exit code: -1073479162
Standard Output:
Standard Error:
Exception Message:An exception (-1073479162) caused the SSH command to fail - Server unexpectedly closed network connection
So something has to be with OpenSSH, Cripto, MAC, ....
I have same error when trying to add Oralce Linux 9.2. SSH works from several machines/users, but cannot add to SCOM.
Error is the same even if I enter wrong discovery credentials.
Grega