Can I get a rootHash?

[DontCopyThatFloppy]

I have an older node running fine. But a new node installed a few hours ago has its propagation server seemingly spinning through these tasks over and over...

Dig Peer A.B.C.D does not have rootHash 5a06078f0371a06e20eb313e44fd8a3e9a49c3146e947a9a397d2e02974b7834.
Dig Peer W.X.Y.Z does not have rootHash ee0a674062e40a68a9e48746199d6bbc2a553d941f20f9f8c564e07d1a2c511e

It hits a bunch of peers for 5a060* and seems to fail with all of them. Then it does ee0a6*. Then it restarts on 5a060* again. Has it somehow fallen behind its peers and now it's asking for something they don't have because they've moved on? Or those other nodes are old and because they don't have new software they don't have what my new-install is asking for?

Not a huge deal: I know it's an alpha so I expect to upgrade every day or so anyways. Thanks!

[DontCopyThatFloppy]

Since uninstall/reinstall isn't hard... and upgrades didn't seem to change anything... I deleted and started again. And it seems to be working now. So I don't know what went wrong: I gave up ;)

Marking as solved... but really this is may be something else someone else sees at some point

[MichaelTaylor3D]

Its testing if peers are synced, these peers are not synced and that is why they dont have a root hash. Likely because they are running older versions.

There are about 54 DIG Nodes and only 34 seems to actively upgrade regularly. I tried tweeting reminders but it hasnt putting a dent in these outdated nodes.

But anyways its not an error, just information that it detected outdated nodes that are not synced with the latest store updates.