Author

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

newbie
Activity: 11
Merit: 0
How do I get verified? I looked through my email and don't see anything to reply too.
member
Activity: 658
Merit: 21
4 s9's 2 821's
Good, because we're down 5PH now.    Embarrassed
It's not all canaan's miners moving off. 
member
Activity: 126
Merit: 10
Good news. They are going to talk to the block gods for us. Standby gents.
member
Activity: 658
Merit: 21
4 s9's 2 821's
Just made is to Disney World for the weekend. On my way to a meeting with the 7 dwarfs. Going to get this mining issue resolved. Heard they know how to crack blocks.


Multiple blocks preferable!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
just a ? and maybe a sort of a heads up to kano in case it is an issue that you are not aware of..      

for the last 2 weeks I happened to notice that any time a block is found on the network and then the pool starts working on a new block. I have noticed the time it takes for the pool to start on the new work is some times as much as 5 mins behind.

for instance block number 499476 found by slushpool at 2017-12-15 13:31  and then they instantly started working on block 499477 and working on it for almost 5 mins before the time kano pool switched and started the new work on trying to work on block 499477

sometimes its only about 15-20 seconds difference that the pool takes to switch on to a new block and get to work and figured that was just normal time its taking for other pools to switch work after another pool finds a block..    But over 4 mins seems like a real long relay time.  

so incase that is longer then it should take I figured I would say something to let you know so if it is a problem you could see what the cause might be.   Tho if not then I guess its no biggie and you would know its not any thing that could cause any issue with the pool missing out on the big race to find a block before any other pool ever did.  





I had noticed the same thing. Kano assured me that the Pool immediately goes to work on the new work for the new block. No delays. He would know since he has the tools to monitor the hash on each block. He explained to me that many Internet providers use proxies for websites and they are not always updated properly. I pushed the I believe button because he would know since he is monitoring the back end. Now with that said... timing in this game is everything. Ensure that you mine to the fastest ping Pool node for your location. In my case, it is the NYA with a 14ms ping.

MINE ON!!! KANO-SAN has got our back!!

True I know if there is anyone thats can be trusted to even know what he's talking about as far as how things work its Kano. and if something was anything that could cause problems with the pool or cause it to have worse luck hitting blocks it would be in his interest and every one mining to find and fix and bugs or issues that were found if there was a problem with anything.

and glad to know that delay in the time shown from the time new work started on block and new work is not a real problem. Tho now that I thing about it some more and knowing how the info pages are also on a different server than the actual pool its self I can see how it would have to lag behind a bit on what ever data that needs to go from one place to another to be displayed.


So going through the logs for that specific block:

499476
000000000000000000a90fdd34d539c9a25a56355a245708ff855f9e3245e98b

Pool log:
[2017-12-15 18:31:22.912+00] Block hash changed to 000000000000000000a90fdd34d539c9a25a56355a245708ff855f9e3245e98b

Mining monitor - when it saw the block change.
It's in the USA and connects to every mining node (not in china) no some may take a fraction of a second longer,
The last one (pool 1) is in singapore and I guess the connection from the USA to there and back to the USA was a little slow for that one Tongue
But the times there show when the work change, sent from the main server, arrived at the monitor, after going via the node.
 [2017-12-15 18:31:22.953] Stratum from pool 10 detected new block at height 499476
 [2017-12-15 18:31:22.956] Stratum from pool 0 requested work restart
 [2017-12-15 18:31:22.960] Stratum from pool 11 requested work restart
 [2017-12-15 18:31:22.963] Stratum from pool 7 requested work restart
 [2017-12-15 18:31:23.004] Stratum from pool 4 requested work restart
 [2017-12-15 18:31:23.012] Stratum from pool 8 requested work restart
 [2017-12-15 18:31:23.012] Stratum from pool 6 requested work restart
 [2017-12-15 18:31:23.045] Stratum from pool 9 requested work restart
 [2017-12-15 18:31:23.220] Stratum from pool 2 requested work restart
 [2017-12-15 18:31:23.238] Stratum from pool 5 requested work restart
 [2017-12-15 18:31:23.376] Stratum from pool 3 requested work restart
 [2017-12-15 18:31:25.727] Stratum from pool 1 requested work restart

