Quote from: gjhiggins on Today at 05:17:20 PM

Quote from: psycodad on Today at 04:39:11 PM

I thought restarting the node would be a good idea as the debug.log was getting a little large (not so sure anymore if it really was a smart thing to do).
Now from debug.log it looks like a lot of blocks are getting orphaned (but I am not clear if these are blocks I have that are getting orphaned or if some other nodes tries to send me these blocks and my nodes doesn't accept them):

I had the same experience working off my old chaindump from a couple of days ago when trying to cross-sync my servers - loadsa orphans being processed.

So I started again, with same dump but this time connecting to 185.150.190.19. The first thing my node did was re-org away a pile of blocks and after that it was just a matter of syncing up to the latest block (as far as 185.150.190.19 sees it). I suspect my node was previously on a fork and as there were so many orphaned blocks, there was a good chance that 185.150.190.19 had a cleaner chain - which it seems to have had.

I have a parallel node on the main server that is currently syncing from 0, in due course that will give me a chaindump that is definitely orphan-free. I'll make a zipfile available when it's done.

In the meantime, here's the most recent chaindump zipfile, the result of the re-syncing to 185.150.190.19 as described above.

Latest node as far as my two listening servers are concerned is 2363137 #000005c5918bb70de908caf07cb8b6865ca8ff1220a0b9878eb89132ba46117b

Cheers

Graham

Thank you so much for your hints!