Skip to main content

Error codes

PrivX Key Manager will emit some events, typically error conditions but also warnings and diagnostics, with defined error codes. Messages with a defined code will begin with letters UKM- followed by five digits. The code will be followed by a semicolon and the fixed name of the event, which is followed by a semicolon and the variable human-readable part.

The errors are returned by the APIs and displayed by the GUI and by the command line clients. If an error with a defined code causes a job to fail, that job's error field will start with the code.

Events with defined codes will also be written to the local syslog at the Key Manager Server where they happened.

UKM-10000​

Event: Host connection failed

Description: Opening a connection to the host failed. This can happen due to multiple causes, such as network connectivity issues or local changes on the host causing the authentication to fail. Check the error details to see how to remediate the situation.

UKM-10001​

Event: Host connection timeout

Description: Opening a connection to the host ended in a timeout on the PKM server side. This can happen because of network connectivity issues or because the opened connection did not return expected output to the PKM server.

UKM-10002​

Event: Hostkey changed

Description: The host being connected to gave a host key which does not match with the host keys previously stored by PKM for the host. Either the host key has been changed locally on the host or the IP of the host has changed and the PKM server's connection ended up in a different host than expected.

UKM-10003​

Event: Downloaded file corrupted

Description: During an operation on a host, a file had different length after being downloaded than it had on the file system on the host. Possibly a broadcast message was mixed up in the file download or a problem with the terminal caused the download to be corrupted.

UKM-20000​

Event: Key out of validity period

Description: A key could not be restored because its validity period has expired. To successfully restore the target key, set its validity period, then rerun this operation.

UKM-25000​

Event: Out of identity file slots ** Description:** A new private key was to be generated, but there were no open slots (IdentityFile entries from either the product defaults or the global or user-specific client configurations) for the key. To handle the situation, either re-use an existing key, select an algorithm with open slots in the client configuration or request PKM to add a new entry to the client configuration.

UKM-25001​

Event: Key-activity scan failed to find key activity Description: Key-activity scan did not find any key-activity events from a host. This may be because the host logs SSH logins to unexpected locations, or because the host does not log SSH logins at all. To fix this issue, ensure that SSH logins are logged to configured locations on the target host: Ensure that syslog is running and configured correctly. You may also need to restart the syslog service. If the target host runs any OpenSSH-based SSH servers, ensure they are running with appropriate logging levels. If the host logs to custom locations, also ensure those locations are included in the Key Manager host settings.