So basically it's all OK for that block, so I'm not sure what the cause was for you seeing it minutes later.
Also note that the web site shows the time in the bottom left and right in tiny letters - check what it says there also next time you see this.
The left is the web server UTC and the right is what your browser thinks the current time is.
i.e. you may be seeing a cached copy of the web site and it would show the server time in the past.

The web server itself doesn't use any caching or cloudflare or anything like that since firstly, cloudflare is a security risk (you have to give them your SSL certificate and thus trust every employee of every company that has access to their servers) and secondly, the code/server is configured to handle the load pretty well without the need for that.
i.e. the web server doesn't take minutes to send you the data, it's immediate, and the data it uses is immediate.
The timeouts that sometimes occur, might cause a delay since the web page is made up of 2 requests, the header and the content.
That would be extremely rare, since the timeout would have to occur right between the 2 requests.
But the web page content would be all wrong, so you'd know about that happening.
The timeout itself can mean everyone for up to about 30 seconds or so after it may show timeout messages with nothing else, but not pages with out of date information.
member
Activity: 126
Merit: 10
Just made is to Disney World for the weekend. On my way to a meeting with the 7 dwarfs. Going to get this mining issue resolved. Heard they know how to crack blocks.
full member
Activity: 341
Merit: 100
just a ? and maybe a sort of a heads up to kano in case it is an issue that you are not aware of..      

for the last 2 weeks I happened to notice that any time a block is found on the network and then the pool starts working on a new block. I have noticed the time it takes for the pool to start on the new work is some times as much as 5 mins behind.

for instance block number 499476 found by slushpool at 2017-12-15 13:31  and then they instantly started working on block 499477 and working on it for almost 5 mins before the time kano pool switched and started the new work on trying to work on block 499477

sometimes its only about 15-20 seconds difference that the pool takes to switch on to a new block and get to work and figured that was just normal time its taking for other pools to switch work after another pool finds a block..    But over 4 mins seems like a real long relay time.  

so incase that is longer then it should take I figured I would say something to let you know so if it is a problem you could see what the cause might be.   Tho if not then I guess its no biggie and you would know its not any thing that could cause any issue with the pool missing out on the big race to find a block before any other pool ever did.  





I had noticed the same thing. Kano assured me that the Pool immediately goes to work on the new work for the new block. No delays. He would know since he has the tools to monitor the hash on each block. He explained to me that many Internet providers use proxies for websites and they are not always updated properly. I pushed the I believe button because he would know since he is monitoring the back end. Now with that said... timing in this game is everything. Ensure that you mine to the fastest ping Pool node for your location. In my case, it is the NYA with a 14ms ping.

MINE ON!!! KANO-SAN has got our back!!

True I know if there is anyone thats can be trusted to even know what he's talking about as far as how things work its Kano. and if something was anything that could cause problems with the pool or cause it to have worse luck hitting blocks it would be in his interest and every one mining to find and fix and bugs or issues that were found if there was a problem with anything.

and glad to know that delay in the time shown from the time new work started on block and new work is not a real problem. Tho now that I thing about it some more and knowing how the info pages are also on a different server than the actual pool its self I can see how it would have to lag behind a bit on what ever data that needs to go from one place to another to be displayed.

member
Activity: 210
Merit: 15
just a ? and maybe a sort of a heads up to kano in case it is an issue that you are not aware of..      

for the last 2 weeks I happened to notice that any time a block is found on the network and then the pool starts working on a new block. I have noticed the time it takes for the pool to start on the new work is some times as much as 5 mins behind.

for instance block number 499476 found by slushpool at 2017-12-15 13:31  and then they instantly started working on block 499477 and working on it for almost 5 mins before the time kano pool switched and started the new work on trying to work on block 499477

sometimes its only about 15-20 seconds difference that the pool takes to switch on to a new block and get to work and figured that was just normal time its taking for other pools to switch work after another pool finds a block..    But over 4 mins seems like a real long relay time.  

