Dashboard: Metric client health check failed with "500 Internal Privoxy Error"

Created on 15 Nov 2017  路  1Comment  路  Source: kubernetes/dashboard

Environment
Dashboard version: 1.7.1
Kubernetes version: 1.8.3
Operating system: ubuntu16 lts

my dashboard didn't see heapster graph. i found the error in the log:

2017/11/15 02:31:25 [2017-11-15T02:31:25Z] Outcoming response to 10.244.0.0:50361 with 200 status code
2017/11/15 02:31:36 [2017-11-15T02:31:36Z] Incoming HTTP/1.1 GET /api/v1/log/kube-system/kubernetes-dashboard-69c5c78645-5vzfw/kubernetes-dashboard?logFilePosition=end&offsetFrom=2000000000&offsetTo=2000000100&previous=false&referenceLineNum=0&referenceTimestamp=newest request from 10.244.0.0:50361: {}
2017/11/15 02:31:36 [2017-11-15T02:31:36Z] Outcoming response to 10.244.0.0:50361 with 200 status code
2017/11/15 02:32:56 Metric client health check failed: an error on the server ("<html>\n<head>\n <title>500 Internal Privoxy Error</title>\n <link rel=\"shortcut icon\" href=\"http://config.privoxy.org/error-favicon.ico\" type=\"image/x-icon\"></head>\n<body>\n<h1>500 Internal Privoxy Error</h1>\n<p>Privoxy encountered an error while processing your request:</p>\n<p><b>Could not load template file <code>no-server-data</code> or one of its included components.</b></p>\n<p>Please contact your proxy administrator.</p>\n<p>If you are the proxy administrator, please put the required file(s)in the <code><i>(confdir)</i>/templates</code> directory.  The location of the <code><i>(confdir)</i></code> directory is specified in the main Privoxy <code>config</code> file.  (It's typically the Privoxy install directory).</p>\n</body>\n</html>") has prevented the request from succeeding (get services heapster). Retrying in 30 seconds.
2017/11/15 02:35:07 Metric client health check failed: an error on the server ("<html>\n<head>\n <title>500 Internal Privoxy Error</title>\n <link rel=\"shortcut icon\" href=\"http://config.privoxy.org/error-favicon.ico\" type=\"image/x-icon\"></head>\n<body>\n<h1>500 Internal Privoxy Error</h1>\n<p>Privoxy encountered an error while processing your request:</p>\n<p><b>Could not load template file <code>no-server-data</code> or one of its included components.</b></p>\n<p>Please contact your proxy administrator.</p>\n<p>If you are the proxy administrator, please put the required file(s)in the <code><i>(confdir)</i>/templates</code> directory.  The location of the <code><i>(confdir)</i></code> directory is specified in the main Privoxy <code>config</code> file.  (It's typically the Privoxy install directory).</p>\n</body>\n</html>") has prevented the request from succeeding (get services heapster). Retrying in 30 seconds.
2017/11/15 02:36:03 [2017-11-15T02:36:03Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.244.0.0:50361: {}
2017/11/15 02:36:03 [2017-11-15T02:36:03Z] Outcoming response to 10.244.0.0:50361 with 200 status code
2017/11/15 02:36:04 [2017-11-15T02:36:04Z] Incoming HTTP/1.1 GET /api/v1/pod/kube-system?filterBy=&itemsPerPage=15&name=&page=1&sortBy=d,creationTimestamp request from 10.244.0.0:50361: {}
2017/11/15 02:36:04 Getting list of all pods in the cluster
2017/11/15 02:36:04 No metric client provided. Skipping metrics.
2017/11/15 02:36:04 Getting pod metrics
2017/11/15 02:36:04 No metric client provided. Skipping metrics.

i deployed it with the yaml on raw.github.com, why it use a proxy?
i try to curl http://heapster.kube-system:80/healthz in other pod then it return ok, from monitoring-grafana.kube-system it seems evething ok too.

then what should i do ?

Most helpful comment

by set the param "--heapster-host=http://heapster.kube-system.svc.cluster.local" in dashboard , the problem was solved.

>All comments

by set the param "--heapster-host=http://heapster.kube-system.svc.cluster.local" in dashboard , the problem was solved.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

maciaszczykm picture maciaszczykm  路  4Comments

dzoeteman picture dzoeteman  路  4Comments

mxey picture mxey  路  3Comments

minminmsn picture minminmsn  路  4Comments

Eddman picture Eddman  路  4Comments