Author

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

hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
Almost 10PH folks
luckyant kicking on the afterburners.
Flux capacitor fluxing
hero member
Activity: 770
Merit: 523
Almost 10PH folks
luckyant kicking on the afterburners.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
Restart itself takes just seconds but ckdb reloads everything and processing all data for a few minutes after start, before data will be available on website for users.

Ahh i see. So the 20 minutes Kano talks about is the time it took for the system to get back up to speed as far as the web front end..  But all the while its processing shares regardless of how the front end looks question marks and all.. Thanks again for clearing that up.. im going to attempt an install of his open source pool software for my own solo pool. I currently run mpos with node.js for stratum..

Best Regards
d57heinz
full member
Activity: 157
Merit: 103
Restart itself takes just seconds but ckdb reloads everything and processing all data for a few minutes after start, before data will be available on website for users.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
While Kano is sleeping I may try to answer - if my answer instead of Kano will be ok to you.

ckdb works together with ckpool and all miners works against ckpool.
As Kano restarting ckdb only it doesn't affect on mining process and on shares count, these are logged with ckpool.  After ckdb restart it reloads all log files from ckpool and processing all data. Nothing lost.

Thanks for answering that for me,, I wondered how he was doing that.. Since it takes 20 min or so..

Best Regards
d57heinz
full member
Activity: 157
Merit: 103
While Kano is sleeping I may try to answer - if my answer instead of Kano will be ok to you.

ckdb works together with ckpool and all miners works against ckpool.
As Kano restarting ckdb only it doesn't affect on mining process and on shares count, these are logged with ckpool.  After ckdb restart it reloads all log files from ckpool and processing all data. Nothing lost.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
Restart took 22 minutes (and completed 6 minutes ago)
Looks like I better add into the todo list: speeding up the restart since the extra time is of course due to the pool growth.

Kano,  
can you explain to me how the system keeps track of shares during all these ckdb restarts..?  

reason i ask is i dont see any difference in my shift records.. I figure you must have a procedure that keeps the sharelogging going to the very end, maybe thats the last thing you have to reload??

Best Regards
d57heinz
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
where is all this hash power coming from? slush? or solo pool?

i like it!!  Smiley

i just need more hash my self now to get the reward up Cheesy


edit: Btw someone with skills make a cool Signature we could use  Smiley


Well, I switch 'display signature' allways to OFF  ...  Cheesy
hero member
Activity: 572
Merit: 506
Holy Cow.  8PH and growing!!! 

Finally Kano pool is growing like it should! Great job Kano

Agreed  Cheesy
member
Activity: 109
Merit: 10
where is all this hash power coming from? slush? or solo pool?

i like it!!  Smiley

i just need more hash my self now to get the reward up Cheesy


edit: Btw someone with skills make a cool Signature we could use  Smiley
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Payout 391403 sent - to VRobb and everyone else Smiley
559d51ae2800466e8ff49ee108ff6a426e513f762379bb28bd01789f00bfaadf
and confirmed
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
Frankly I feel lucky and honored to have stumbled across the kano ckpool(s) as I'm quite new to this game and spent a lot of time researching where/what/how to get onto btc mining.  ck and kano-san are doing great things for the health and longevity of btc - how do I know? Easy, just go back to page 1 of this thread, as I did, and read it for yourself.  The integrity and fortitude shown by our esteemed sysops is not just words. Their actions speak volumes as to the class these two gentlemen show to us, the pool members, and to the whole concept of btc and the ramifications their actions have.
I have a new s7 on the way, and as I mentioned  in a previous post, to consider pointing my hardware anywhere else but here is unthinkable to me.  I am an old-school computer guy, from the days of pdp's, teletypes, and trash-80's. Once I see the right way to do something, then that's the way to do it. Period.
All hail ck and kano! Showing the rest of the code bozos how it's done!
legendary
Activity: 1484
Merit: 1004
Holy Cow.  8PH and growing!!! 

Finally Kano pool is growing like it should! Great job Kano
full member
Activity: 196
Merit: 100
Holy Cow.  8PH and growing!!! 
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Restart took 22 minutes (and completed 6 minutes ago)
Looks like I better add into the todo list: speeding up the restart since the extra time is of course due to the pool growth.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
Congrats on the pool growth, glad to see kano.is starting to get the hash it deserves.

I agree with this 100%.. its refreshing to get on a pool with vibrant life behind it:)


Got a ckdb restart coming in again shortly.

As expected for a ckdb restart, no miners will be affected at all.

Web site stats will be unavailable or '?' for about 10 minutes.

This one is rather urgent since I've found an issue where certain data is never freed and thus over time ram usage grows to use up the whole server.
The new size of the pool of course means this is happening faster so this is the first time I've confirmed the problem ... and of course worked out where the problem is and fixed it.

Restart will specifically be in 45minutes when the minute hand hits zero Smiley

Thanks for the heads up.. Good time for me to fix some of my backup pools..

Best Regards
d57heinz
sr. member
Activity: 294
Merit: 250
Got a ckdb restart coming in again shortly.

As expected for a ckdb restart, no miners will be affected at all.

Web site stats will be unavailable or '?' for about 10 minutes.

This one is rather urgent since I've found an issue where certain data is never freed and thus over time ram usage grows to use up the whole server.
The new size of the pool of course means this is happening faster so this is the first time I've confirmed the problem ... and of course worked out where the problem is and fixed it.

Restart will specifically be in 45minutes when the minute hand hits zero Smiley

Thanks for the heads up.  Great communication as usual!
hero member
Activity: 770
Merit: 523
Got a ckdb restart coming in again shortly.

As expected for a ckdb restart, no miners will be affected at all.

Web site stats will be unavailable or '?' for about 10 minutes.

This one is rather urgent since I've found an issue where certain data is never freed and thus over time ram usage grows to use up the whole server.
The new size of the pool of course means this is happening faster so this is the first time I've confirmed the problem ... and of course worked out where the problem is and fixed it.

Restart will specifically be in 45minutes when the minute hand hits zero Smiley
Memory leaks good to find. Excellent work sir.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Got a ckdb restart coming in again shortly.

As expected for a ckdb restart, no miners will be affected at all.

Web site stats will be unavailable or '?' for about 10 minutes.

This one is rather urgent since I've found an issue where certain data is never freed and thus over time ram usage grows to use up the whole server.
The new size of the pool of course means this is happening faster so this is the first time I've confirmed the problem ... and of course worked out where the problem is and fixed it.

Restart will specifically be in 45minutes when the minute hand hits zero Smiley
hero member
Activity: 770
Merit: 523
I like the two big spikes before each of the last blocks. Brilliant.
Jump to: