question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed parsing container metadata

See original GitHub issue

What happened: After upgrade on 1.4.1 we’ve faced with some problems. Parsing container metadata information is failing , I show much notices in Fluentd pod logs, like: [debug]: parsing container meta information failed for: NAMESPACE/POD_NAME

What you expected to happen:

Correct parsing containers metadata

How to reproduce it (as minimally and precisely as possible): Upgrade to 1.4.1

Environment:

  • Kubernetes version (use kubectl version): 1.11
  • OS (e.g: cat /etc/os-release): RHEL7
  • OpenShift 3.11.98

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:25

github_iconTop GitHub Comments

1reaction
matthewmodestinocommented, Oct 9, 2020

@rockb1017 for fyi ^

Shouldnt impact anything, may just take longer for annotation changes etc to show up…

1reaction
kish3007commented, Oct 7, 2020

@matthewmodestino i see, is it the right config map update?

<label @SPLUNK>
  # Enrich log with k8s metadata
  <filter tail.containers.**>
    @type kubernetes_metadata
    annotation_match [ "^splunk\.com" ]
    watch false                                                    ---> new line added
    cache_ttl 600                                                 ---> new line added
    de_dot false
  </filter>
Read more comments on GitHub >

github_iconTop Results From Across the Web

Amazon ECS container metadata file - AWS Documentation
The metadata file is created on the host instance and mounted in the container as a Docker volume and therefore is not available...
Read more >
Error extracting container id while using Kubernetes metadata
Step 1: Set an identifier for each filestream input · Step 2: Exclude all processed files · Step 3: Use new option names....
Read more >
Internal error: Failed to parse metadata, File aps_php.php
The metafile_uri directory (from the apsc.aps_package table) is missing on the server or the APP-META.xml file is corrupted. Resolution. If the ...
Read more >
Red Hat Satellite 6: Capsule sync fails with Error: Katello ...
Error : Katello::Errors::Pulp3Error Parsing interrupted: The repository metadata being synced into Pulp is erroneous in a way that makes it ...
Read more >
error converting YAML to JSON: yaml: line 27: did not find ...
Error : error parsing mongodb-deployment.yaml: error converting YAML to JSON: ... app: mongodb template: metadata: labels: app: mongodb spec: containers: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found