Grafana container in CrashLoopBackoff on GKE #582
Comments
xiaods
added a commit
to xiaods/conduit
that referenced
this issue
Mar 29, 2018
this is a known issue with grafana in k8s. `grafana/grafana:5.0.4` was just released today. update the repo from `5.0.3` to `5.0.4` fixed issues linkerd#582
xiaods
added a commit
to xiaods/conduit
that referenced
this issue
Mar 29, 2018
this is a known issue with grafana in k8s. `grafana/grafana:5.0.4` was just released today. update the repo from `5.0.3` to `5.0.4` fixed issues linkerd#582 Signed-off-by: Deshi Xiao <xiaods@gmail.com>
xiaods
added a commit
to xiaods/conduit
that referenced
this issue
Mar 29, 2018
this is a known issue with grafana in k8s. grafana/grafana:5.0.4 was just released today. update the repo from 5.0.3 to 5.0.4 fixed issues linkerd#582 Signed-off-by: Deshi Xiao <xiaods@gmail.com>
siggy
pushed a commit
that referenced
this issue
Mar 29, 2018
this is a known issue with grafana in k8s. grafana/grafana:5.0.4 was just released today. update the repo from 5.0.3 to 5.0.4 fixed issues #582 Signed-off-by: Deshi Xiao <xiaods@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
User reported the Grafana container in CrashLoopBackoff, with Conduit 0.3.1, on GKE.
Related issues:
Confirmed fix is in
grafana/grafana:master. Will wait for this change to propagate to a release and then we can update to that image:log output:
$ stern grafana -n conduit + grafana-66d57d5875-2zlxc › conduit-proxy grafana-66d57d5875-2zlxc conduit-proxy INFO conduit_proxy using controller at HostAndPort { host: DnsName("proxy-api.conduit.svc.cluster.local"), port: 8086 } grafana-66d57d5875-2zlxc conduit-proxy INFO conduit_proxy routing on V4(127.0.0.1:4140) grafana-66d57d5875-2zlxc conduit-proxy INFO conduit_proxy proxying on V4(0.0.0.0:4143) to None grafana-66d57d5875-2zlxc conduit-proxy INFO conduit_proxy::transport::connect "controller-client", DNS resolved DnsName("proxy-api.conduit.svc.cluster.local") to 10.196.240.97 grafana-66d57d5875-2zlxc conduit-proxy ERR! conduit_proxy::control "controller-client", controller error: Error attempting to establish underlying session layer: operation timed out after Duration { secs: 3, nanos: 0 } grafana-66d57d5875-2zlxc conduit-proxy INFO conduit_proxy::transport::connect "controller-client", DNS resolved DnsName("proxy-api.conduit.svc.cluster.local") to 10.196.240.97 + grafana-66d57d5875-2zlxc › grafana grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards/..data': Read-only file system grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards/..2018_03_16_23_33_08.827149221/conduit-viz.json': Read-only file system grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards/..2018_03_16_23_33_08.827149221/conduit-health.json': Read-only file system grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards/..2018_03_16_23_33_08.827149221': Read-only file system grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards/conduit-viz.json': Read-only file system grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards/conduit-health.json': Read-only file system grafana-66d57d5875-2zlxc grafana chown: changing ownership of '/var/lib/grafana/dashboards': Read-only file systemThe text was updated successfully, but these errors were encountered: