Quote from: jaapgvk on August 21, 2018, 06:10:54 PM

Quote from: zthomasz on August 21, 2018, 03:13:34 PM

Quote from: bible_pay on August 21, 2018, 02:12:24 PM

Quote from: zthomasz on August 21, 2018, 01:47:36 PM

Quote from: bible_pay on August 21, 2018, 11:46:20 AM

Quote from: MIP on August 21, 2018, 06:08:16 AM

It seems there is another strange block around there, half of my MNs have all stopped just at 65736 and then expired.

Did our recovery mode catch it or are they not yet on that new version yet?

Mine look OK today, but I do see 2 that say restart required all of a sudden.

Same here, expired, restart required about 12 hours ago.

We recently added a feature to 1.1.4.5 to allow a node to recover. I'm pushing this (on the linux side) to the latest version now so we can upgrade to this version (if we find we need to upgrade nodes today).

Did these sancs in question crash, or fork, or are they still synced guys?

biblepayd stopped running, so I restarted it, then restarted the sanc from the controller wallet, synced at block 65930.

I think that mine forked or stalled. They were on lower blockheights but still running.

In your case 1.1.4.5 should have helped it recover.

I just checked one and it says 'core dumped', so Im running my sanc in valgrind mode. Lets hope it gives us the line # this next go around.