Go-ethereum: Light mode down

Created on 5 Dec 2017  路  11Comments  路  Source: ethereum/go-ethereum

System information

Geth version: 1.7.3
OS & Version: Windows 7-x64
Commit hash : (if develop)
client-Wallet: Ethereum_Wallet-0.9.3

Expected behaviour

finding at least one peer to update my blockchain.

Actual behaviour

won`t find peers on light mode to sync blockchain at all.
this week,seems network is somehow down.
due this issue, i can't transfer.

Steps to reproduce the behaviour

Backtrace

[backtrace]

inactive

Most helpful comment

This is a social issue. People don't enable "lightserv" mode. Tough luck.

Are there any public analytics on how many up-to-date "lightserv" nodes are online right now? Do we know what number of percentage is a healthy amount?

If there are numbers, we can start a campaign to increase it into a healthy amount.

Now, if we were discussing the ramifications of enabling "lightserv" by default - that would be a different matter...

Is there an issue for this? (Should we open one?)

All 11 comments

so am i alone?

@nav1d You are not alone, I just tried running light mode from geth 1.6.6-stable, which had worked fine about a month ago, but doesn't appear to sync right now...

I guess I'll try updating geth first

1____library_application_support_ethereum_wallet_binaries_geth_unpacked__geth_

Might have something to do with the network being congested right now

yeah,i think ethereum network does not have enough potential to handle clients.
i'm wonder what should we do with this shit?! if continues, it can freeze network.

@nav1d This issue can not be solved with any code update. If people running "regular" go-ethereum nodes don't reserve any peer slots/time for "light" clients, then those will have nothing to connect to.

It _could_ perhaps be alleviated by implementing #15624, but that's a very niche case (and, anyway, requires the above).


@pepijnolivier Updating to a newer geth would help - v1.7.3 ideally, as it has LES v2 support.

Note also that specifying --syncmode light --maxpeers100 is exacerbating the issue. You're raising the default, and attempting to reserve more of this precious resource.


Recommend closing as "nothing to do" - unless it can be demonstrated that a "light" node is rejected my by a "lightserv" node that still has open peer slots.

"nothing to do" !?
bro, i know its about traffic and not about code. but according to my prev post, it should figured out to prevent this issue, because this is about its structure.
downloding 30gb(fast mode) or 300gb(full mode) blockchain is not a good idea, many micro-trans made by smartphones and tablets. which smartphone can save 300gb into itself??
if ethereum wants to be used globally, it should reduce blockchain size or add more light-node peers.

Yes, "nothing to do".

I'm in the same boat: my light clients are having trouble finding nodes to serve them. For that reason, I've started a dedicated public node, just to serve light clients (as mentioned in issue #15624, linked prior).

This is a _social_ issue. People don't enable "lightserv" mode. Tough luck.


Now, if we were discussing the ramifications of enabling "lightserv" by default - that would be a different matter...

This is a social issue. People don't enable "lightserv" mode. Tough luck.

Are there any public analytics on how many up-to-date "lightserv" nodes are online right now? Do we know what number of percentage is a healthy amount?

If there are numbers, we can start a campaign to increase it into a healthy amount.

Now, if we were discussing the ramifications of enabling "lightserv" by default - that would be a different matter...

Is there an issue for this? (Should we open one?)

@shazow Regarding a separate issue for lightserv!=0 by default - I haven't found one (although there are probably several already). I wouldn't recommend doing this myself - see https://github.com/ethereum/go-ethereum/issues/15624#issuecomment-352181753 and #15689.

EDIT: Actually, there's PR #15691 just for that.


(#15454 seems to be the issue with the most laconic and on-point title.)

IMO OK to close since v1.8.0 has been released.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings