I have also experienced v0.6.1 getting stuck at certain blocks (verified by get_info). Restarting the client seems to fix it (it syncs to the present block on restart), but it typically will end up getting stuck at some point again. This seems a lot less stable than v0.6.0.

The only "fork" related messages I see in logs/p2p/p2p.log are various messages similar to the following:

2015-02-14T13:21:48 th_a:invoke handle_message           push_block ] unable to link longest fork ["702ff49818c179c81a58fee4222019125340ae53",{"next_blocks":[],"is_linked":true,"is_valid":false,"invalid_reason":{"code":30019,"name":"time_in_future","message":"time is in the future","stack":[{"context":{"level":"error","file":"chain_database.cpp","line":837,"method":"verify_header","hostname":"","thread_name":"th_a","timestamp":"2015-02-14T13:18:41"},"format":"","data":{"block_digest.timestamp":"2015-02-14T13:19:10","now":"2015-02-14T13:18:41","delta_seconds":29}},{"context":{"level":"warn","file":"chain_database.cpp","line":848,"method":"verify_header","hostname":"","thread_name":"th_a","timestamp":"2015-02-14T13:18:41"},"format":"","data":{"block_digest":{"previous":"21e3abc711b7e90f683bff8c13ae6b8c34df41f2","block_num":1787605,"timestamp":"2015-02-14T13:19:10","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"d32f5a705db5ef8082f29fd6b21c6ac63c5d9856","previous_secret":"65bdc28ac7fb31156f3ad1c4d14cadb37c715326","delegate_signature":"1f1082bf13e8eb7d4900937b52e02022457d077525d4236efb3c5a7be668adb7c6604945d01f0ece6dd54cb4c83e4831ba7ffd280bd0121dc4c16d3a519ef15d07","user_transaction_ids":[]},"block_signee":"BTS8eLeqSZZtB1YHdw7KjQxRSRmaKAseCxhUSqaLxUdqvdGpp6nck"}}]},"is_included":false,"is_known":true}] chain_database.cpp:1799


Quote from: DataSecurityNode on February 14, 2015, 05:21:18 AM
I had a similar issue with my wallet today. I was still running 0.5.3. I upgraded thinking it would solve the issue, but it still persisted even after the upgrade. Same as what you describe with just being stuck at a block. Finally I forced a reset of the database and it got working.

Never had an issue with a stuck block like that before with this system.

I'm running 6.1 and I also had to reset the data base today.

I had a similar issue with my wallet today. I was still running 0.5.3. I upgraded thinking it would solve the issue, but it still persisted even after the upgrade. Same as what you describe with just being stuck at a block. Finally I forced a reset of the database and it got working.

Never had an issue with a stuck block like that before with this system.

I resynced and upgraded my memory from 4GB to 16GB and now I'm running smooth as can be.  Thanks for the help!

before you resync can you go to advanced and find the console, then type 'getinfo' in the console and note the last block, then wait 1 minute and type 'getinfo' again and see if the block changed? Some times the stuck on a block issue is just a GUI issue and the blocks are actually still syncing behind the scene.

Resync...

0. Backup your wallet
1. Go %appdata%\Bitshares
2. Delete everyting EXCEPT wallet folder
3. Start Bitshares again and wait loooooooong time :)

Everything was syncing smoothly with 0.6.1 until it got to block #1083620 and now it's not syncing anymore.  I have between 8-15 network connections and have restarted a couple times.  It's similar to my issue with 0.5.3 I mentioned here:  https://bitsharestalk.org/index.php?topic=13845.0

Any idea what I can do?   :-[