ESET PRIVATE Scanning Solution – Table of Contents

Basic troubleshooting

Copy current article URL Share via email

This article (PDF) Whole documentation (PDF)

All container images should log output to STDOUT or STDERR. Logs can be viewed using the standard Kubernetes command:

kubectl logs \<pod_name\>

To check which scanners are currently registered with the Load Balancer, run:

kubectl exec \$(kubectl get pods -l eset=config-agent -o jsonpath='{.items\[\*\].metadata.name}') --
load_balancer_configurator -t esets-load-balancer:50053 -1

If the Load Balancer does not show any registered scanners, restart the Scanner deployment. Scanners are expected to automatically register upon startup.

˄˅