Installation and environment setup

These sections present troubleshooting and solutions for common problems with installation.

Guardium Insights upgrade becomes stuck because CSV does not update
Guardium Insights upgrade becomes stuck with MongoDBCommunity error
CBC ciphers and SSH vulnerabilities
Secure Shell (SSH) service error when deploying on Amazon Web Services (AWS)
Guardium Insights v3.3.x - Db2 pod stuck in pending state
Occasionally a db2u pod may become stuck in the Pending state because the node labeled for the db2u pod does not have enough resources to run the pod. This troubleshooting topic explains how to resolve this issue.
Guardium Insights v3.4.x - Db2 pod stuck in pending state
Occasionally a db2u pod may become stuck in the Pending state because the node labeled for the db2u pod does not have enough resources to run the pod. This troubleshooting topic explains how to resolve this issue.
Troubleshooting Db2 filesystem pods
When deploying Guardium® Insights on IBM Cloud, you may notice issues with the Db2® pods on the filesystem.
Db2 client communication issues
When you install Guardium Insights, you might notice issues with the Db2 pod.
Db2 errors for reports and risk services
Existing universal connector certificate does not work in a restored environment
Existing data mart pull configuration does not work in a restored environment
MongoDB warning in pre-upgrade validation script
Kafka pods in CrashLoop when storage size is not large enough

Parent topic: Problems and solutions