so incase that is longer then it should take I figured I would say something to let you know so if it is a problem you could see what the cause might be.   Tho if not then I guess its no biggie and you would know its not any thing that could cause any issue with the pool missing out on the big race to find a block before any other pool ever did.  





I had noticed the same thing. Kano assured me that the Pool immediately goes to work on the new work for the new block. No delays. He would know since he has the tools to monitor the hash on each block. He explained to me that many Internet providers use proxies for websites and they are not always updated properly. I pushed the I believe button because he would know since he is monitoring the back end. Now with that said... timing in this game is everything. Ensure that you mine to the fastest ping Pool node for your location. In my case, it is the NYA with a 14ms ping.

MINE ON!!! KANO-SAN has got our back!!
full member
Activity: 341
Merit: 100
just a ? and maybe a sort of a heads up to kano in case it is an issue that you are not aware of..      

for the last 2 weeks I happened to notice that any time a block is found on the network and then the pool starts working on a new block. I have noticed the time it takes for the pool to start on the new work is some times as much as 5 mins behind.

for instance block number 499476 found by slushpool at 2017-12-15 13:31  and then they instantly started working on block 499477 and working on it for almost 5 mins before the time kano pool switched and started the new work on trying to work on block 499477

sometimes its only about 15-20 seconds difference that the pool takes to switch on to a new block and get to work and figured that was just normal time its taking for other pools to switch work after another pool finds a block..    But over 4 mins seems like a real long relay time.  

so incase that is longer then it should take I figured I would say something to let you know so if it is a problem you could see what the cause might be.   Tho if not then I guess its no biggie and you would know its not any thing that could cause any issue with the pool missing out on the big race to find a block before any other pool ever did.  



member
Activity: 73
Merit: 10
Under my shift worker tab. The 5nd is in the red but im past that on the bar graph.
Over on the right i have a number of 6.97 i believe. Is that my current hash rate? So that means im half way to the 5nd?

Just one s9?  Yeah you're over 1/2 way there.  The red graph gets confusing with a smaller  pool, it was much easier for a rookie to understand when this pool was hitting 5 blocks in 5 days.   When the next block hits, the stuff to the right of the red area will be in red, and the left side of the current red area will be white (and out of the 5nd).   How much is not in the red will be determined when we find that next block.


MINE ON
Yes just one s9.

Thanks for the help on it!

Its slowly coming up
newbie
Activity: 10
Merit: 0
This is voodoo - had a couple S9's with same problem. One board (always chain 6) either dead or missing chips on reboot.


This works for me - not sure why?


Turn off all power for a few mins

Reboot with no internet connection

Let it cycle for about 30 mins - it will start up and shut down repeatedly.

Connect internet.

Magic - it runs for about 2 weeks above 13.5TH/s.  

Sometimes repeat a couple of times till you get the correct performance - be patient - wait at least 24 hrs till you decide.  
If GH/S(ideal) for chain 6 (or any chain) is in the 2k range - repeat immediately.  All 3 chains should be above 4k.

Then eventually (after about 2 weeks with 100 x HW errors of the other 2 chains) chain 6 board goes down over a couple of hours in GH/S(ideal) to the 2k region.

Just repeat and it recovers - all good for another couple of weeks.

I'd be very interested to know if it works for you - and if anyone might have an idea why?


