Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 985. (Read 5352429 times)

^ Just proves every little bit helps!

Block! by Lord2 with 17THs! The miner that found it was only 1THs
Maybe an S5?
and a payout

Edit: Restart block?

Yep it was saying just over 900 - but the hash rate is still around 50PHs so I guess it was a couple PH of rentals ... and I'm certainly never concerned about losing rentals ...

Meanwhile, I've resolved the problem with the passthru (written some code to report the client count) so next time the passthru screws up like this I won't be in the dark about it.
The passthru machine runs 2 passthrus, one for kano.is and a 2nd for kano.space (that only a few people ever connect to)
The 2nd one, kano.space, was ok during all this except of course for the (unneeded) pool restart that made it reconnect.

 looks like we also somehow lost a good amount of users from just yesterday. right now its saying 797 users. I could of swore that was over 900 yesterday if im remembering right.

The pool hash rate dropped to an alarmingly low 20PH there for about 10 minutes.

The problem was that the passthru stopped accepting connections at all, and dropped everyone, but kept running along without a peep about there being a problem.
My alarms of course went crazy as the hash rate spiralled down, but it took a bit of time to realise it was the passthru (since it doesn't report anything at all when running - another TODO to fix in ckpool ...)
I restarted both the main pool and the passthru to rectify the problem.

All the nodes were mining OK - they total about 20PH - but of course everyone was failed over there when I restarted the main pool.

Restarting the passthru immediately fixed the problem and the hash rate is now back to 50PH

The outage started at 07:58 UTC and was resolved at 08:10 UTC, so 60% of miners should see at least a 12 minute gap in their mining on the pool for that time, 4 minutes after the block.

All of mine failed over to their backup pool for about 15 min. All of them have reconnected now though. Must have been a problem with the main node.

Pool hash rate down to 40pH, and my ckpool monitor is beeping

Block! by blockmines
S9v2

As per the message on the notices web page: https://kano.is/index.php?k=notice


In about 49 hours - see the web site for the countdown in the header.

Edit: oops - updated - it's the NL node, not the NYA node.

They are paying for it. I literally JUST purchased this thing and it has died twice. I was actually testing it to sell ironically enough so I wouldn't be selling a bad unit. good thing I did!

Your beard looks as gray as mine!

My  late father-in-law liked hunting turkey.

Thanks for the photo.

I've spent the past 4 days turkey hunting with very limited internet access so I could not access the forum.  Looks like the pool has been rocking and rolling while I was away and April is still smoking hot!  

I did get a nice gobbler on this trip!  

I'm ready for a "100+ block" month of May! 

Yep April has been good month - and a record of course also

Avg 34.94PHs
Blocks 61
Expected 41.36
Mean Diff% 67.81%
Mean Txn% 111.07%
Luck% 147.47%
PPS% 162.33%

Anyone unsure about that PPS%, it's the total of how much the pool rewarded versus the expected 100% PPS reward for the whole pool for the month.
Each miner will of course get a different result depending upon when they mined and if they mined all month etc. but it's also random.
If you mined all month with the same hash rate, your total reward should be close to that 162.33% - it's random of course how close, and can be above or below it.
If you mined sporadically, or changed your hash rate often, then your result will have higher variance - but again, random how close, and can be above or below.

But most of all, all those miners who've been here since before November last year and have stayed around, they will of course have done very well out of making that choice not to leave after having 2 VERY good months since then recovering the bad month and putting everyone well ahead

Good luck with the repair. Hope it doesn't cost you an arm and a leg to send it back.
Mine are WAY out of warranty, so I'll have to suck up the repair costs for the hash board when I send it to Denver.

Sorry all for the OT.

What a very GREEN April we had!! 

COMEONBLOCKSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 

My brand new one is doing that exact same thing. I am sending it back to Bitmain after sending them logs and pictures. They told me the same thing, but when I look at the logs the first hash board / second chip hits 103 with the first chip only hitting 70 and then a ton of failed shutdown due to temp but the other boards are fine and this is in my server room closet with 67 f air blowing on it, so it is definitely not overheating from environmental, I think there is an issue with that board. Maybe not enough thermal past on the heat sinks or something.


freq[48]=662   freq[49]=656   freq[50]=656   freq[51]=662   freq[52]=662   freq[53]=637   freq[54]=662   freq[55]=662   
freq[56]=662   freq[57]=662   freq[58]=662   freq[59]=662   freq[60]=668   freq[61]=668   freq[62]=668   

total valid nonce number:57456
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:26854
last_nonce_num:14166
chain[5]: All chip cores are opened OK!
Test Patten on chain[5]: OK!
chain[6]: All chip cores are opened OK!
Test Patten on chain[6]: OK!
chain[7]: All chip cores are opened OK!
Test Patten on chain[7]: OK!
setStartTimePoint total_tv_start_sys=193 total_tv_end_sys=194
restartNum = 2 , auto-reinit enabled...
Fatal Error: Temperature is too high!
Fatal Error: Temperature is too high!
Fatal Error: Temperature is too high!
Fatal Error: network connection lost!
Fatal Error: Temperature is too high!
Fatal Error: network connection lost!
Fatal Error: Temperature is too high!
Fatal Error: network connection lost!
Fatal Error: Temperature is too high!
Fatal Error: network connection lost!

Fatal Error: network connection lost!
Fatal Error: Temperature is too high!
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[5]: (asic index start from 1-63)

get RT hashrate from Chain[6]: (asic index start from 1-63)

get RT hashrate from Chain[7]: (asic index start from 1-63)
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=29
read failed, old value: Chain[5] Chip[62] local Temp=91
read failed on Chain[5] Chip[62] middle Temp old value:103
Chain[5] Chip[32] TempTypeID=55 middle offset=28
read failed, old value: Chain[5] Chip[32] local Temp=62
read failed on Chain[5] Chip[32] middle Temp old value:81
Done read temp on Chain[5]
do read temp on Chain[6]

damn  this pool has had a great april


Monthly Statistics

UTC Month........Pool Avg....Blocks......Expected...Mean Diff%.......MeanTx%............Luck%........PPS%
2017 Apr........…34.94PHs...61...........41.36........67.81%............111.07%...........147.47%.....162.33%

Almost 150% luck

we just need 1 more block to finish at 149.9%  or 2 more to do 152.32%

but to be honest I will take 147.47% anytime

S9v2

Block!

Congrats moecarrim !  

Been "off the grid" for 5 days sailing 40 miles off-shore from South Carolina to New Jersey. Too many pages to read to catch up, so I just read last five. Gotta say, we were having a fantastic April when I left and it has gotten even better!! Way to rock it, fellow miners!


@blockchainmines: Congrats on cranking up your hashing total. I enjoyed watching your videos and seeing your setup. Very happy to have you here at Kano Pool.