I'm currently rewriting my own witness-failover script, but for now, I'm relying on conductor to handle any missed blocks.
And few hours ago, it seems that it received a false positive and shutdown my witness. My guess is that it also skipped the fallback to my backup-server.
INFO:steembase.http_client:Changing http node from https://gtg.steem.house:8090 to https://steemd.privex.io
Missed -3 new blocks!
Missed 3 new blocks!
INFO:steembase.http_client:Changing http node from https://steemd.privex.io to https://rpc.buildteam.io
Witness therealwolf Disabled!
What I find interesting, is the Missed -3 new blocks! log. Didn't know you could miss negative blocks ;)
Now, I value transparency and I want everyone who is voting for me, to have a good feeling that I'm taking the task of being a Witness serious:
So if somebody was worried why my witness was deactivated for a few hours - conductor bugged out and shut down my witness. And I sadly didn't get any alert, since the witness didn't actually miss any blocks.
But everything is running again and my own failover script should be ready soon, even though conductor worked like a charm the last few months.
Wolf
If you believe that I'm a trustworthy witness - then please consider voting for me. Either through a click on the image below or at: https://steemit.com/~witnesses
Every vote counts!
