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.

Possible MetaData Issue with Lighthouse

See original GitHub issue

I was looking through a recent Lighthouse peerstore dump from Altona and found 14 teku nodes in the peerstore. All 14 had a reputation of 0 & metadata = null. I’m wondering if there is a possible issue with the MetaData req/resp method. 🤷‍♂️

Here is an example of a teku entry:

  {
    "peer_id": "16Uiu2HAmRaVfypo834Kovh4mQErjTzigyAnri4618wpEke3bXftD",
    "peer_info": {
      "_status": "Healthy",
      "reputation": 0,
      "client": {
        "kind": "Teku",
        "version": "v0.12.0-dev-5380e888",
        "os_version": "linux-x86_64",
        "protocol_version": "ipfs/0.1.0",
        "agent_string": "teku/teku/v0.12.0-dev-5380e888/linux-x86_64/oracle_openjdk-java-11"
      },
      "connection_status": {
        "Connected": {
          "in": 0,
          "out": 1
        }
      },
      "listening_addresses": [
        "/ip4/xx.x.x.xxx/tcp/9000/p2p/16Uiu2HAmRaVfypo834Kovh4mQErjTzigyAnri4618wpEke3bXftD"
      ],
      "sync_status": {
        "Synced": {
          "info": {
            "status_head_slot": 65255,
            "status_head_root": "0xf9aa4c155d92640eae4ff6f9262625e9ccd092f328cb84284bc558a915f3ec1d",
            "status_finalized_epoch": 2013,
            "status_finalized_root": "0x7d5a7d2ee690fa2fd50cf0c18e4c28d674e5c33b2d184cbe36cec135219b6891"
          }
        }
      },
      "meta_data": null
    }
  }

For comparison, here is an example of a Prysm node:

 {
    "peer_id": "16Uiu2HAmLvREVVcPJGbpRmvEMxV8AJy1s8fn9LRPXVB9FBo9xYaW",
    "peer_info": {
      "_status": "Healthy",
      "reputation": 50,
      "client": {
        "kind": "Unknown",
        "version": "unknown",
        "os_version": "unknown",
        "protocol_version": "ipfs/0.1.0",
        "agent_string": "Prysm/v1.0.0-alpha.13/a9bbbae19abac0c3c8cf7c4213b949172f97cf57"
      },
      "connection_status": {
        "Connected": {
          "in": 0,
          "out": 1
        }
      },
      "listening_addresses": [
        "/ip4/xx.xxx..x.xx/tcp/13000"
      ],
      "sync_status": {
        "Synced": {
          "info": {
            "status_head_slot": 65254,
            "status_head_root": "0x69d4de78fc15e0e04763d66f826fe345b3cd703724d5e4e6bdf4cc0fef2275af",
            "status_finalized_epoch": 2013,
            "status_finalized_root": "0x7d5a7d2ee690fa2fd50cf0c18e4c28d674e5c33b2d184cbe36cec135219b6891"
          }
        }
      },
      "meta_data": {
        "seq_number": 1,
        "attnets": "0xbfafd576ffffb3d7"
      }
    }
  }

Here is a Nimbus node:

 {
    "peer_id": "16Uiu2HAmUZgER8SkBxfyf8RaH8As7AmU5ZgYqSmhmuvYTZbSjgdg",
    "peer_info": {
      "_status": "Healthy",
      "reputation": 50,
      "client": {
        "kind": "Nimbus",
        "version": "0.0.1",
        "os_version": "unknown",
        "protocol_version": "ipfs/0.1.0",
        "agent_string": "nim-libp2p/0.0.1"
      },
      "connection_status": {
        "Connected": {
          "in": 0,
          "out": 1
        }
      },
      "listening_addresses": [
        "/ip4/x.x.x.x/tcp/9000"
      ],
      "sync_status": {
        "Synced": {
          "info": {
            "status_head_slot": 65242,
            "status_head_root": "0xf10aaf360ba51620202fd1d9753cb1738f24102c84eaefb47ac2cea4ae8d1bb6",
            "status_finalized_epoch": 2013,
            "status_finalized_root": "0x7d5a7d2ee690fa2fd50cf0c18e4c28d674e5c33b2d184cbe36cec135219b6891"
          }
        }
      },
      "meta_data": {
        "seq_number": 0,
        "attnets": "0xffffffffffffffff"
      }
    }
  },

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
Nashatyrevcommented, Jul 14, 2020

Yep, we still experiencing the similar problem as was solved #2254

0reactions
Nashatyrevcommented, Jul 22, 2020

The issue fixed on the Lighthouse side https://github.com/sigp/lighthouse/pull/1369

Read more comments on GitHub >

github_iconTop Results From Across the Web

Add og:image metadata to lighthouse report HTML · Issue #9685
when sharing lighthouse-report urls in e.g slack/mattermost or similar it would be great to get a small preview of the lighthouse results.
Read more >
Lighthouse Variability | Tools for Web Developers
A guide on dealing with variance in Lighthouse results. ... Tier-1 network variability, Medium, POSSIBLE, POSSIBLE, POSSIBLE.
Read more >
Configuring SAML For Lighthouse - Opengear Help Desk
Identity Provider metadata is available if this application supports dynamic configuration. Open the link and save the page as an XML file ( ......
Read more >
How to Improve Website Lighthouse Scores | Gatsby
Instead, Lighthouse uses Total Blocking Time (TBT) as a metric to predict possible issues that could impact FID site ratings.
Read more >
Document does not have a meta description
# How the Lighthouse meta description audit fails​​ The audit fails if: Your page doesn't have a <meta name=description> element.
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