Page 1 of 2

System catching up

Posted: Thu Dec 07, 2017 7:09 am
by Steve Sokolowski
There was a problem overnight where the share inserters stopped inserting data into the database. As designed, the system stored the shares in memory until someone was able to address the problem. The shares are being inserted right now and should recover throughout the next few hours. During this time, the reported numbers will be all over the place, because they are processing old data.

No money was lost, and we will correct the charts later in the morning. Feel free to reply if you have any additional questions.

Someone asked why this seems to happen when releases occur. The short answer is that unlike, say, a game, where you can program it and test it on your computer before shipping it, there is no way to test the huge number of miners that connect to this system before release. We can only simulate "fake" miners, which will catch some bugs but not ones due to network conditions, or specific types of miners, or attacks like the one on the Bitconnectcoin network.

Fortunately, I'd like to hope that we've gotten better at it. This release was more complex than the x11 release in April and resulted in just this one issue, which I've already identified the cause of and am looking into now. I don't think there are a large number of bugs that still remain to be found, as this same issue caused two crashes and there were 8 hours between.

Re: System catching up

Posted: Thu Dec 07, 2017 7:26 am
by Foldmine
Good to know. I was worried that my miners were off, but not switching to backup pool and not recording shares here. Thanks for the info

Re: System catching up

Posted: Thu Dec 07, 2017 7:31 am
by dronKZ
Steve Sokolowski wrote:There was a problem overnight where the share inserters stopped inserting data into the database. As designed, the system stored the shares in memory until someone was able to address the problem. The shares are being inserted right now and should recover throughout the next few hours. During this time, the reported numbers will be all over the place, because they are processing old data.

No money was lost, and we will correct the charts later in the morning. Feel free to reply if you have any additional questions.
Hi Steve, a successful update and the system's operation did not doubt you either when the rebate is restored, but then there is such a question on the payment system, I had payments at 13.00-15.00, I was happy with this at the moment, payments are made early in the morning at 5-6, it is very inconvenient to change the time of payments for my time zone? 6 Astana !?

Re: System catching up

Posted: Thu Dec 07, 2017 7:40 am
by NYCrypto1
Hey Steve,

There is still a problem with the payouts though. I have not been paid of my Zcash or Bitconnect in 2 days, just restarts timer. Can we fix the payouts?

Re: System catching up

Posted: Thu Dec 07, 2017 7:56 am
by Steve Sokolowski
NYCrypto1 wrote:Hey Steve,

There is still a problem with the payouts though. I have not been paid of my Zcash or Bitconnect in 2 days, just restarts timer. Can we fix the payouts?
The Bitconnect network is under attack and is not processing any transactions because the attacker is not including transactions in his blocks. It is possible that all bitconnectcoins are permanently lost, because they will never be able to be transferred. We will, of course, send them to you if the attack ends. If we gain enough hashrate here, then we will attempt to reverse the attacker's blockchain and restore the normal operation of the network. You can follow the orphans at https://chainz.cryptoid.info/bcc/orphans.dws. As you can see, they are still ongoing as of an hour ago. The chart is misleading because it counting orphans from midnight until now, so today's point is always going to be lower.

For the ZEC payments, please submit a support ticket. Chris will investigate the issue when he works on installing and updating coins later today.

Re: System catching up

Posted: Thu Dec 07, 2017 8:16 am
by Morbiduzz
It continue to disconnect one of my miners damn!! It appear dead on miner setup page

Re: System catching up

Posted: Thu Dec 07, 2017 8:32 am
by Steve Sokolowski
Morbiduzz wrote:It continue to disconnect one of my miners damn!! It appear dead on miner setup page
I think this is an issue specific to your miner. I can't reproduce it and I haven't heard this from anyone else recently either :(

Re: System catching up

Posted: Thu Dec 07, 2017 8:50 am
by gnikminer
Steve Sokolowski wrote:
Morbiduzz wrote:It continue to disconnect one of my miners damn!! It appear dead on miner setup page
I think this is an issue specific to your miner. I can't reproduce it and I haven't heard this from anyone else recently either :(

Steve,

I don't know what hours you work or if you access the server's remotely, etc, but I have been having this issue as well, with the mass majority of my miners, and I've seen complaints from other members as well. For the most part, I've been able to isolate some parameters and conditions for this to occur. I've found some workarounds on my side, but I'm willing to bet it adds a little bit too your servers' workload (as well as requires resources I'd prefer not to use on my end). Unfortunately, my day job makes me unavailable during what most consider normal working hours (I'm central time), but if you are available outside of that to look into this issue, I believe that I may provide some value to you.

Re: System catching up

Posted: Thu Dec 07, 2017 9:40 am
by illuminati
Thanks for being so active on here and keeping all informed.

Re: System catching up

Posted: Thu Dec 07, 2017 9:45 am
by Steve Sokolowski
gnikminer wrote:
Steve Sokolowski wrote:
Morbiduzz wrote:It continue to disconnect one of my miners damn!! It appear dead on miner setup page
I think this is an issue specific to your miner. I can't reproduce it and I haven't heard this from anyone else recently either :(

Steve,

I don't know what hours you work or if you access the server's remotely, etc, but I have been having this issue as well, with the mass majority of my miners, and I've seen complaints from other members as well. For the most part, I've been able to isolate some parameters and conditions for this to occur. I've found some workarounds on my side, but I'm willing to bet it adds a little bit too your servers' workload (as well as requires resources I'd prefer not to use on my end). Unfortunately, my day job makes me unavailable during what most consider normal working hours (I'm central time), but if you are available outside of that to look into this issue, I believe that I may provide some value to you.
If you'll be available anytime between 9pm and 4am Central tonight, then Chris would love to talk to you about this. Thanks!