20% rejects with Zeus Thunder X3 and bfgminer

[edonkey]

First time mining on this pool. I'm seeing lots of rejects, so my profitability estimates are not being met.

I've read the help section and changed my scan time to 1, but that didn't help. Here's my command line:

/var/www/minera/minera-bin/bfgminer --scrypt -S zus:all --set zus:chips=128 --set zus:clock=332 --scan-time=1 -c /var/www/minera/conf/miner_conf.json

The conf file just defines the pools and JSON API stuff. No other commands are in there.

The version of bfgminer is 5.2.0-2-ga488b3f. I recently built it as part of a fresh minera installation.

Any ideas?

[Steve Sokolowski]

kires, are you there?

I remember that there was a catch with using bfgminer and people had better results with cgminer. You can try that, but I still want to figure out what your exact problem is.

I want to review the database to see the cause of your rejected shares. I'll assume that your username is the same as on the forums? I'll look into this during the evening and get back to you soon.

[edonkey]

kires, are you there?

I remember that there was a catch with using bfgminer and people had better results with cgminer. You can try that, but I still want to figure out what your exact problem is.

I want to review the database to see the cause of your rejected shares. I'll assume that your username is the same as on the forums? I'll look into this during the evening and get back to you soon.

Thanks for the follow up Steve.

My user name is different. I'll PM it to you.

[edonkey]

Looks like the system won't let me send a PM.

Maybe I should just use the "Contact Us" link to send the information to an administrator?

[Steve Sokolowski]

I changed the private message settings. Are your messages still rejected? What error message do you get?

For now, you can send your username to the contact address, or text it to the phone number if that's simpler.

[edonkey]

Minera is still reporting a high number of rejects (15.7%). Nothing obvious is jumping out in the log, but here are a few snippets:

Code: Select all

 [2015-08-28 06:22:29] Accepted 0002dec7 ZUS 0bjy pool 0 Diff 348m/125m 
 [2015-08-28 06:22:31] 20s:23.17 avg:21.54 u:22.60 Mh/s | A:7067 R:1416+122(6.4%) HW:545/5.8%
 [2015-08-28 06:22:31] Network difficulty changed to 6 (48.92M)
 [2015-08-28 06:22:31] New block: ...7518942b9b6ff257 diff 6 (48.92M)
 [2015-08-28 06:22:31] Stratum from pool 0 detected new block
 [2015-08-28 06:22:35] Network difficulty changed to 3 (27.49M)
 [2015-08-28 06:22:35] New block: ...bf0f0587e0853c78 diff 3 (27.49M)
 [2015-08-28 06:22:35] Stratum from pool 0 detected new block
 [2015-08-28 06:22:36] Network difficulty changed to 6 (48.91M)
 [2015-08-28 06:22:36] New block: ...43a664780ba5b624 diff 6 (48.91M)
 [2015-08-28 06:22:36] Stratum from pool 0 detected new block
 [2015-08-28 06:22:39] Accepted 0002de89 ZUS 0aae pool 0 Diff 348m/125m 
 [2015-08-28 06:22:40] Pool 0 is issuing work for an old block: c91cf6773a29eceffcd2baf9d4efc6daf19d1d46987eb019bf0f0587e0853c78
 [2015-08-28 06:22:41] Network difficulty changed to 6 (48.94M)
 [2015-08-28 06:22:41] New block: ...2ea376adcc189e0c diff 6 (48.94M)
 [2015-08-28 06:22:41] Pool 0 is issuing work for an old block: c91cf6773a29eceffcd2baf9d4efc6daf19d1d46987eb019bf0f0587e0853c78
 [2015-08-28 06:22:41] Stratum from pool 0 detected new block
 [2015-08-28 06:22:41] Pool 0 caught up to new block
 [2015-08-28 06:22:44] Network difficulty changed to 3 (27.56M)
 [2015-08-28 06:22:44] New block: ...45bfa094e6bd996b diff 3 (27.56M)

The bottom line is that I'm not seeing anywhere near the profitability promised by this pool. My Zeus Thunder usually runs at between 26 and 28 MH/s on straight litecoin pools. It was pointed at prohashing all day yesterday and earned $0.73. When divided by the advertised profitability of $0.063 per day, the pool is only paying me for the equivalent of 11.6 MH/s per day.

I don't know what's wrong, but I'm certain that I can do much better elsewhere.

[Steve Sokolowski]

I'm looking into this right now. There is something odd with the rejects for your miners that isn't present for other miners. You may have actually triggered a bug in the system and helped us fix something that's been around for a while.

[Steve Sokolowski]

I looked into this problem.

The reason for the rejects in all cases was the the shares were stale. There wasn't any more information in the database that would explain why so many of your shares were stale compared to everyone else's. It's almost as if the mining software is not handling new jobs correctly.

Is it possible for you to try this with cgminer? That way, we can determine whether it's your miners or whether bfgminer is at fault.

[CptPajamas]

I realize this is an old problem, but I do not see if it was resolved or not.

I was thinking of trying Minera as well as a distribution for controllers, but with the problems I've faced recently I was able to track them back down to the version of BFGMiner I was using and using a static difficulty and restart time (d=2048 r=0.35 as password arguments).

If the version of BFGMiner is 5.2 or lower, see if you can update it to 5.4.

Perhaps those might help in this particular situation

[loszhor]

First time mining on this pool. I'm seeing lots of rejects, so my profitability estimates are not being met.

I've read the help section and changed my scan time to 1, but that didn't help. Here's my command line:

/var/www/minera/minera-bin/bfgminer --scrypt -S zus:all --set zus:chips=128 --set zus:clock=332 --scan-time=1 -c /var/www/minera/conf/miner_conf.json

The conf file just defines the pools and JSON API stuff. No other commands are in there.

The version of bfgminer is 5.2.0-2-ga488b3f. I recently built it as part of a fresh minera installation.

Any ideas?

This topic appears to be old but an important issue can be possibly resolved resolved from it. In your command line you should set scan-time to 1, expiry to 1, and queue to 0.

Reasons:

Rejects usually happen when the block/share has become stale, as in it has become obsolete by the time it was submitted, and if you are getting many rejected shares and/or blocks it might be that your connection to the pool is not as desirable as it could be.

Setting scan-time and expiry to 1 will ensure that you do not work a share too long and setting queue to 0 will make sure that your work is always up to date and will greatly reduce the risk of stale work.

Let me know if this helps.