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

[/quote]

did you not even read the 4-5 posts before yours?
[/quote]

Has the event ever occured that something positive was produced by the walnut of yours where other people have a brain? 
[/quote]

So you didn't read and expected everyone to explain it to you in layman's terms.   Got it, you're one of the lazy.
[/quote]

and you are probably one of the most grumpy... 


ey, let's burry the axe, okay?
this goes nowhere...
[/quote]


There were two Salvos fired so far.
the "did you not even read the 4-5 posts before yours?"
and
"Has the event ever occured that something positive was produced by the walnut of yours where other people have a brain?  "

Of the two the second is more of a personal insult about one's mental capacity.
The first is a general RTFM comment often used by those who feel someone is not doing due diligence in researching an issue.

both comments could have been handled better. We are not taunting each other to gain advantage in battle. Most of us will never see one another
in real life. Most of us want the same thing, to mine and get some value out of this bitcoin mining thingy.

Lets shake hands and agree to disagree harmoniously.

and you are probably one of the most grumpy... 

ey, let's burry the axe, okay?
this goes nowhere...

So you didn't read and expected everyone to explain it to you in layman's terms.   Got it, you're one of the lazy.

Has the event ever occured that something positive was produced by the walnut of yours where other people have a brain?  



No, havn't seen it. i had to refresh the page in order to see indeed. I wouldn't ask if i did... 

If we all would leave out messages like yours that don't contribute anything other than making this forum less readable, it would be possible to see all new interesting post'


thanks.

I am aware of the false block found symptom after a pool restart. I also can see where 2400 would be valid for midnight depending on how you define things.
What I was a bit concerned about was that the Last Block: found time is 2018-05-21 24:08:25.

That has a time stamp of over 24 hours and is not a valid time in any system I know of on planet earth.

From John Ringo's "Troy Rising" series book one.
“It is said that in science the greatest changes come about when some researcher says "Hmmm. That's odd."

I used to be a Novell Administrator long ago and in a different life. The later versions of Novell used something call eDirectory which was a database that
kept track of all the objects in the Novell network. Part of having a consistent database is a very precise tracking of time. The Novell database could be distributed across many servers and many geographic regions. Because of this the database had to know the precise time of any event so it could properly update the database with the most current changes.

A time stamp of over 24 hours would not have been allowed in Novell. I was just wondering if Kano might need clues to find out why his program seg-faulted.
It is my job as a concerned member of Kano pool to bring up little things that would not seem to make a difference when bad things are happening with no apparent cause.

Now if the android app is treating 24 = 0, then 24:08:25 could be a valid time stamp. I just never noticed it doing that before which is why I brought it up after kano pool had its issue.

did you not even read the 4-5 posts before yours?

Probably the app not handling KDB restarts.
The web site is correct - KDB puts up the block messages from the pool before it even knows if they're valid blocks
Any share that hashes as a block will also always be shown there if not already shown.

Kano, i had 2 messages today on the app that a new block has been found, but i cant see them on the website specs. Whats with that? Please dont tell its an error message please.... 

The first time ckpool just stopped and dmesg said it segfaulted but alas no core, the others were lock timeouts.
The KDB restarts were both lock timeouts and me restarting it to work around the resource issues by changing things.

I've found recently that ckpool is a CPU hog and I'm pretty sure I know why
(it uses between 2 and 3 times the CPU of KDB but does about the same amount of work)

However, regarding the resource issues, if it happens again in the near future I'll expedite upgrading the main back end server.
It should be enough to handle the load, but this example says otherwise when unexpected things occur.

Of course, no one loses anything, but I guess having to mine for a while on your failover pool can be a let down
(I certainly don't want that to happen to everyone)

Yeah I've seen that too, the ckpool Android app gives 2400 for midnight instead of 0000.  Weird, but nothing to see here I'd guess!

Mine On!  

-EDIT- and you'll get false block alerts, too, after pool restarts... 

I just noticed something a bit odd. The time of the last block found has an hour value of 24 with some minutes and seconds after it. The last I recall there are only 24 hours in a day. Is something a bit wobbley with the ckpook app?

Kano, thanks a lot for fixing this!

Just out of curiosity, do you know why ckpool crashed?
Was the problem somehow related to KDB / resource issue (I though ckpool is totally independent...)?

They are not Bitcoin blocks and not blocks on this pool.

You have been mining altcoins - which this pool does not support in any way whatsoever.

If you are using a rental proxy then they have been pointing your miner at altcoins.

Very high fees on rental proxies make them a bad idea (along will all the other reasons)

Hi, I am New with mining and on May 20 of 2018 antminer s3 has 44 block, what this means and do I going to get pay?
Thanks

And May 21 2018 another 2, no pay, please help me , thanks...

Unfortunately the resource issue continued due to the long KDB reloads as it got further out of sync due ... to each reload failing and thus compounding the issue.

After shutting down a few things that mining can function without and yet again ckpool crashing, KDB finally was able to catch up and all finally OK at 17:05 UTC
One important point to note, however, is that no shares were lost in all this.
As per normal, a KDB restart does scan back to before it was up to when it stopped, then run forward using the reload files and in this case that was all OK other than the original corruption that did not lose any shares - all share sequence numbers were accounted for correctly.

Of course everyone was failed over to their backup pools for quite a while during this, but any shares submitted have been accounted for.

Sorry for the long delay fixing the problems, but finally all is OK again - and of course the web site is back up and all functioning OK again.

I have my 3rd option to mine solo.  Basically on fail over I start lottery mining...lol

Whew...had me goin' there for a bit... 

here all up as well. 

I have all the servers running, and the hashrate is normal,  


Ps.: The site works 

^^^ what he said.  Kano is totally on the case for sure.  Must be a good one whatever it is!


Mine On (when applicable)^tm