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

grafana: no data on Ubuntu after #8517 #8603

Closed
1 task done
allnil opened this issue Jun 4, 2024 · 3 comments
Closed
1 task done

grafana: no data on Ubuntu after #8517 #8603

allnil opened this issue Jun 4, 2024 · 3 comments
Labels
A-observability Related to tracing, metrics, logs and other observability tools C-bug An unexpected or incorrect behavior

Comments

@allnil
Copy link
Contributor

allnil commented Jun 4, 2024

Describe the bug

Grafana can't see the reth instance and shows NO DATA on dashboards using the latest reth image on Ubuntu 22.04 LTS
I identified that the issue first time occured in this PR commit #8517
I build e89e4c9 and previous commit 80809a4 locally to compare them and used docker-compose from etc/ folder

docker compose -f etc/docker-compose.yml -f etc/lighthouse.yml up -d

The node itself is working and the state is growing
Screenshot 2024-06-04 at 15 15 55
Screenshot 2024-06-04 at 15 49 08

Steps to reproduce

  1. docker compose -f etc/docker-compose.yml -f etc/lighthouse.yml up -d
    with latest image on ubuntu
  2. go to the grafana dashboard

Node logs

No response

Platform(s)

Linux (x86)

What version/commit are you on?

latest

What database version are you on?

latest

Which chain / network are you on?

mainnet

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

docker build . -t reth:local

Code of Conduct

  • I agree to follow the Code of Conduct
@allnil allnil added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Jun 4, 2024
@onbjerg
Copy link
Member

onbjerg commented Jun 10, 2024

hey! is this still the case on beta.9?

@mattsse
Copy link
Collaborator

mattsse commented Jun 11, 2024

pretty sure we fixed this via #8593

closing optimistically, please ping if this is still an issue

@mattsse mattsse closed this as completed Jun 11, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Jun 11, 2024
@mattsse mattsse added A-observability Related to tracing, metrics, logs and other observability tools and removed S-needs-triage This issue needs to be labelled labels Jun 11, 2024
@allnil
Copy link
Contributor Author

allnil commented Jun 11, 2024

it works
checked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-observability Related to tracing, metrics, logs and other observability tools C-bug An unexpected or incorrect behavior
Projects
Archived in project
Development

No branches or pull requests

3 participants