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

ETH Ropsten: websocket: read limit exceeded. Retrying... #490

Closed
matyushkins opened this issue Sep 10, 2020 · 16 comments
Closed

ETH Ropsten: websocket: read limit exceeded. Retrying... #490

matyushkins opened this issue Sep 10, 2020 · 16 comments

Comments

@matyushkins
Copy link
Contributor

HI.
Eth Ropsten
Geth/v1.9.20-stable-979fc968/linux-amd64/go1.15
Blockbook Sync from 0

Falls more than once on this error:

E0910 06:52:15.205891 6 sync.go:302] getBlockWorker 3 connect block error hash 0xd092253c94e5f24426fff2c9a203ec921b2df0d188d0f7ffb654be0dbec15ddd, height 599275: websocket: read limit exceeded. Retrying... E0910 06:52:15.205887 6 sync.go:302] getBlockWorker 2 connect block error hash 0xc02b5459997699df8b7a2bc45db78d784b1938b360ac3bc9f92764ee290e4ea5, height 599281: websocket: read limit exceeded. Retrying...

@martinboehm
Copy link
Contributor

Hi. We have not seen this behavior. Does it recover from it or do you have to restart the server?

@matyushkins
Copy link
Contributor Author

Hey. On our testnet, this has been observed more than once when synchronizing from scratch. Those. the node is synchronized from scratch and the blockbook is also synchronized from scratch. Restart did not help. deleting the data didn't help either.

@aman-rac
Copy link

@martinboehm , any updates? I am facing the same issue.

@csiocompany
Copy link

csiocompany commented Oct 30, 2020 •
edited
Loading

@matyushkins @martinboehm @aman-rac

Version from 1 Sep woks fine. Something has changed...

@aman-rac
Copy link

@csiocompany , you built using the master after this commit?

@csiocompany
Copy link

csiocompany commented Oct 30, 2020 •
edited
Loading

@aman-rac I do not know exactly. I only see the package date I was build is 1 september.

Upd.
Here is the version in web interface:

Blockbook
Version / Commit / Build | 0.3.4 / bea6b62-dirty / 2020-09-01T11:57:57+00:00

Backend
Version | Geth/v1.9.20-stable-979fc968/linux-amd64/go1.15

@martinboehm
Copy link
Contributor

martinboehm commented Oct 31, 2020 •
edited
Loading

Do I understand it correctly that the September 1st version built from master works fine and later builds from master do not work?

The only significant change since September 1st is this a199317 commit, which bumps go-ethereum dependecy to v1.9.20 (from v1.8.20).

@aman-rac @csiocompany Could you please check the behaviouor either rolling back the dependency to v1.8.20 or more preferably upgrading to the latest go-ethereum, currently v1.9.23 and then let us know of the result?

martinboehm added a commit that referenced this issue Nov 25, 2020
@martinboehm
Fix ETH Ropsten: websocket: read limit exceeded #490
08afda9 
Geth sets maxRequestContentLength to 5M.
However, Ropsten contains blocks of largers size (for example 599281).
These which cannot be fetched using API.

Fixed by hacky way of modifying the geth source before
the build of the project.
Will submit PR to go-ethereum with final fix.
martinboehm added a commit that referenced this issue Dec 4, 2020
@martinboehm
Fix ETH Ropsten: websocket: read limit exceeded #490
69d13e0 
Geth sets maxRequestContentLength to 5M.
However, Ropsten contains blocks of largers size (for example 599281).
These which cannot be fetched using API.

Fixed by hacky way of modifying the geth source before
the build of the project.
Will submit PR to go-ethereum with final fix.
sidhujag pushed a commit to syscoin/blockbook that referenced this issue Dec 23, 2020
@martinboehm
Fix ETH Ropsten: websocket: read limit exceeded trezor#490
0ec9c7a 
Geth sets maxRequestContentLength to 5M.
However, Ropsten contains blocks of largers size (for example 599281).
These which cannot be fetched using API.

Fixed by hacky way of modifying the geth source before
the build of the project.
Will submit PR to go-ethereum with final fix.
@matyushkins
Copy link
Contributor Author

It work in last master on 26.12.2020

@martinboehm martinboehm mentioned this issue Jan 27, 2021
Closed
@aman-rac
Copy link

