- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-05-2024 09:22 PM
When i was installed prisma cloud console on k8s, the console pod status being to "CrashLoopBackOff".
I see the logs "utils.go:359 command "/usr/bin/mongod..." exited abruptly: signal: aborted (core dumped)".
kubectl logs "pod-name" -n twistlock.
What is the problem? How can i check this issue?
08-06-2024 09:30 AM
Hi @YeongukMo
There might be a number of causes of this issue; from instance may I suggest start troubleshooting at K8, check for resource limits. Taake a look to the following article for a troubleshooting guide:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNRSCA4
Also refer to our documentation about deploying Prisma Cloud on Kubernetes:
Alan
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!