NEVER return your miner to Bitmain China (via Hong Kong) on warranty - they take over a month and send somebody else faulty shit miner back - dirty full of mosquitos from Taiwan, not fixed and with same chain 6 problem.  Its just a Swaparoo (an Aussie term that CAN mean just keep moving things around, look busy and trying to help - but don't do anything useful).  Support goes DEAD eventually if you keep complaining that your WARRANTY replacement has the same problem you started with.

Cheers - usukan



Giving this a shot now on my 14TH/s version. It's had 1 board (chain 6) acting up over the past few days....sometimes it comes online and only detects 12 asic chips and reads a temperature of 15*, sometimes it detects all the asics but outputs 0 hashing power, then sometimes the hashing power output for the whole device shows 0 when in reality it's cranking out the normal amount.

When it does work it seems to only work for a day or two until some of the hashing power starts dropping off, yet the miner status page shows it as hashing at full speed. Usually a reboot or a shutdown temporarily fixes the issue, but this last time it was giving me issues several reboots didn't remedy the problem...the board would come online with all 63 asics detected, but no hash power.

So I'm attempting your fix right now. Shut the unit down through command line then killed the breaker to it, let it sit momentarily while disconnecting the network cable, flipped the breaker back on and am letting it try to connect/reboot itself with no connection. Will be plugging in the network cable shortly and hoping for the best! Will update with my outcome!
member
Activity: 658
Merit: 21
4 s9's 2 821's
Under my shift worker tab. The 5nd is in the red but im past that on the bar graph.
Over on the right i have a number of 6.97 i believe. Is that my current hash rate? So that means im half way to the 5nd?

Just one s9?  Yeah you're over 1/2 way there.  The red graph gets confusing with a smaller  pool, it was much easier for a rookie to understand when this pool was hitting 5 blocks in 5 days.   When the next block hits, the stuff to the right of the red area will be in red, and the left side of the current red area will be white (and out of the 5nd).   How much is not in the red will be determined when we find that next block.


MINE ON
newbie
Activity: 65
Merit: 0
There will be a DB restart in about 30 minutes, around 12:30 UTC
It will actually be when the zekken shift completes and is processed - which will be about then.

No mining will be affected at all.

The web site and API will reply with lotsa zeros and '?' marks during a DB restart, for about 10 minutes.

This is a minor update to try and deal with the timeouts that occur every once in a while - and I'll now mention the actual cause since I've implemented a way to deal with them Smiley
The rewards and payouts pages go back to when the pool started for some miners.
The data back then gets swapped out of ram and sometimes when a long term miner checks their rewards and payouts, it takes too long to swap back into ram and times out on the web page.
I think the actual cause is if two different people do it at the same time - which would also explain why it's not very common.
This change helps stop that data from ever swapping out, since the DB now runs with a RES footprint smaller than bitcoin and a VIRT size smaller than ckpool, it's OK to stop that data from being swapped out.

I'll post again once the DB restart has completed.
KanoDB restart complete.
Was from 12:31 to 12:37 UTC
Mine on Smiley

Yep, saw that 30 min ago... came here to see what was going on. Thanks for explaining!

www2.netdoor.com/~wblaster/CKPool_WebUI-Down_Dec15-2017.jpg
www2.netdoor.com/~wblaster/CKPool_WebUI-Down_Dec15-2017b.jpg
member
Activity: 73
Merit: 10
Under my shift worker tab. The 5nd is in the red but im past that on the bar graph.
Over on the right i have a number of 6.97 i believe. Is that my current hash rate? So that means im half way to the 5nd?
member
Activity: 73
Merit: 10
Looks like another attack on the site again.


Attack on the site, but miners are running on a different server. 
Good!
member
Activity: 658
Merit: 21
4 s9's 2 821's
Looks like another attack on the site again.


Attack on the site, but miners are running on a different server. 
member
Activity: 73
Merit: 10
Looks like another attack on the site again.
sr. member
Activity: 308
Merit: 251
I like big BITS and I cannot lie.
Yeeeah, soo, im gonna have to have you guys go ahead and find some blocks. Mmkay?

Oh, and yea... going to have to have you come in on Sunday and find some more blocks. Mmkay?

That would be great.

I'm in my alchemy lab trying to perfect my luck potions. Will update on results.
newbie
Activity: 33
Merit: 0
Yeeeah, soo, im gonna have to have you guys go ahead and find some blocks. Mmkay?

Oh, and yea... going to have to have you come in on Sunday and find some more blocks. Mmkay?

That would be great.
member
Activity: 210
Merit: 15
Here Kitty, Kitty, Kitty.... Here Kitty, Kitty Kitty..... bring that block on over here. Mine On!!
Jump to: