BitShares unplanned maintenance

[xeroc]

I wrote an incident report .. waiting for the lawyer to approve the stuff that comes with that report

[Chronos]

Has anyone written a technical overview of what went wrong and what the fix was?

I'd definitely be interested in more details, as well. Bitshares outages have seen so rare since 2.0 was released. This was a major event!

[karnal]

Has anyone written a technical overview of what went wrong and what the fix was?

[R]

Good time to analyze which witnesses were quick to react with this situation.

I know xeldal, lafona and sahkan are updating. no idea about the others

Surely their 'missed blocks' statistic is going to go through the roof soon? Might spur a shift in voting intent!

[fav]

Good time to analyze which witnesses were quick to react with this situation.

I know xeldal, lafona and sahkan are updating. no idea about the others

[yvv]

Good news. The issue was handled pretty well.

[Brekyrself]

Good time to analyze which witnesses were quick to react with this situation.

[fav]

we're back https://steemit.com/bitshares/@ash/beauty-sleep-is-over-bitshares-restarting

[fav]

Update 9 (Aftermath): https://steemit.com/bitshares/@ash/bitshares-entered-unplanned-maintenance-mode

[fav]

Update 8 (final?): https://steemit.com/bitshares/@ash/bitshares-entered-unplanned-maintenance-mode

[fav]

Update 7: https://steemit.com/bitshares/@ash/bitshares-entered-unplanned-maintenance-mode

[fav]

Update 6: https://steemit.com/bitshares/@ash/bitshares-entered-unplanned-maintenance-mode

[fav]

Update 5: https://steemit.com/bitshares/@ash/bitshares-entered-unplanned-maintenance-mode

[fav]

Witnesses are incapable of producing blocks b/c there is an issue that prevents verifying the previous chain - a particular transaction is fouling up the works. Dan Larimer and witnesses are working the problem as fast as possible.

[crypto4ever]

How is this even technically possible?

Did all the miners stop mining at the same time?

Is there a bug in the code?


<3
JQ

There's data in a particular block (from what I've read) that caused this problem. It's probably a minor fix. It just takes time to understand it, create a fix, and then test it.  It's a small hiccup, and once fixed, you probably won't see this happen ever again.

The extra time they are taking to be careful they fix it right and the fix is 100% good, I like.  I don't want them to rush writing a cheap fix.   Leave them some time.

...and usually someone will write a blog post explaining what happened and how it was fixed after this is all over.