mozilla-releng/balrog

fluentbit-gke: Failed to parse time (24/Mar/2022:21:43:44 +0000)

Opened this issue · 0 comments

gcloud logs for balrog show this error with fair frequency. No known consequence, but avoiding it would help make the logs easier to scan for "real" errors.

{
"insertId": "jxnebx06sf0y8g34",
"jsonPayload": {
"pid": "1",
"message": "Failed to parse time (24/Mar/2022:21:43:44 +0000): parsing time "24/Mar/2022:21:43:44 +0000" as "2006-01-02T15:04:05Z07:00": cannot parse "ar/2022:21:43:44 +0000" as "2006""
},
"resource": {
"type": "k8s_container",
"labels": {
"cluster_name": "balrog-prod-v1",
"location": "us-west1",
"project_id": "moz-fx-balrog-prod-3fa2",
"container_name": "fluentbit-gke",
"pod_name": "fluentbit-gke-xjs4t",
"namespace_name": "kube-system"
}
},
"timestamp": "2022-03-24T21:43:49.922255525Z",
"severity": "ERROR",
"labels": {
"k8s-pod/k8s-app": "fluentbit-gke",
"k8s-pod/kubernetes_io/cluster-service": "true",
"k8s-pod/component": "fluentbit-gke",
"k8s-pod/controller-revision-hash": "77c8b4d768",
"k8s-pod/pod-template-generation": "5",
"compute.googleapis.com/resource_name": "gke-balrog-prod-v1-default-pool-v1-39153909-89bz"
},
"logName": "projects/moz-fx-balrog-prod-3fa2/logs/stderr",
"sourceLocation": {
"file": "metrics.go",
"line": "30"
},
"receiveTimestamp": "2022-03-24T21:43:54.912620962Z"
}