monocular
monocular copied to clipboard
Timeout to connect repo url
# kubectl logs monocular-monocular-api-688f54cc85-b4lbx -n kube-system time="2018-07-02T12:09:28Z" level=info msg="Configuration bootstrap init" configFile="/monocular/config/monocular.yaml" time="2018-07-02T12:09:28Z" level=info msg="Configuration file found!" time="2018-07-02T12:09:28Z" level=info msg="Loading CORS from config file" time="2018-07-02T12:09:28Z" level=info msg="Loading repositories from config file" time="2018-07-02T12:09:28Z" level=info msg="Configuration bootstrap finished" time="2018-07-02T12:09:41Z" level=info msg="Using cache directory" path="/monocular/repo-data" time="2018-07-02T12:10:11Z" level=error msg="error on refresh charts from repo" error="Get http://10.21.1.69:8879/index.yaml: dial tcp 10.21.1.69:8879: i/o timeout" repo=&{ObjectIdHex("5b3a1605b624845ad604693f") stable https://kubernetes-charts.storage.googleapis.com/index.yaml https://github.com/kubernetes/charts/tree/master/stable} time="2018-07-02T12:10:11Z" level=warning msg="authentication is disabled" error="no signing key, ensure MONOCULAR_AUTH_SIGNING_KEY is set" time="2018-07-02T12:10:11Z" level=info msg="Started Monocular API server" addr=":8081" [negroni] 2018-07-02T12:10:55Z | 200 | 114.993µs | 10.100.21.8:8081 | GET /healthz [negroni] 2018-07-02T12:11:25Z | 200 | 93.905µs | 10.100.21.8:8081 | GET /healthz
cc @prydonius
@FengyunPan2 are you sure your repo is connectable?
@prydonius yepe, I have 2 pod for monocular api, one can connect repo, another can not connect repo.
# kubectl get pod -n kube-system | grep monocular-api monocular-monocular-api-688f54cc85-d9dxr 1/1 Running 9 1h monocular-monocular-api-688f54cc85-mntgt 1/1 Running 8 1h # kubectl logs monocular-monocular-api-688f54cc85-d9dxr -n kube-system | grep 'Downloading metadata' | tail -2 time="2018-07-03T02:26:10Z" level=info msg="Downloading metadata" dest="/monocular/repo-data/chinac/consul/3.0.0/chart.tgz" source="http://10.21.1.69:8879/consul-3.0.0.tgz" time="2018-07-03T02:26:10Z" level=info msg="Downloading metadata" dest="/monocular/repo-data/chinac/elasticsearch/0.4.9/chart.tgz" source="http://10.21.1.69:8879/elasticsearch-0.4.9.tgz" # kubectl logs monocular-monocular-api-688f54cc85-mntgt -n kube-system | grep timeout time="2018-07-03T02:25:56Z" level=error msg="error on refresh charts from repo" error="Get http://10.21.1.69:8879/index.yaml: dial tcp 10.21.1.69:8879: i/o timeout" repo=&{ObjectIdHex("5b3adaa8b8eb2aee5b217025") chinac http://10.21.1.69:8879 https://github.com/kubernetes/charts/tree/master/stable} time="2018-07-03T03:26:26Z" level=error msg="error on refresh charts from repo" error="Get http://10.21.1.69:8879/index.yaml: dial tcp 10.21.1.69:8879: i/o timeout" repo=&{ObjectIdHex("5b3adaa8b8eb2aee5b217025") chinac http://10.21.1.69:8879 https://github.com/kubernetes/charts/tree/master/stable}
I have the same issue using the following helm repository in monocular: https://jroucheton.github.io/miniapps/index.yaml
I am using only one pod for monocular-api.
time="2018-08-21T23:28:54Z" level=error msg="error on refresh charts from repo" error="Get http://jroucheton.github.io/miniapps/index.yaml: dial tcp 185.199.110.153:80: i/o timeout" repo=&{ObjectIdHex("5b7c1b913cbda5889b1bb634") test http://jroucheton.github.io/miniapps }
On my side, It seems that this pod cannot access to external URL...