fresh v0.10.0.0 node won't sync past block one, prints stacktrace #400

log file https://paste.debian.net/1203664/

running on Ubuntu 20.04

Error disappears if I set --block-sync-size to the default 100, or remove it altogether, but setting it to even 101 causes the above errors.

hi @lyza

try deleting old directory and resyncing with this ./wownerod --data-dir=/home/wownero/bitwownero --add-peer=global.wownodes.com:34568 --add-peer=very.wow.such.money:34568 --add-peer=wownero.fyi:34568. It will take a few minutes to find other peers the first time running wownerod. If it still does not connect, check your firewall, ports 34568 and 34567 should be open.

For --block-sync-size, the default is 20 blocks for newer blocks and 100 blocks for older blocks. Bigger batch size is more resource intensive, so it depends on your system's CPU/RAM. It would be best to not inlcude this flag unless there is a specific reason to do so.

Right, I did know it was 20 on newer blocks, but I'm syncing from block 1 which is why I mentioned the default as 100. And I know it uses increased resources, which is why I tried it with block-sync-size 101, just 1% more than it should have been doing anyway. The system is a 6 core machine with 40 GB of RAM so I don't think it's a resource issue.

But yeah, works perfectly without that option.