Comments (6)
tzapu
commented on July 19, 2024
hi, logs are misleading, that’s how it looks when it works ok. you can try adding —v or —vv for a more verbose log.
check eth2stats.io and see if it updates there
… On 17 Jul 2020, at 22:11, Chase Wright ***@***.***> wrote:
My eth2stats for lighthouse don't seem to be updating
time="2020-07-17T19:04:56Z" level=info msg="Could not load config file. Falling back to args. Error: Config File \"config\" Not Found in \"[/]\"" module=main
time="2020-07-17T19:04:56Z" level=info msg="[core] setting up eth2stats server connection"
time="2020-07-17T19:04:56Z" level=info msg="[core] getting beacon client version"
time="2020-07-17T19:04:56Z" level=info msg="[core] got beacon client version" version=Lighthouse/v0.1.2-unstable/x86_64-linux
time="2020-07-17T19:04:56Z" level=info msg="[core] getting beacon client genesis time"
time="2020-07-17T19:04:56Z" level=info msg="[core] beacon client genesis time" genesisTime=1593433805
time="2020-07-17T19:04:56Z" level=info msg="[core] awaiting connection to eth2stats server"
time="2020-07-17T19:05:03Z" level=info msg="[core] getting chain head for initial feed"
time="2020-07-17T19:05:03Z" level=info msg="[core] got chain head" headSlot=131574
time="2020-07-17T19:05:03Z" level=info msg="[core] successfully connected to eth2stats server"
time="2020-07-17T19:05:03Z" level=info msg="[core] setting up chain heads subscription"
time="2020-07-17T19:05:03Z" level=info msg="[polling] polling for new heads"
That's all it does, no other logs, at all. But my Beacon-Node is running fine.
If I stop the docker and re-start it, it updates the headSlot to the latest headSlot, then sits there again.
I appear to be on the latest commit d1c9215
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#43>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWYLEAN5IREFGKIUVT7HRTR4CO7DANCNFSM4O6XXHRQ>.
from eth2stats-client.
MysticRyuujin
commented on July 19, 2024
It not updating there was what caused me to go look at it in the first place...
I can't tell why but my lighthouse client is always way behind...
I'll keep watching I guess? Maybe it is updating slow? idk
from eth2stats-client.
MysticRyuujin
commented on July 19, 2024
Adding --v or --vv didn't change the output significantly...
time="2020-07-17T20:58:53Z" level=info msg="Could not load config file. Falling back to args. Error: Config File \"config\" Not Found in \"[/]\"" module=main
time="2020-07-17T20:58:53Z" level=debug msg="[main] Debug mode"
time="2020-07-17T20:58:53Z" level=info msg="[core] setting up eth2stats server connection"
time="2020-07-17T20:58:53Z" level=debug msg="[core] looking for existing token"
time="2020-07-17T20:58:53Z" level=debug msg="[core] found token"
time="2020-07-17T20:58:53Z" level=info msg="[core] getting beacon client version"
time="2020-07-17T20:58:53Z" level=info msg="[core] got beacon client version" version=Lighthouse/v0.1.2-unstable/x86_64-linux
time="2020-07-17T20:58:53Z" level=info msg="[core] getting beacon client genesis time"
time="2020-07-17T20:58:53Z" level=info msg="[core] beacon client genesis time" genesisTime=1593433805
time="2020-07-17T20:58:53Z" level=info msg="[core] awaiting connection to eth2stats server"
time="2020-07-17T20:58:53Z" level=info msg="[core] getting chain head for initial feed"
time="2020-07-17T20:58:53Z" level=info msg="[core] got chain head" headSlot=132138
time="2020-07-17T20:58:53Z" level=info msg="[core] successfully connected to eth2stats server"
time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] sending telemetry"
time="2020-07-17T20:58:53Z" level=info msg="[core] setting up chain heads subscription"
time="2020-07-17T20:58:53Z" level=info msg="[polling] polling for new heads"
time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] peers: 38"
time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] done sending telemetry"
time="2020-07-17T20:59:05Z" level=trace msg="[core] sending heartbeat"
time="2020-07-17T20:59:05Z" level=trace msg="[core] done sending heartbeat"
time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] sending telemetry"
time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] peers: 39"
time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] done sending telemetry"
time="2020-07-17T20:59:17Z" level=trace msg="[core] sending heartbeat"
time="2020-07-17T20:59:17Z" level=trace msg="[core] done sending heartbeat"
time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] sending telemetry"
time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] peers: 41"
time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] done sending telemetry"
from eth2stats-client.
tzapu
commented on July 19, 2024
it looks like for whatever reason polling the rest endpoint for new heads does not change
do the lighthouse logs show advancing slots/block/head?
… On 18 Jul 2020, at 00:00, Chase Wright ***@***.***> wrote:
Adding --v or --vv didn't change the output significantly...
time="2020-07-17T20:58:53Z" level=info msg="Could not load config file. Falling back to args. Error: Config File \"config\" Not Found in \"[/]\"" module=main
time="2020-07-17T20:58:53Z" level=debug msg="[main] Debug mode"
time="2020-07-17T20:58:53Z" level=info msg="[core] setting up eth2stats server connection"
time="2020-07-17T20:58:53Z" level=debug msg="[core] looking for existing token"
time="2020-07-17T20:58:53Z" level=debug msg="[core] found token"
time="2020-07-17T20:58:53Z" level=info msg="[core] getting beacon client version"
time="2020-07-17T20:58:53Z" level=info msg="[core] got beacon client version" version=Lighthouse/v0.1.2-unstable/x86_64-linux
time="2020-07-17T20:58:53Z" level=info msg="[core] getting beacon client genesis time"
time="2020-07-17T20:58:53Z" level=info msg="[core] beacon client genesis time" genesisTime=1593433805
time="2020-07-17T20:58:53Z" level=info msg="[core] awaiting connection to eth2stats server"
time="2020-07-17T20:58:53Z" level=info msg="[core] getting chain head for initial feed"
time="2020-07-17T20:58:53Z" level=info msg="[core] got chain head" headSlot=132138
time="2020-07-17T20:58:53Z" level=info msg="[core] successfully connected to eth2stats server"
time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] sending telemetry"
time="2020-07-17T20:58:53Z" level=info msg="[core] setting up chain heads subscription"
time="2020-07-17T20:58:53Z" level=info msg="[polling] polling for new heads"
time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] peers: 38"
time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] done sending telemetry"
time="2020-07-17T20:59:05Z" level=trace msg="[core] sending heartbeat"
time="2020-07-17T20:59:05Z" level=trace msg="[core] done sending heartbeat"
time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] sending telemetry"
time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] peers: 39"
time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] done sending telemetry"
time="2020-07-17T20:59:17Z" level=trace msg="[core] sending heartbeat"
time="2020-07-17T20:59:17Z" level=trace msg="[core] done sending heartbeat"
time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] sending telemetry"
time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] peers: 41"
time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] done sending telemetry"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWYLECVYHDYAYPD5EZNLN3R4C3XNANCNFSM4O6XXHRQ>.
from eth2stats-client.
tzapu
commented on July 19, 2024
ii ve just seen yours jump to 132161 but not sure if it was because you restarted it or it worked
… On 18 Jul 2020, at 00:03, Alex T ***@***.***> wrote:
it looks like for whatever reason polling the rest endpoint for new heads does not change
do the lighthouse logs show advancing slots/block/head?
> On 18 Jul 2020, at 00:00, Chase Wright ***@***.*** ***@***.***>> wrote:
>
>
> Adding --v or --vv didn't change the output significantly...
>
> time="2020-07-17T20:58:53Z" level=info msg="Could not load config file. Falling back to args. Error: Config File \"config\" Not Found in \"[/]\"" module=main
> time="2020-07-17T20:58:53Z" level=debug msg="[main] Debug mode"
> time="2020-07-17T20:58:53Z" level=info msg="[core] setting up eth2stats server connection"
> time="2020-07-17T20:58:53Z" level=debug msg="[core] looking for existing token"
> time="2020-07-17T20:58:53Z" level=debug msg="[core] found token"
> time="2020-07-17T20:58:53Z" level=info msg="[core] getting beacon client version"
> time="2020-07-17T20:58:53Z" level=info msg="[core] got beacon client version" version=Lighthouse/v0.1.2-unstable/x86_64-linux
> time="2020-07-17T20:58:53Z" level=info msg="[core] getting beacon client genesis time"
> time="2020-07-17T20:58:53Z" level=info msg="[core] beacon client genesis time" genesisTime=1593433805
> time="2020-07-17T20:58:53Z" level=info msg="[core] awaiting connection to eth2stats server"
> time="2020-07-17T20:58:53Z" level=info msg="[core] getting chain head for initial feed"
> time="2020-07-17T20:58:53Z" level=info msg="[core] got chain head" headSlot=132138
> time="2020-07-17T20:58:53Z" level=info msg="[core] successfully connected to eth2stats server"
> time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] sending telemetry"
> time="2020-07-17T20:58:53Z" level=info msg="[core] setting up chain heads subscription"
> time="2020-07-17T20:58:53Z" level=info msg="[polling] polling for new heads"
> time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] peers: 38"
> time="2020-07-17T20:58:53Z" level=trace msg="[telemetry] done sending telemetry"
> time="2020-07-17T20:59:05Z" level=trace msg="[core] sending heartbeat"
> time="2020-07-17T20:59:05Z" level=trace msg="[core] done sending heartbeat"
> time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] sending telemetry"
> time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] peers: 39"
> time="2020-07-17T20:59:05Z" level=trace msg="[telemetry] done sending telemetry"
> time="2020-07-17T20:59:17Z" level=trace msg="[core] sending heartbeat"
> time="2020-07-17T20:59:17Z" level=trace msg="[core] done sending heartbeat"
> time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] sending telemetry"
> time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] peers: 41"
> time="2020-07-17T20:59:17Z" level=trace msg="[telemetry] done sending telemetry"
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWYLECVYHDYAYPD5EZNLN3R4C3XNANCNFSM4O6XXHRQ>.
>
from eth2stats-client.
MysticRyuujin
commented on July 19, 2024
I'm not sure what is/was happening, so I wiped my lighthouse BN and started fresh. I see eth2stats keeping track with the sync state, so I'm guessing it was something to do with the BN.
from eth2stats-client.
Related Issues (20)
- client fails to launch with certain chars in name
- eth2stats adds a new gRPC connection to the prysm node every 12 seconds until the OS runs out of file handlers HOT 3
- Nodes are not visible in Global Map screen HOT 1
- 404 error code with Medalla
- Prysm gets more verbose logs than other clients
- fatal error: invalid node URL: "beacon:4000" HOT 1
- Can't pull peer count HOT 2
- teku metrics polling fails to parse HOT 1
- Favorited node resets to unfavorited after X minutes HOT 2
- System Slot feature HOT 1
- Support for spadina HOT 1
- Support for Lighthouse v0.3.0+ HOT 2
- Lighthouse v0.3.0 Breaks Beacon Metrics HOT 1
- Eth2Stats client using 1.5GB memory HOT 4
- Take into account peer state for standard API HOT 2
- failed to poll metrics: parse \"http://beacon-chain-prod-4:9090/metrics\": first path segment in URL cannot contain colon HOT 2
- Nimbus - could not find `process_resident_memory_bytes` in metrics HOT 5
- Pyrmont testnet HOT 1
- Let's Encrypt Certificate for https://eth2stats.io Expired
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eth2stats-client.