kubernetes-retired/kubedash

503 Service Unavailable

Closed this issue · 0 comments

Hi,

I have deployed kubedash on a 1.2 K8s cluster with deploy/bundle.yaml, and I sometimes have "503 Service Unavailable" error.
No more GET requests appears in kubedash container logs, and heapster container have same logs as usual


2016/09/06 08:18:56 http: multiple response.WriteHeader calls
2016/09/06 08:18:56 http: multiple response.WriteHeader calls
E0906 08:19:07.917226       1 model_handlers.go:757] timestamp argument cannot be parsed: parsing time "2016-09-01T10:22:00 02:00" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "Z07:00"
2016/09/06 08:19:07 http: multiple response.WriteHeader calls
E0906 08:19:07.917390       1 model_handlers.go:626] unable to get pod metric: the requested pod is not present in the specified namespace
2016/09/06 08:19:07 http: multiple response.WriteHeader calls
E0906 08:19:08.010443       1 model_handlers.go:757] timestamp argument cannot be parsed: parsing time "2016-09-01T10:22:00 02:00" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "Z07:00"
2016/09/06 08:19:08 http: multiple response.WriteHeader calls
E0906 08:19:08.010536       1 model_handlers.go:626] unable to get pod metric: the requested pod is not present in the specified namespace
E0906 08:19:25.314026       1 model_handlers.go:757] timestamp argument cannot be parsed: parsing time "2016-09-01T10:22:00 02:00" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "Z07:00"
2016/09/06 08:19:25 http: multiple response.WriteHeader calls
E0906 08:19:25.423170       1 model_handlers.go:757] timestamp argument cannot be parsed: parsing time "2016-09-01T10:22:00 02:00" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "Z07:00"
2016/09/06 08:19:25 http: multiple response.WriteHeader calls

I have to restart pod to make it work