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.

Sign up for GitHub

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

Jump to bottom

Sync stalls on phase0 blocks with LH v2.2.0 #3147

Closed
jdevcs opened this issue Apr 7, 2022 · 2 comments
Closed

Sync stalls on phase0 blocks with LH v2.2.0 #3147

jdevcs opened this issue Apr 7, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@jdevcs
Copy link

jdevcs commented Apr 7, 2022

Description

Beacon node is unable to sync and start_slot is always 0

Version

using docker image: latest or v2.2.0

Present Behavior

curl --location --request GET 'http://localhost:5052/lighthouse/syncing'

its always responding

{
    "data": "Stalled"
}

and is at start_slot 0

{
    "data": {
        "SyncingFinalized": {
            "start_slot": "0",
            "target_slot": "3543488"
        }
    }
}

Expected Behaviour

start_slot should increase

Steps to resolve

For simple reproducing:
docker run -p 9000:9000 -p 127.0.0.1:5052:5052 -v ${HOME}/.lighthouse:/root/.lighthouse1 sigp/lighthouse lighthouse --network mainnet beacon --http --http-address 0.0.0.0
@pawanjay176
Copy link
Member

Thanks for the issue. We are testing a fix with this PR #3146

If you are syncing fresh, then I recommend downgrading to v2.1.5

@jdevcs jdevcs mentioned this issue Apr 7, 2022
Closed
@michaelsproul michaelsproul changed the title sync problem start_slot is always 0 Sync stalls on phase0 blocks with LH v2.2.0 Apr 7, 2022
@michaelsproul michaelsproul added the bug Something isn't working label Apr 7, 2022
@michaelsproul michaelsproul pinned this issue Apr 7, 2022
@michaelsproul michaelsproul mentioned this issue Apr 8, 2022
Closed
@jdevcs jdevcs mentioned this issue Apr 11, 2022
Closed
bors bot pushed a commit that referenced this issue Apr 12, 2022
@michaelsproul @paulhauner
v2.2.1 (#3149)
fa896bb 
## Issue Addressed

Addresses sync stalls on v2.2.0 (i.e. #3147).

## Additional Info

I've avoided doing a full `cargo update` because I noticed there's a new patch version of libp2p and thought it could do with some more testing.



Co-authored-by: Paul Hauner <[email protected]>
bors bot pushed a commit that referenced this issue Apr 12, 2022
@michaelsproul @paulhauner
v2.2.1 (#3149)
aa72088 
## Issue Addressed

Addresses sync stalls on v2.2.0 (i.e. #3147).

## Additional Info

I've avoided doing a full `cargo update` because I noticed there's a new patch version of libp2p and thought it could do with some more testing.



Co-authored-by: Paul Hauner <[email protected]>
@michaelsproul
Copy link
Member

Closing as this is fixed in v2.2.1, but I'll leave this pinned a bit longer

paulhauner added a commit to paulhauner/lighthouse that referenced this issue May 6, 2022
@michaelsproul @paulhauner
v2.2.1 (sigp#3149)
7dc43d3 
## Issue Addressed

Addresses sync stalls on v2.2.0 (i.e. sigp#3147).

## Additional Info

I've avoided doing a full `cargo update` because I noticed there's a new patch version of libp2p and thought it could do with some more testing.



Co-authored-by: Paul Hauner <[email protected]>
@michaelsproul michaelsproul unpinned this issue May 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@michaelsproul @pawanjay176 @jdevcs