Troubleshooting IBM Hyper Protect Virtual Servers
Refer the following information for troubleshooting issues with IBM Hyper Protect Virtual Servers
Attach data volume within 5 min
If you have a volumes section in the contract, the IBM Hyper Protect Virtual Server instance assumes that a data volume will be attached. The user must either attach the volume during the IBM Hyper Protect Virtual Servers instance creation, or within 5 minutes after instance creation starts. After this 5-minute wait period, the instance shuts down.
Single workload
Currently, only a single workload is supported. Therefore, only a single workload must be specified as part of the docker-compose file.
The contract is mandatory
If you create a IBM Hyper Protect Virtual Servers instance without passing any contract, the instance starts running, and then shuts down eventually.
Contract format is yaml
The contract must follow the YAML format. If the format is not proper, it fails the contract validation check, and the instance shuts down eventually.
Contract schema
If the contract schema is incorrect, the contract validation fails when the instance is booting and the instance shuts down. You can check for errors that are associated with hpcr-contract log identifier in IBM Logging instance.
Contract encryption key
If you opt to use contract encryption, then you must take the correct key. The contract is decrypted by the bootloader and if it is not encrypted by the correct key, then you see decryption failure errors in the serial console of the instance.
Logging configuration failure
When the instance boots, monitor the serial console to identify any errors that are logged by the bootloader or from the logging service. If you don't see any logs reaching your private IBM Logging instance, it might be because your logging configuration failed. Failure to configure logging also leads to the instance shutting down. If your logging configuration fails, you should check whether the logging hostname, port, and ingestion key that is provided in the contract are correct.
Starting an instance with a DASD volume that is a reformatted partition fails
You must format the DASD volume by using the dasdfmt command, when you attach a DASD volume with a contract generated by using a different seed.
Issues with IBM Secure Execution for Linux
For information about troubleshooting issues with IBM Secure Execution for Linux, see Troubleshooting.