StratisBitcoinFullNode icon indicating copy to clipboard operation
StratisBitcoinFullNode copied to clipboard

Fault Reason: Destination array is not long enough to copy all the items in the collection. Check array index and length.

Open thecrypt0hunter opened this issue 5 years ago • 5 comments

Getting the following error whilst running Full Node on testnet (Ubuntu 18.04) - running coldstaking:

Fault Reason: Destination array is not long enough to copy all the items in the collection. Check array index and length.

Heres: a snippet of the stack trace - let me know if you need more info:

Name Type Health

CallbackMessageListener-IncomingMessage-[::ffff:51.140.242.76]:26178 Dequeuer Faulted * Fault Reason: Object reference not set to an instance of an object. CallbackMessageListener-IncomingMessage-[::ffff:51.140.242.76]:26178 Dequeuer Faulted * Fault Reason: Object reference not set to an instance of an object. CallbackMessageListener-IncomingMessage-[::ffff:51.140.242.76]:26178 Dequeuer Faulted * Fault Reason: Object reference not set to an instance of an object. CallbackMessageListener-IncomingMessage-[::ffff:51.140.242.76]:26178 Dequeuer Faulted * Fault Reason: Object reference not set to an instance of an object. NetworkPeerDisposer-peersToDispose Dequeuer Faulted * Fault Reason: Object reference not set to an instance of an object. PosMining.Stake Loop Faulted * Fault Reason: Destination array is not long enough to copy all the items in the collection. Check array index and length.

thecrypt0hunter avatar Jun 07 '19 14:06 thecrypt0hunter

When I saw this issue - I just rebooted the node and it resolved.

thecrypt0hunter avatar Jun 07 '19 15:06 thecrypt0hunter

There should be a stack trace in the node.txt file

This is not the stack trace it's the async provider output

dangershony avatar Jun 07 '19 15:06 dangershony

This was an extract from the node.txt

thecrypt0hunter avatar Jun 07 '19 21:06 thecrypt0hunter

There doesn't seem to be much else - but, I'll download and post here for further analysis

thecrypt0hunter avatar Jun 07 '19 21:06 thecrypt0hunter

probably there is a problem with AsyncProvider cutting off stack trace in some case, will investigate

MithrilMan avatar Jun 07 '19 22:06 MithrilMan