Author

Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 258. (Read 837101 times)

legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
juhakall, a 4/4 difficulty proof being rejected sounds strange.. I'll have a look at it. This was with Stratum?

Yes, that's with stratum.

The target is the exact same you mentioned previously, so the share should be accepted. Do you have the time when this happened? If so I'll have a look at the logs if there are any errors.

Maybe the data is mangled somehow, so when the server hashes it the share doesn't even meet diff 1.
sr. member
Activity: 658
Merit: 250
juhakall, a 4/4 difficulty proof being rejected sounds strange.. I'll have a look at it. This was with Stratum?

Yes, that's with stratum.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
bitcoind and namecoind both slowed down at the same time. There's some sort of issue there. Pool recovered after a couple of minutes though.

juhakall, a 4/4 difficulty proof being rejected sounds strange.. I'll have a look at it. This was with Stratum?
sr. member
Activity: 353
Merit: 251
Website itself is up, but my client can't connect ...
sr. member
Activity: 658
Merit: 250
hero member
Activity: 742
Merit: 500
sr. member
Activity: 658
Merit: 250
I noticed an odd rejected share, using cgminer 2.10.2 & stratum:

Rejected 3fd895f5 Diff 4/4 GPU 1 pool 0 (Work below difficulty)

I only barely understand how share difficulties work, but I was told in #cgminer IRC channel that the target hash for diff4 should be 0x000000003fffc000. My rejected share hash was 0x000000003fd895f5, which is smaller than the target, so shouldn't it be accepted? I'm also aware of the discrepancy between "real" and actually used diff1 shares, which is explained here by kanoi. Could this be a similar problem, meaning that there's a disagreement between cgminer and BitMinter as to what actually is the target for a diff4 share?
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Stratum port 5050 seems to be down. Port 3333 working OK.

It's working for me. It's just a redirect, so 5050 and 3333 should be up/down at the same time.
legendary
Activity: 1036
Merit: 1000
DARKNETMARKETS.COM
Stratum port 5050 seems to be down. Port 3333 working OK.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Need to restart bitcoind and namecoind. They take a while to get up and running again, sorry for the delay..
legendary
Activity: 1274
Merit: 1004
.... although I hope not to see this type of behavior again.

Everyone says this about their child at some point Wink
I think I say this every day for my 2 year old.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Hall of fame is on my list. Smiley

I had eight shifts with zero or near zero scores.

Could be because your miner stayed at a backup pool or that it crashed when it was disconnected by the server. Some miner programs have been having those issues lately.
sr. member
Activity: 476
Merit: 250
So you did something to resume 'normal' / getwork processing?

I had eight shifts with zero or near zero scores.
donator
Activity: 2058
Merit: 1007
Poor impulse control.
.... although I hope not to see this type of behavior again.

Everyone says this about their child at some point Wink
legendary
Activity: 1610
Merit: 1000
Turbor, your explanation is as good as any I can come up with.

Any recent kernel upgrade of the pool? If yes just go back to old one Wink
legendary
Activity: 1036
Merit: 1000
DARKNETMARKETS.COM
DrHaribo, what you think about implementing Hall of Fame (users who found most amount of blocks) like in Slush pool?

http://mining.bitcoin.cz/stats/hall-of-fame/
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Turbor, your explanation is as good as any I can come up with.

Looks like all I/O got slower and slower. After a while some getwork requests took 5 minutes. The database connections terminated with "end of file" and it was impossible to establish new ones. syslog tells me the web server got stuck for over 120 seconds waiting for a page from disk. But there is nothing wrong with the disks. The pool server had several hundred thousand closed connections that somehow the kernel stopped clearing away. The load was 25-30 with almost no cpu usage. Apparently all these processes were waiting on IO. I could still send a request to bitcoind or namecoind and it would register in their logs but no response would come out. After restarting each process everything is fine. It's like the kernel just wouldn't honor IO requests from the "old" processes. I've never seen anything like it.

So yes, maybe it was the ghost in the machine.

I'll be working on robustness and automatic recovery, although I hope not to see this type of behavior again.
legendary
Activity: 1022
Merit: 1000
BitMinter
hero member
Activity: 742
Merit: 500
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Back up again... sorry for the downtime Sad

Not namecoin this time. Something strange going on, will need to investigate further.
Jump to: