What you expected to happen?
What happened?
How to reproduce it?
Anything else we need to know?
Versions:
$ scope version
$ docker version
$ uname -a
$ kubectl version
Logs:
$ docker logs weavescope
or, if using Kubernetes:
$ kubectl logs <weave-scope-pod> -n <namespace>
hi guys, i hope i can find some one who can help with this problem i'am facing.
I installed weavescope and in the begining it was workinf fine then suddenlty i started to have some problems: it does no longer show anything saying no reports were set by probes recently.
This is the logs am getting from the scope agent pods:
kiram@skyleader:~$ kubectl logs weave-scope-agent-nqv9x -n weave
time="2019-07-01T09:15:19Z" level=info msg="publishing to: weave-scope-app.weave.svc.cluster.local:80"
INFO: 2019/07/01 09:15:19.223013 Basic authentication disabled
INFO: 2019/07/01 09:15:19.228243 command line args: --mode=probe --probe-only=true --probe.docker=true --probe.docker.bridge=docker0 --probe.kubernetes.role=host weave-scope-app.weave.svc.cluster.local:80
INFO: 2019/07/01 09:15:19.228638 probe starting, version 1.11.2, ID 29a650ed8e8677c8
WARN: 2019/07/01 09:15:19.366531 Cannot resolve 'weave-scope-app.weave.svc.cluster.local': lookup weave-scope-app.weave.svc.cluster.local on 10.96.0.10:53: write udp 10.10.10.6:40852->10.96.0.10:53: write: operation not permitted
WARN: 2019/07/01 09:15:19.409861 Cannot resolve 'scope.weave.local.': dial tcp 172.17.0.1:53: connect: connection refused
ERRO: 2019/07/01 09:15:19.903695 Error checking version: Get https://checkpoint-api.weave.works/v1/check/scope-probe?arch=amd64&flag_kernel-version=4.15.0-54-generic&flag_kubernetes_enabled=true&flag_os=linux&os=linux&signature=fmoGdg1u4kXxHAJNrg58p0%2FXSWiM4OlFZ4DE9TF0zAk%3D&version=1.11.2: dial tcp: lookup checkpoint-api.weave.works on 10.96.0.10:53: write udp 10.10.10.6:45638->10.96.0.10:53: write: operation not permitted
ERRO: 2019/07/01 09:15:20.225383 Error checking version: Get https://checkpoint-api.weave.works/v1/check/scope-probe?arch=amd64&flag_kernel-version=4.15.0-54-generic&flag_kubernetes_enabled=true&flag_os=linux&os=linux&signature=fmoGdg1u4kXxHAJNrg58p0%2FXSWiM4OlFZ4DE9TF0zAk%3D&version=1.11.2: dial tcp: lookup checkpoint-api.weave.works on 10.96.0.10:53: write udp 10.10.10.6:50591->10.96.0.10:53: write: operation not permitted
WARN: 2019/07/01 09:15:22.041220 Error collecting weave status, backing off 10s: Get http://127.0.0.1:6784/report: dial tcp 127.0.0.1:6784: connect: connection refused. If you are not running Weave Net, you may wish to suppress this warning by launching scope with the --weave=false option.
WARN: 2019/07/01 09:15:32.044697 Error collecting weave status, backing off 20s: Get http://127.0.0.1:6784/report: dial tcp 127.0.0.1:6784: connect: connection refused. If you are not running Weave Net, you may wish to suppress this warning by launching scope with the --weave=false option.
WARN: 2019/07/01 09:15:52.046718 Error collecting weave status, backing off 40s: Get http://127.0.0.1:6784/report: dial tcp 127.0.0.1:6784: connect: connection refused. If you are not running Weave Net, you may wish to suppress this warning by launching scope with the --weave=false option.
write udp 10.10.10.6:40852->10.96.0.10:53: write: operation not permitted
This seems to be your main problem: the process cannot send a DNS request.
I haven't seen this type of error before. Is it possible you have a firewall rule in place blocking DNS traffic?
i am also facing the same isse
This error maybe is that the env IPALLOC_RANGE of weave's config is not correct.