Propagation Server: RejectPuzzleSolution and DOUBLE_SPEND error messages?

[DontCopyThatFloppy]

I have a working node (with payouts), and two that appear working but have no payouts. All three were updated a couple hours ago. Most of the logs have the same entries... but for the propagation server the synchronize-store parts differ.

The working node has entries like this, so they're presumably correct, so I'm using it as a reference:

Ensuring server coin exists for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Starting synchronization for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Checking synchronization status for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
All entries in root history for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352 are synced.
Current rootHash for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352: 5a06078f0371a06e20eb313e44fd8a3e9a49c3146e947a9a397d2e02974b7834
Active epoch peers for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352: [
Completed processing peers for rootHash 5a06078f0371a06e20eb313e44fd8a3e9a49c3146e947a9a397d2e02974b7834 in store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352.
Ensuring server coin exists for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Finalizing sync for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Finalization complete for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352.

The first no-payout node looks like this:

Ensuring server coin exists for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Finalizing sync for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Finalization complete for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352.
Ensuring server coin exists for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Starting synchronization for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Checking synchronization status for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
All entries in root history for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352 are synced.
Current rootHash for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352: 5a06078f0371a06e20eb313e44fd8a3e9a49c3146e947a9a397d2e02974b7834
Error handling synced store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352: RejectPuzzleSolution

The second no-payout node looks like this:

Ensuring server coin exists for store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352...
Failed to synchronize store c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352: DOUBLE_SPEND

Any ideas how to fix those RejectPuzzleSolution/DOUBLE_SPEND issues? Or is there a way to somehow reset the nodes (short of a reinstall) to have them try again? Thanks!

[MichaelTaylor3D]

I dont know the solution to this off hand, unfortuantly, it will have to wait till i get back from my trip next week before i can debug it.