@martinboehm , same issue on ropsten height 599275: websocket: read limit exceeded.

Blockbook - 0.3.4 (Built from this commit)
Geth - 1.10.1

@martinboehm
Copy link
Contributor

Fixed by 0bf1d17

@7-of-9
Copy link

7-of-9 commented May 27, 2021 •
edited
Loading

@martinboehm Same issue, using Geth/v1.10.3-stable-991384a7/linux-amd64/go1.16.3 and BB frontend 0.3.4 / cf66ce9 / 2021-05-17T06:27:32+00:00....

Just two blocks, specifically:

E0527 04:40:57.611810 21562 sync.go:335] getBlockWorker 2 connect block error hash 0xc02b5459997699df8b7a2bc45db78d784b1938b360ac3bc9f92764ee290e4ea5, height 599281: websocket: read limit exceeded. Retrying...
E0527 04:40:58.177114 21562 sync.go:335] getBlockWorker 1 connect block error hash 0xd092253c94e5f24426fff2c9a203ec921b2df0d188d0f7ffb654be0dbec15ddd, height 599275: websocket: read limit exceeded. Retrying...

@martinboehm
Copy link
Contributor

@7-of-9 Hi, the commit cf66ce9 is not in our repository. Please make sure that the version of Blockbook you run includes the commit 0bf1d17.

@7-of-9
Copy link

7-of-9 commented May 27, 2021 •
edited
Loading

Thanks @martin-key sry yes, cf66ce9 is a commit on my fork. It bumps geth to 1.10.3 (from 1.10.2 in your commit 0bf1d17).
I'd assumed that 1.10.3 would be fine, as the geth fix came in the previous version.
I'm going to try geth 1.10.2 per your commit, but fear it will fail on these same two blocks.

@martin-key
Copy link
Contributor

I believe that comment was for @martinboehm

@martinboehm
Copy link
Contributor

@7-of-9 Hi, I just tested it again in our development server
image
and it worked fine, as you can see in the log:

I0528 13:45:36.006528   69934 sync.go:384] connecting block 598000 0x9e2ed3a21ed8c91dd415382b3dbd77f73a0295d7e27745cd16bcbd65cb6a0d52, elapsed 14.23086127s {txAddressesHit:0 txAddressesMiss:0 balancesHit:25229 balancesMiss:143}
I0528 13:45:54.340843   69934 sync.go:384] connecting block 599000 0x1b425647a48ef36f6fb9e21bb81ab8d1dd44f0679d4b5926574040aee1b55d91, elapsed 18.333740149s {txAddressesHit:0 txAddressesMiss:0 balancesHit:154118 balancesMiss:3825}
I0528 13:46:25.402140   69934 sync.go:384] connecting block 600000 0x608806544f4f47731503751a6397039690cd63609137b25bf708235ecf6946b0, elapsed 31.060341425s {txAddressesHit:0 txAddressesMiss:0 balancesHit:175921 balancesMiss:4363}
I0528 13:46:38.173845   69934 sync.go:384] connecting block 601000 0xdc994cb100771bcf2bf857f289d3a39e71057223ae7f2bb35d122bf8f1729b6b, elapsed 12.771299817s {txAddressesHit:0 txAddressesMiss:0 balancesHit:0 balancesMiss:0}
I0528 13:46:51.039468   69934 sync.go:384] connecting block 602000 0x3b8b68bec5d4b352acc29fceeebf531ab2c4390d985e557e217493f0d7dfb950, elapsed 12.865192113s {txAddressesHit:0 txAddressesMiss:0 balancesHit:0 balancesMiss:0}

@7-of-9
Copy link

7-of-9 commented May 30, 2021

Thanks @martinboehm - confirmed, I sync'd from your master branch ok. Must be something bad on my fork.

bidoudan pushed a commit to stibits-inc/blockbook that referenced this issue Jul 4, 2022
@martinboehm
Fix ETH Ropsten: websocket: read limit exceeded trezor#490
e688818 
Geth sets maxRequestContentLength to 5M.
However, Ropsten contains blocks of largers size (for example 599281).
These which cannot be fetched using API.

Fixed by hacky way of modifying the geth source before
the build of the project.
Will submit PR to go-ethereum with final fix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@7-of-9 @martin-key @martinboehm @matyushkins @csiocompany @aman-rac