IBM Support

SSH auto connect fails. Trace shows error: PEM_read_PrivateKey failed (SCI99949)

Troubleshooting


Problem

SSH auto connect fails. Trace shows error: PEM_read_PrivateKey failed (SCI99949)

Symptom

SSH auto connect fails. Trace shows error: PEM_read_PrivateKey failed

Cause

The passphrase in the rsd private key has not been activated with "cmurefresh -s " or has a passphrase is different than the other rsd private keys.

Resolving The Problem

If you are going to use a? passphrase for the SSH keys you need to be sure you use the same passphrase for all the private keys including the system private key. You will also need to do a "cmurefresh -s <passphrase>" every time Enterprise is started. The best and easiest way is when building rsd key pairs with cmusshkey utility when it asks for a passphrase just press enter and don't enter in a passphrase. That way you won't have to be concerned with all the rsd keys having different pasphrases.

[{"Product":{"code":"SSFVK3","label":"IBM Sterling Connect:Enterprise for UNIX"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

PRI24801

Product Synonym

[<p><b>]Fact[</b><p>];Connect:Enterprise UNIX;All releases[<BR>] [<br/>] SCI99949

Document Information

Modified date:
17 December 2019

UID

swg21525092

Page Feedback