Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR log/harvester.go:282 Read line error: parsing CRI timestamp: parsing time " #11409

Closed
Sam123ben opened this issue Mar 23, 2019 · 3 comments
Assignees
Labels
containers Related to containers use case Filebeat Filebeat Team:Integrations Label for the Integrations team

Comments

@Sam123ben
Copy link

Please post all questions and issues on https://discuss.elastic.co/c/beats
before opening a Github Issue. Your questions will reach a wider audience there,
and if we confirm that there is a bug, then you can open a new issue.

For security vulnerabilities please only send reports to security@elastic.co.
See https://www.elastic.co/community/security for more information.

Please include configurations and logs if available.

For confirmed bugs, please report:

  • Version: 6.6.1
  • Operating System: Linux
  • Discuss Forum URL:
  • Steps to Reproduce:
    helm upgrade --install filebeat --namespace tools stable/filebeat --set indexTemplateLoad[0]=elasticsearch-client:9200

kubectl logs -f filebeat-wln8s -n tools filebeat
{"log":"172.18.182.187" as "2006"; File: /var/lib/docker/containers/cd9f6d83547d8069af596897df22aba170a01699d0d8279c630d61602c8a788e/cd9f6d83547d8069af596897df22aba170a01699d0d8279c630d61602c8a788e-json.log
2019-03-23T11:34:37.736Z INFO [monitoring] log/log.go:144 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":150,"time":{"ms":156}},"total":{"ticks":1330,"time":{"ms":1338},"value":1330},"user":{"ticks":1180,"time":{"ms":1182}}},"handles":{"limit":{"hard":65536,"soft":2048},"open":21},"info":{"ephemeral_id":"e890a013-6d8b-4d03-90df-930e0e64f9b5","uptime":{"ms":30025}},"memstats":{"gc_next":12620624,"memory_alloc":11200720,"memory_total":777612480,"rss":119328768}},"filebeat":{"events":{"added":418,"done":418},"harvester":{"closed":9,"open_files":12,"running":12,"started":21}},"libbeat":{"config":{"module":{"running":0},"reloads":2},"output":{"events":{"acked":253,"batches":5,"total":253},"type":"file","write":{"bytes":310813}},"pipeline":{"clients":2,"events":{"active":0,"filtered":165,"published":253,"total":418},"queue":{"acked":253}}},"registrar":{"states":{"cleanup":35,"current":61,"update":418},"writes":{"success":123,"total":123}},"system":{"cpu":{"cores":4},"load":{"1":0.58,"15":0.56,"5":0.58,"norm":{"1":0.145,"15":0.14,"5":0.145}}}}}}
2019-03-23T11:34:37.986Z INFO log/harvester.go:255 Harvester started for file: /var/lib/docker/containers/cd9f6d83547d8069af596897df22aba170a01699d0d8279c630d61602c8a788e/cd9f6d83547d8069af596897df22aba170a01699d0d8279c630d61602c8a788e-json.log
2019-03-23T11:34:37.986Z INFO log/harvester.go:255 Harvester started for file: /var/lib/docker/containers/f45a5b9557da75cd5ed8560e8995bb2838bc68e6e4f34560f08865b1592693b5/f45a5b9557da75cd5ed8560e8995bb2838bc68e6e4f34560f08865b1592693b5-json.log
2019-03-23T11:34:37.989Z INFO log/harvester.go:255 Harvester started for file: /var/lib/docker/containers/ebb36f414090c33746bd6797f0c12d515c08264cc09b40b2f77cc622baeb4500/ebb36f414090c33746bd6797f0c12d515c08264cc09b40b2f77cc622baeb4500-json.log
2019-03-23T11:34:37.989Z INFO log/harvester.go:255 Harvester started for file: /var/lib/docker/containers/eb13df295d8a1c6c273d4ffe9692ae21250c953f1e0905e67f4252262ee914d7/eb13df295d8a1c6c273d4ffe9692ae21250c953f1e0905e67f4252262ee914d7-json.log
2019-03-23T11:34:38.003Z ERROR log/harvester.go:282 Read line error: parsing CRI timestamp: parsing time "

@Sam123ben
Copy link
Author

#9768

I see this PR but still this issue persist. Can you please let me know what need to be done from y=my end to resolve this issue.

@ruflin ruflin added Filebeat Filebeat Team:Integrations Label for the Integrations team labels Mar 25, 2019
@alvarolobato alvarolobato changed the title ERROR log/harvester.go:282 Read line error: parsing CRI timestamp: parsing time " ERROR log/harvester.go:282 Read line error: parsing CRI timestamp: parsing time " Mar 25, 2019
@alvarolobato alvarolobato added [zube]: Inbox containers Related to containers use case labels Mar 25, 2019
@odacremolbap
Copy link
Contributor

Hi @Sam123ben

I'm not able to reproduce the issue.
My logs are formatted {"log":"something","stream":"stdout","time":"2019-03-28T10:59:54.375970751Z"}

can you log into a node and post here a log line for that file?

@exekias
Copy link
Contributor

exekias commented Apr 8, 2019

Closing as a duplicate of #10957, please provide any further feedback there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Related to containers use case Filebeat Filebeat Team:Integrations Label for the Integrations team
Projects
None yet
Development

No branches or pull requests

5 participants