Skip to content
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

LES client panics after syncing is done #24611

Closed
s1na opened this issue Mar 30, 2022 · 1 comment · Fixed by #24641
Closed

LES client panics after syncing is done #24611

s1na opened this issue Mar 30, 2022 · 1 comment · Fixed by #24641
Assignees
Labels

Comments

@s1na
Copy link
Contributor

s1na commented Mar 30, 2022

System information

Geth version: Version: 1.10.18-unstable Git Commit: 25bd17d725db5378b3611ac077506dc09e940a77
OS & Version: OSX

What happened

Immediately after the light client finished syncing from a local light server it crashed.

DEBUG[03-30|09:21:27.166] Fetching batch of headers                id=0eaf38fb12f42c09 conn=dyndial count=192  fromnum=6,623,214 skip=0   reverse=false
TRACE[03-30|09:21:27.167] Light Ethereum message arrived           id=0eaf38fb12f42c09 conn=dyndial code=3  bytes=16
TRACE[03-30|09:21:27.167] Received block header response message   id=0eaf38fb12f42c09 conn=dyndial
INFO [03-30|09:21:27.167] Imported new block headers               count=2    elapsed=1.633ms   number=6,623,213 hash=9cd49a..f77956 age=13h22m31s
DEBUG[03-30|09:21:27.168] Synchronise finished                     elapsed=2m22.876s
INFO [03-30|09:21:27.558] Storing bloom trie                       section=201 head=d764fc53973d2d80887b70196ab2bbd1ee802878a347bcacd3ea881424ccb4fd root=041dfbb3335d21f8d9d2dd8d58b2e45f469eab888b2575879074bc46069e1690 compression=0.460
INFO [03-30|09:21:28.264] Storing CHT                              section=201 head=d764fc53973d2d80887b70196ab2bbd1ee802878a347bcacd3ea881424ccb4fd root=06a4b2487785d1914b65dae0e4f8284570798a19f74f717c0432f5822862c15c


panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x1c0 pc=0x486e884]
                                                                                                                                                                                                                          goroutine 205 [running]:
github.com/ethereum/go-ethereum/les.(*lightFetcher).mainloop(0xc0003aedc0)
        github.com/ethereum/go-ethereum/les/fetcher.go:445 +0x21a4
created by github.com/ethereum/go-ethereum/les.(*lightFetcher).start
        github.com/ethereum/go-ethereum/les/fetcher.go:198 +0x87
@s1na s1na added the type:bug label Mar 30, 2022
@rjl493456442 rjl493456442 self-assigned this Mar 30, 2022
@s1na
Copy link
Contributor Author

s1na commented Mar 31, 2022

The commands I used were. For server:

make geth && ./build/bin/geth --goerli --maxpeers 3 --nodiscover --light.serve 25 --light.maxpeers 2 --light.nosyncserve

For client:

make geth && ./build/bin/geth --goerli --http --http.port 10545 --http.api 'eth,debug' --maxpeers 1 --nodiscover --syncmode 'light' --port 20202 --ulc.servers 'enode://...' --datadir ../goerli-light

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants