Connection refused to Compute console due to mongodb issue

 mongo.go:744 Failed to connect to mongo: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: 127.0.0.1:27017, Type: Unknown, Last error: connection() error occurred during connection handshake: dial tcp 127.0.0.1:27017

• Prisma Cloud compute 
• Defender data volume hosed on NFS volume

• First we check that orchestrator and container runtime version are aligned with system requirements

• kubectl get nodes -o wide

• Get the defender logs 

  kubectl logs <defender pod name> -n twistlock

  
  and we will see error as follows
  • mongo.go:744 Failed to connect to mongo: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: 127.0.0.1:27017, Type: Unknown, Last error: connection() error occurred during connection handshake: dial tcp 127.0.0.1:27017
• At this point check on which volume type the defender data folder is mounted on.

  • kubectl get deployment <Prisma Cloud deployment name > -o yaml -n twistlock

    
    output:
  • 
  • 
• Since storageClassName disclosed it's nfs volume at this point I asked the customer to add our recommended NFS flags to their /etc/fstab as documented  here
• As documented in mongodb add the following flags to /etc/fstab on the host where the mongodb is running:

  • bg
    hard
    nolock
    noatime
    nointr