utreexod keeps going in a loop in blocks from the year 2015 (Mainnet) #187
Comments
|
(UPDATE) I deleted everything in
I started it back up from scratch using
Now it's stuck in a loop again with these errors.
|
|
Hey thanks for testing utreexod out. Would it be possible for you post the full logs since the beginning? Also, it'd be helpful if you posted your full config file here as well. The first comment you have where you posted the logs only starts out on the restart. It would help me debug what's actually going on. My initial guess is that the binary is writing not to the external disk but to the internal disk and that internal disk is not big enough. `--datadir="path/to/dir" is how you tell the binary to write somewhere else and since I don't see that when you ran it, that's my initial guess. |
|
Sorry, I deleted the logs from the first time, but I have attached all the logs from since I retried from scratch, seems to be running into the same error, just in the 2012 blocks instead of the 2015 blocks. Here is my current storage space info.
utreexod.log.10.gz |
|
@kcalvinalvin UPDATE I think it might be my fault. I suspect the external USB SSD I was using was old and faulty. |
|
So after resyncing from scratch on a new SSD, everything was running fine until I closed it. Even though everything was shutdown gracefully, minutes later I tried to resume syncing and it started running into the same "Adding orphan block" error. I am syncing from another local umbrel full node of mine to speed syncing up. See log attached (had to rename it .txt because .log files are not allowed) |
|
Hey! Thanks for trying it out again. Could you share me the flags for the conf file you had for the last log file? I do think it might be a bug and it'd help be reproduce if I had the flags used there |
|
Sure thing, the only flags I had for this conf are the following. The last conf did not have "connect=192.168.1.46:8333" datadir=/media/usb-drive/.utreexod/data |
|
Update: Bought a used server on ebay. (40 cores, 256GB of RAM, enterprise SSD, running promox) I have shutdown and started utreexod about 5 times so far and it is still syncing without error (so far). I'll let you know what happens. |
|
Hey. Just wondering if you had any luck this time around |
|
About 2 weeks ago, I had a power outage while syncing, and it gave the same "Adding orphan block " error loop. Had to start all over again, It's been running non-stop for 2 weeks now. I'll let you know when it finishes, probably another 2 weeks at this rate. : ) |
Hmm that shouldn't be happening. I have a system with 96GB of RAM and was able to sync in less than a day without running out of memory. I could help out and see what's going on if you could share your config. |
|
I am running ./utreexod --flatutreexoproofindex --prune=0 Attached is the config. |
|
My server ran out of disk space and I had to do an unclean reboot to expand the disk space. (attached logs) |
|
@HalFinneyIsMyHomeBoy I'm getting the same problems with syncing a bridge node. Slows to a crawl at about block 500k. (my system has 16G RAM) I've been discussing this on Calvin's discord, if you want to join in. Here in the utreexod channel You might go faster if you set the max cache sizes to -1, since you have 108G ram, as described in the discord. With only 16G, I get OOM errors. |
Running a full bitcoin core node.
Been running utreexod for a few days, but it looks like it keeps looping over the same blocks from the year 2015 with the log saying. "Adding orphan block"
Running with the following command, using external SSD for utreexod.
See part of the log attached.
utreexod.log
The text was updated successfully, but these errors were encountered: