Increase timeout

[matiwinnetou]

When computer is overloaded and has limited memory, it is easy to get timeout issues:

devnet:default>start
[Success] Starting node from directory : /clusters/default/node-spo1
[Success] Started submit api : http://localhost:8090
[Info] Swagger Url to interact with the cluster's node : http://localhost:10000/swagger-ui.html
Let's wait for the next block to make sure server started properly !!!
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
Waiting for next block...
[ERROR] Waited too long. Something is wrong. You may want to recreate the cluster or just reset data with 'reset' option ...
[OK] Server Started
devnet:default>tip
[Block#] 86
[Slot#] 125
[Block Hash] 14424d714e8553c9491297ea0f70d0ed9dbe28cf60533647008266c002120df7

perhaps increase timeout?

[satran004]

Thanks @matiwinnetou

If you face a similar issue again, could you please try checking if the chain is moving? Try tip more than once and check the block number.

This issue usually occurs when the chain gets stuck due to various reasons. One of the main reasons is downtime. For example, if the devnet is down for 1 minute, you need to reset it.

It's because of the low security parameter (k) value, which is currently set to 12. Don't ask me why :)

We are planning to set it to a higher default value and make it customizable, which will avoid this issue. Most probably, this will be part of the next release.