About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
The message "Failed to open key file" is shown on the vSnap Server after replication fails from target to source vSnap Server.
Symptom
After a replication repair on an Encrypted Pool, the pool becomes offline. The message "Failed to open key file" may be viewed in the journalctl.log.
<timestamp> <VsnapName> startup_data: Importing vsnap pools
<timestamp> <VsnapName> startup_data: Opening LUKS device vsencryptdisk-<deviceID>
<timestamp> <VsnapName> startup_data: Failed to open key file.
<timestamp> <VsnapName> startup_data: Opening LUKS device vsencryptdisk-<deviceID>
<timestamp> <VsnapName> startup_data: Failed to open key file.
<timestamp> <VsnapName> startup_data: Opening LUKS device vsencryptdisk-<deviceID>
<timestamp> <VsnapName> startup_data: Opening LUKS device vsencryptdisk-<deviceID>
<timestamp> <VsnapName> startup_data: Failed to open key file.
<timestamp> <VsnapName> startup_data: Opening LUKS device vsencryptdisk-<deviceID>
<timestamp> <VsnapName> startup_data: Failed to open key file.
<timestamp> <VsnapName> startup_data: Opening LUKS device vsencryptdisk-<deviceID>
In the messages.log the same errors (as above) are seen and many vsnap services fail to start:
<timestamp> <VsnapName> systemd[1]: vsnap-data.service: Failed with result 'exit-code'.
<timestamp> <VsnapName> systemd[1]: Failed to start vSnap Data Services.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap Replication Services.
<timestamp> <VsnapName> systemd[1]: vsnap-repl.service: Job vsnap-repl.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap API Services.
<timestamp> <VsnapName> systemd[1]: vsnap-api.service: Job vsnap-api.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap Maintenance Services.
<timestamp> <VsnapName> systemd[1]: vsnap-maint.service: Job vsnap-maint.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap Worker Services.
<timestamp> <VsnapName> systemd[1]: vsnap-work.service: Job vsnap-work.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Startup finished in 3.492s (kernel) + 2.674s (initrd) + 16.881s (userspace) = 23.047s.
<timestamp> <VsnapName> systemd[1]: NetworkManager-dispatcher.service: Succeeded.
<timestamp> <VsnapName> setroubleshoot[1830]: failed to retrieve rpm info for /opt/vsnap/run/vsnap.sock
<timestamp> <VsnapName> systemd[1]: Failed to start vSnap Data Services.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap Replication Services.
<timestamp> <VsnapName> systemd[1]: vsnap-repl.service: Job vsnap-repl.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap API Services.
<timestamp> <VsnapName> systemd[1]: vsnap-api.service: Job vsnap-api.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap Maintenance Services.
<timestamp> <VsnapName> systemd[1]: vsnap-maint.service: Job vsnap-maint.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Dependency failed for vSnap Worker Services.
<timestamp> <VsnapName> systemd[1]: vsnap-work.service: Job vsnap-work.service/start failed with result 'dependency'.
<timestamp> <VsnapName> systemd[1]: Startup finished in 3.492s (kernel) + 2.674s (initrd) + 16.881s (userspace) = 23.047s.
<timestamp> <VsnapName> systemd[1]: NetworkManager-dispatcher.service: Succeeded.
<timestamp> <VsnapName> setroubleshoot[1830]: failed to retrieve rpm info for /opt/vsnap/run/vsnap.sock
The some ZFS commands such as "zpool list" and "zpool status" report "no pools available"
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"ARM Category":[{"code":"a8m0z0000001jgyAAA","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
More support for:
IBM Spectrum Protect Plus
Component:
Troubleshooting
Software version:
All Versions
Document number:
6846667
Modified date:
15 December 2022
UID
ibm16846667
Manage My Notification Subscriptions