Content pfp
Content
@
https://ethstaker.cc
0 reply
0 recast
0 reaction

Louis πŸ‘΅ πŸ¦‡πŸ”Š pfp
Louis πŸ‘΅ πŸ¦‡πŸ”Š
@superlouis.eth
My worst fear happened last night. After 677 days since my last proposal, I got an opportunity, and my node missed it. Trying not to rage-quit the solo staking game, let's figure out what wen wrong: - No missing attestation, I usually get alerts when I miss attestation and go fix it. I wrongly assumed that healthy attestations meant healthy validator. - Nimbus version 24.12.0 (dappnode package 1.0.16, only 3 weeks late from the "medium-urgency" update) - No errors in the logs. Only a casual warning: "Block could not be sent from validator that is also managed by the beacon node" Looking into the log history, it turns out a similar warning appeared for attestations as well: "A validator client has attempted to send an attestation from validator that is also managed by the beacon node" I mean what the f* is this supposed to mean? Upgraded Nimbus to the latest version (no config change). Warnings are gone. See you in 2 years.
12 replies
26 recasts
137 reactions

Magg / Pine Cone pfp
Magg / Pine Cone
@magg
My condolences @superlouis.eth and @limes.eth ! Worst feeling! Have you considered converting to Rocketpool to get some more hand holding? I love that there's a bunch of other validators running the exact same setup as me, so that if they have a problem I will know about it right away You'd get better APY too, since you could run 4 validators per 32ETH, and if you join the smoothing pool you get an average of MEV instead of hoping for that single expensive block
1 reply
0 recast
3 reactions

Lefteris Karapetsas pfp
Lefteris Karapetsas
@lefteris.eth
This sounds like a bug. I have also had something happen and discovered a bug in the CL client I was using. Definitely contact the client team and share logs with them. This can definitely help improve the client and also provide clarity to you about what happened.
0 reply
0 recast
19 reactions

nixo pfp
nixo
@nixo
best place to ask is either the ethstaker discord or your consensus layer client discord! a lot of the more technical experts aren't super active here
0 reply
0 recast
3 reactions

xh3b4sd ↑ pfp
xh3b4sd ↑
@xh3b4sd.eth
The beauty of the network is that another solo staker may just has covered your miss at the time. Onwards!
0 reply
0 recast
3 reactions

Nachshol.eth pfp
Nachshol.eth
@thewatcher
I use rocketpool and have encountered during the past 2 years about 3 cases when troubleshooting was necessary. Every single time i managed to get help in RP discord and for the mist part, someone has already had the same issue before me so the fix twas already known. Deeply recommend giving it a go albeit joining should be timed with current queue status (if there is a long queue waiting for protocol eth then your validator will take long to activate)
0 reply
0 recast
1 reaction

Paul Dowman πŸ”΄βœ¨ pfp
Paul Dowman πŸ”΄βœ¨
@
That’s frustrating! If it’s any consolation, blocks aren’t worth much these days anyway. Especially this weekend. Most of the value is just in the regular drip of attestations 🫠
0 reply
0 recast
1 reaction

beebeehem pfp
beebeehem
@beebeehem
Almost two years of work, that's crazy. I think the primary issues was when you missed the attestation warning, could have been as a result of some unnoticeable errors, missed upgrade or a combination of those or other factors.
0 reply
0 recast
1 reaction

Daniel Fernandes pfp
Daniel Fernandes
@dfern.eth
Make sure you save the logs from both your CL & EL! I've had something similar happen before, but it took me 3 days to notice b/c I didn't have notifications on...
1 reply
0 recast
1 reaction

Peter🎩 pfp
Peter🎩
@silencedogood.eth
Just put it in t-bills mate
0 reply
0 recast
1 reaction

Borg pfp
Borg
@ruz.eth
https://media.tenor.com/9VHZcUvBslsAAAAC/noo-toy-story
0 reply
0 recast
1 reaction

limes pfp
limes
@limes.eth
I’ve missed two for having shoddy NUC specs. You’ll gettem next time!
0 reply
0 recast
1 reaction

barabazs pfp
barabazs
@barabazs.eth
ugh no! hope you find the cause
0 reply
0 recast
0 reaction