-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
panic: deletion not supported #475
Comments
After this crash, bash console freezes. |
More clarifications: Expected behaviour Actual behaviour Steps to reproduce the behaviour Backtrace
|
System information: Expected behaviour: Actual behaviour: Steps to reproduce the behaviour:
Logs doesn't show what was an actual problem:
**UPD: **
|
Same here, but version 1.1.3 - any ideas? |
My node crashed 3 times, and after that while starting i always recieved something like: Detected unclear exit. |
I'm running into the same panic after syncing from scratch with snap mode
|
Seems to be related to syncing using snap mode, don't get this with the default method but got when using snap |
facing same issue - any tips? |
I switched to other physical nvme, and it worked without problem. The first nvme drive itself was fine though. No idea, what geth did not like about it. |
Same issue. Looks like it can be fixed by increasing the soft/hard limit of open files from 1024 to 65535. Edit, looks like it isnt completely gone but significantly reduced. |
any status update on the bug. prune-state exit with message
is a version 1.1.6 fix this bug? |
when can it be fixed? can't sync |
Fixed by #667, please wait for next release. |
Started fresh full node with snap sync
geth --syncmode=snap --config ./config.toml --datadir node --cache 18000 --rpc --http.port 9545 --http.corsdomain "*" --http.api "eth,web3,personal,net,txpool" --ws --ws.port 8546 --ws.origins "*" \ --ws.api "eth,web3,personal,net,txpool" --rpc.allow-unprotected-txs --txlookuplimit 0 console
After around an hour it crashes
Tried several times to do fresh sync.
Impossible to sync full node.
Any workaround?
Thanks
The text was updated successfully, but these errors were encountered: