i dont know why, but again i had a outage of my miners few hours ago.
first pool is the dutch pool, second is the german pool. All miners have switched to 3rd backup pool.... (nicehash).
Why does this happen every time? Anyone knows? Am i the only one, or do more people expirience this??
first pool is the dutch pool, second is the german pool. All miners have switched to 3rd backup pool.... (nicehash).
Why does this happen every time? Anyone knows? Am i the only one, or do more people expirience this??
I'm on the Dutch node with the German as my secondary. None of my miners failed over, so I suspect you have an issue with your Internet. Maybe try adding a DNS server that isn't your ISP's as a secondary and see if this helps.
I also have the Dutch node as my first choice and experienced a short failover a few hours ago. My secondary is not Kano at the moment (my miner not at home so i don't get to change the settings very often) so I don't know about the German node.
Tomorrow, however, I will change to German as my primary node and Dutch as my second, do a reboot and see what happens. I have a feeling that the Dutch node has been a little unstable for a while as also my hashrate. Don't know if it's the miner or the node.
But they were both so quick that my monitoring didn't fire off, so when that happens (rarely) I don't usually post about it.
The catch with the NL node is that there's no AWS in Amsterdam, so I don't really want to remove that node and move it somewhere further away - since there's a lot of hash rate "close" to it ... though I am still considering ...
... and a failover should only be a few minutes to another kano node ... assuming that the miner code actually works properly ... ... ... ...
Yes the failover code is full of fail
Maybe "bitcoin" needs to find a programmer who can actually write a miner that works properly and takes pride in the quality of their code, instead of sitting around with $20-30mil and not giving a crap about it
After all these years, Bitmain can't do it, nor can ck