Alex Sharov
Alex Sharov
@quickchase it's end of error message. need start of message - there is reason of error and where it happened. try on latest devel plz.
At least it must write to logs rpc requests on higher levels. (If inject logger everywhere is the big task).
please add --metrics flag, start erigon wait when it gets to 100% point. then show us: `http://localhost:6060/debug/vars` then then wait 5 min and show us again: `http://localhost:6060/debug/vars`
@mikolajsobolewski does --torrent.port open for TCP and UDP?
“context canceled” - it means client canceled the request, or client gone.
1. it's safe to kill erigon at any time 2. " bunch of broken file handles. " - what was the error message? 3. Fixed "nil pointer" problem by: https://github.com/ledgerwatch/erigon/pull/5070
thank you. "error closing storage: FlushFileBuffers: The handle is invalid." is much more useful than "handle is invalid".
@AndreaLanfranchi `"v1-006000-006500-bodies.seg": error closing storage: FlushFileBuffers: The handle is invalid.` - does this file exists?
looks similar to https://github.com/edsrzf/mmap-go/issues/22 but we using [email protected] where this problem solved...
> I solved it but redownloading and installing. The problem is that --prune htrc (I don't recall the ultimate pruning version) stopped working and it worked when I replaced with...