You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My prysm instance stopped syncing randomly (using nethermind as EL -- this was always working fine) and revealed the error noted in title. After restarting prysm, the same error appears over and over again.
Has this worked before in a previous version?
This is new behavior and started when I upgraded to 5.0.3
🔬 Minimal Reproduction
I don't know exactly how to reproduce, but in my instance:
Prysm was confirmed working in the morning.
Prysm seemed to have crashed. I run my instance in a linux screen. I screen -r'd into the instance and saw there was no update in hours.
I restarted prysm and now it is syncing, but reads the same error over and over again.
Error
ERROR filesystem: Unable to prune directory directory=0x123 error=slot could not be read from blob file 0.ssz: EOF
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
5.0.3
Anything else relevant (validator index / public key)?
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
My prysm instance stopped syncing randomly (using nethermind as EL -- this was always working fine) and revealed the error noted in title. After restarting prysm, the same error appears over and over again.
Has this worked before in a previous version?
🔬 Minimal Reproduction
I don't know exactly how to reproduce, but in my instance:
Prysm was confirmed working in the morning.
Prysm seemed to have crashed. I run my instance in a linux screen. I screen -r'd into the instance and saw there was no update in hours.
I restarted prysm and now it is syncing, but reads the same error over and over again.
Error
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
5.0.3
Anything else relevant (validator index / public key)?
No response
The text was updated successfully, but these errors were encountered: