Open Cryptophobia opened 6 years ago
From @vdice on January 11, 2017 21:40
Hmmm, I'm not able to reproduce this issue w/ same telegraf image (also GKE, k8s server 1.4.7)
Is there a way to dig it deeper. I did try to add AGENT_DEBUG:true, AGENT_QUITE:false but doesn't help much from log.
@jchauncey any suggestions on how to debug?
From @jchauncey on January 11, 2017 21:45
Nope. I've seen this before but I'm not sure what the cause was. Is it still happening?
On Jan 11, 2017 4:40 PM, "Vaughn Dice" notifications@github.com wrote:
Hmmm, I'm not able to reproduce this issue w/ same telegraf image (also GKE, k8s server 1.4.7)
Is there a way to dig it deeper. I did try to add AGENT_DEBUG:true, AGENT_QUITE:false but doesn't help much from log.
@jchauncey https://github.com/jchauncey any suggestions on how to debug?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/deis/monitor/issues/165#issuecomment-272003563, or mute the thread https://github.com/notifications/unsubscribe-auth/AAaRGG44WRs6bIBsrBRaYhCJH2f-7BPGks5rRUxLgaJpZM4LLgQt .
From @zinuzoid on January 12, 2017 11:1
@jchauncey yes, it's still happen.
2017-01-12T11:00:40.151027731Z 2017/01/12 11:00:40 E! ERROR in input [inputs.kubernetes]: Errors encountered: [Error parsing response: parsing time "null" as ""2006-01-02T15:04:05Z07:00"": cannot parse "null" as """]
2017-01-12T11:00:50.990826710Z 2017/01/12 11:00:50 E! ERROR in input [inputs.kubernetes]: Errors encountered: [Error parsing response: parsing time "null" as ""2006-01-02T15:04:05Z07:00"": cannot parse "null" as """]
From @stuszynski on February 6, 2017 15:0
@zinuzoid I encounter a similar issue. Telegraf is using url = "http://10.240.0.19:10255"
for connecting to kubelet, but your kubelet is most likely listen on HTTPS only.
From @stuszynski on February 7, 2017 12:38
Sorry, my bad. The http://<node-ip>:10255
refer to the unsecured read-only port available on each kubelet.
--read-only-port int32 The read-only port for the Kubelet to serve on with no authentication/authorization, and for localhost healthz endpoint (set to 0 to disable) (default 10255)
I check it manually and I'm sure it provide data on this URL from a telegraf container. We still, however, experience above issue.
From @zinuzoid on December 13, 2016 9:23
Metric in Grafana seems doesn't work, so I check telegraf and there're some error logs from pods.
I'm running cluster in GKE k8s version 1.4.6 Images: quay.io/deis/telegraf:v2.7.0
Is there a way to dig it deeper. I did try to add AGENT_DEBUG:true, AGENT_QUITE:false but doesn't help much from log.
Copied from original issue: deis/monitor#165