Installation and environment setup These sections present troubleshooting and solutions for common problems with installation. Missing MongoDB image results in upgrade and installation failureGuardium Insights upgrade becomes stuck because CSV does not updateGuardium Insights upgrade becomes stuck with MongoDBCommunity errorCBC ciphers and SSH vulnerabilitiesSecure Shell (SSH) service error when deploying on Amazon Web Services (AWS)Guardium Insights v3.3.x - Db2 pod stuck in pending stateOccasionally 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 stateOccasionally 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 podsWhen deploying Guardium® Insights on IBM Cloud, you may notice issues with the Db2® pods on the filesystem.Db2 client communication issuesWhen you install Guardium® Insights, you might notice issues with the Db2 pod.Db2 errors for reports and risk servicesExisting universal connector certificate does not work in a restored environmentExisting data mart pull configuration does not work in a restored environmentMongoDB warning in pre-upgrade validation scriptKafka pods in CrashLoop when storage size is not large enoughParent topic: Problems and solutions