-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
RPC error: transport error: HTTP response too short: length 0, needed 12 #1377
Comments
Exactly every 5000 blocks, me as well.
|
It's due to the commit that happens in updater.rs Not sure exactly how rust works, but my guess would be the sync channel is blocked waiting for the |
It's indexing slower now and with more frequent errors. @casey 60000 blocks in 12 hours. Update: I killed the process and started again because it became deadly slow. |
It's very write-heavy - using an NVME will speed things up a lot |
used a ramdisk to do a ord index but it is similarily slow |
@hashbender it has nothing to do with disks, I am on SSD. I am confused why it is not the highest priority now because ord is not usable. I tried to roll back to different versions and with We know that there is a bug somewhere between Even though I got almost all blocks (10000 left) now it is stuck with any version.
|
is it safe for me to rollback to 0.4.0, index the chain, then upgrade back to 0.4.2? |
Yes, it is safe to try it out. |
rolling back didn't work, my |
This time, I was able to index all blocks with |
i feel like this should be the highest priority issue, seems like most people are unable to sync |
Any success? @dannydeezy @OrpingtonClose |
I was hitting this bug on 0.4.2. Mine was stuck several times, finally crashed at 772406. I essentially kept restarting with Perhaps a workaround for those experiencing this now is to run the indexing in a bash loop, on tmux or similar until it completes. |
You were lucky, I get 5 blocks per hour after block ~764000. |
More specifically this. @jbdatko |
Seems like as the sat ranges get more fragmented later in the sync the volume of writes per 5k block flush gets really high. ~10 minutes to index, ~5 minutes to flush on my machine at block height 635000-640000. Quick math tells me that it would take 45PiB or so to store a pointer from each individual sat to its TXO, so over time fragmenting of the sat space will become a real problem for ordinal sat tracking. |
Watching iostat during the flush shows a pattern of ~14 seconds of reading ~20MB/s, then ~2.5 seconds of writing ~300MB/s on my NVME SSD. |
Perhaps a variant of |
Is there a workaround for this issue? I saw some mentions of using older versions but wasn't clear if those work reliably. I'm on a beefy Mac M1, 32GB RAM, 1TB SSD. Syncing bitcoin node from genesis took < 8 hours. Indexing in |
Yes, fragmenting gets worse over time. At the moment you will need 64gb or more of RAM to have a chance at syncing the ord index with |
We we're thinking of doing exactly this. Building the database on-demand, but this would mean a complete redesign so we put that on hold. Maybe it's time to resurface that though. |
FYI @dude513 recommendation worked for me: |
I downgraded to version |
You can't use |
FWIW I too got by this by downgrading to 0.4.0. Sped right through indexing on 0.4.0 but was stalling on 0.4.2. |
I spoke too soon.. stuck at last 10k blocks |
Managed to index after switching to 0.4.0. Last few thousand blocks took the bulk of the time to index. |
https://github.com/casey/ord/pull/1516 will fix these errors since blocks will no longer be requested through RPC. |
Tried the above and still got the error several times. What I did to resolve the issue just in time to miss 100k was I typed |
getting this issue on ord 0.5.0 |
@donnlee I think this fixed the issue https://github.com/casey/ord/pull/1637 |
@andrewtoth , ok I will try branch |
I'm also having this issue and testing https://github.com/casey/ord/pull/1637 now |
@andrewtoth , I confirm that casey@50f2ad7 on ord 0.5.0 has fixed the issue of blocks re-indexing at 775000 |
I got here from google because I am seeing the same error message when I run |
@coconutpalms not sure it's a good idea to use a third party bitcoind. |
I'm concerned about downloading the blockchain because of US restrictions on illegal data, is there a way to run a node and inscribe ordinals without doing that? |
@coconutpalms if that's your concern I regret to inform you that |
I'm going to close this, since this seems stale. Please reopen if not. |
The text was updated successfully, but these errors were encountered: