Sometimes several of my workers stops being shown their shares at My account stats whilst others shares' number continue to increase in time. Estimated reward also drops.
Looking at workers I notice nothing significant at all - they're producing shares as usual and cgminer marks them as Accepted.
After being restarted cgminer performs as usual but now shares are being counted and I see them in stats.
Looks like there's some instability in counting of shares which were accepted by stratum.
It'd be nice to make some color coding for the "Last share at" field, for instance 0 to 1 minutes make green, up to 10 minutes - orange and more than 10 - red. Just to make quick table reading easier)
Post
Topic
BoardPools
Re: [3000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + Stratum
by
dietwice
on 24/02/2013, 18:48:29 UTC
Looks like "Average hashrate in last 10 rounds" value doesn't change. It shows me the same value for a few days. Not important, just to mention.
Post
Topic
BoardPools
Re: [3000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + Stratum
by
dietwice
on 22/02/2013, 19:48:06 UTC
Is it ok that the block reward calculation is being processed for about 50 minutes till now?
I've just made cgminer 2.10.0 at Raspberry Pi to drive my Cairnsmore CM1. Looks like it performs a bit better than the same version on Win7 at i7-2600K.
I like the debug version of cgminer aimed to collect some info on crash. It doesn't crash
Post
Topic
BoardPools
Re: [2500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + Stratum
by
dietwice
on 29/11/2012, 08:15:56 UTC
I've updated the DaCoinMinster's GreaseMonkey script which tweaks the pool website. It shows some additional stats and also makes workers' status check even more trivial than it is out of the box.
Now it calculates miner's hashrate and some pool averages properly taking in account different block rewards.
Imho it would be great to have a command line switch just to disable GBT and stop worrying about which one of backup pools had accidentally enabled GBT support.
Actually come to think of it, perhaps the results are coming back before the database entry is even being created. Hmm
I connect cgminer to the mining_proxy which itself connects to the Slush's pool. Both connections are via Stratum. This way I get cgminer stable on network outages.
Maybe it is also a reason of getting an extra-fast response by cgminer from the other end of Stratum.
Yes, being a local proxy it responds quickly which is why you can reproduce it. Try 2.8.7 please.
There are lots of messages "Accepted untracked stratum share" among regular "Accepted 68132465..." ones. What do they mean?
p.s. It took about 50 sec to recover normal operations when I switched to another wifi network. And it died when I switched back.
That means the stratum pool you are mining with is returning "accepted" messages without the same ID that cgminer sent the share with, so cgminer doesn't know which shares the pool is accepting. The communication is all done asynchronously and cgminer keeps a database of sent shares so that when it gets a response from the pool it can tell you which share it was.
Actually come to think of it, perhaps the results are coming back before the database entry is even being created. Hmm
I connect cgminer to the mining_proxy which itself connects to the Slush's pool. Both connections are via Stratum. This way I get cgminer stable on network outages.
Maybe it is also a reason of getting an extra-fast response by cgminer from the other end of Stratum.
2.8.4 on Win7 x64 still crashes on network failures.
Being on Wi-Fi it survived switching to another network just by switching to backup pool and then reconnecting to the main one (Slush). But on switching network back it crashed.
Problem signature: Problem Event Name: APPCRASH Application Name: cgminer.exe Application Version: 0.0.0.0 Application Timestamp: 507f309d Fault Module Name: StackHash_0a9e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 6f43203a OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1058 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789