Topic: Is 100% rejection normal? (Read 2109 times)
its pretty rare to have that kind of rejection... my highest was about 1.3
Hello,
Thanks for the response, but unfortunately it doesn't help at the moment either
The credentials should be good, as I can use the GPU miners with the same credentials I reserved for the CPU only miners. I do have 4 registered workers (2 for GPU miners that work great and 2 for the CPU miners that despite constant computation have all shares rejected; except for the couple I just verified with a GPU miner in a matter of minutes).
I appreciate the suggestion also to try a different client, but I chose cgminer for the CPU mining machine since it appeared to be a reasonable option for them. They are both GNU/Linux servers that don't have graphical displays installed and have some firewall issues not worth discussing here, but in short, GUIs are out of the question. I have also tried poclbm, and while it's much slower than cgminer, it also never had shares accepted. I originally thought that was because the hashing speed was too low, but I stopped thinking that when I saw that cgminer was reporting a higher hash speed than my slowest GPU.
I'm surprised no one has run into this!
The stats of my latest run make me ill:
----------------------------------------------
$ ./cgminer -a 4way -o http://mining.bitcoin.cz:8332 -u USER -p PASS
Summary of runtime statistics:
Started at [2011-08-12 10:51:19]
Runtime: 36 hrs : 36 mins : 24 secs
Average hashrate: 12.7 Megahash/s
Queued work requests: 10475
Share submissions: 382
Accepted shares: 0
Rejected shares: 382
Reject ratio: 100.0
Hardware errors: 0
Efficiency (accepted / queued): 0%
Utility (accepted shares / min): 0.00/min
Discarded work due to new blocks: 10415
Stale submissions discarded due to new blocks: 3
Unable to get work from server occasions: 28
Work items generated locally: 10985
Submitting work remotely delay occasions: 0
New blocks detected on network: 277
Thanks for the response, but unfortunately it doesn't help at the moment either
The credentials should be good, as I can use the GPU miners with the same credentials I reserved for the CPU only miners. I do have 4 registered workers (2 for GPU miners that work great and 2 for the CPU miners that despite constant computation have all shares rejected; except for the couple I just verified with a GPU miner in a matter of minutes).
I appreciate the suggestion also to try a different client, but I chose cgminer for the CPU mining machine since it appeared to be a reasonable option for them. They are both GNU/Linux servers that don't have graphical displays installed and have some firewall issues not worth discussing here, but in short, GUIs are out of the question. I have also tried poclbm, and while it's much slower than cgminer, it also never had shares accepted. I originally thought that was because the hashing speed was too low, but I stopped thinking that when I saw that cgminer was reporting a higher hash speed than my slowest GPU.
I'm surprised no one has run into this!
The stats of my latest run make me ill:
----------------------------------------------
$ ./cgminer -a 4way -o http://mining.bitcoin.cz:8332 -u USER -p PASS
Summary of runtime statistics:
Started at [2011-08-12 10:51:19]
Runtime: 36 hrs : 36 mins : 24 secs
Average hashrate: 12.7 Megahash/s
Queued work requests: 10475
Share submissions: 382
Accepted shares: 0
Rejected shares: 382
Reject ratio: 100.0
Hardware errors: 0
Efficiency (accepted / queued): 0%
Utility (accepted shares / min): 0.00/min
Discarded work due to new blocks: 10415
Stale submissions discarded due to new blocks: 3
Unable to get work from server occasions: 28
Work items generated locally: 10985
Submitting work remotely delay occasions: 0
New blocks detected on network: 277
Shares can be rejected by a pool if you are not submitting with proper worker authentication credentials. Also note that it is best you use a different pool worker login for each miner software instance.
Grab guiminer to start with, and use it's built-in ufasoft miner by picking new->cpu miner. Put your worker info there and mine away. If that works, than it is cgminer, or the way you are using it, that is the problem. Then stop CPU mining unless someone else is paying the electricity bill.
Grab guiminer to start with, and use it's built-in ufasoft miner by picking new->cpu miner. Put your worker info there and mine away. If that works, than it is cgminer, or the way you are using it, that is the problem. Then stop CPU mining unless someone else is paying the electricity bill.
Thanks for the response!
I know ~13 MHash is low, but one of my GPU miners is making steady progress and reporting only ~8 MHash. I'm not trying to compete here, just trying to figure out why this isn't working and looking for any insight on this. If any of the shares were accepted, I wouldn't worry as much about the electricity cost, but since it appears everything is rejected, it looks like a completely fruitless venture. I'd really like to know why though since my non-CPU miners are chugging along properly (albeit slowly as well).
My first guess is that it's some kind of configuration issue with cgminer, but it appears to be working properly and connecting to the right miner site with my proper username/password. I just can't imagine a miner can be computing at that rate for this long and not have a single accepted share, or any indication of what's going wrong.
I know ~13 MHash is low, but one of my GPU miners is making steady progress and reporting only ~8 MHash. I'm not trying to compete here, just trying to figure out why this isn't working and looking for any insight on this. If any of the shares were accepted, I wouldn't worry as much about the electricity cost, but since it appears everything is rejected, it looks like a completely fruitless venture. I'd really like to know why though since my non-CPU miners are chugging along properly (albeit slowly as well).
My first guess is that it's some kind of configuration issue with cgminer, but it appears to be working properly and connecting to the right miner site with my proper username/password. I just can't imagine a miner can be computing at that rate for this long and not have a single accepted share, or any indication of what's going wrong.
I can't comment on the program, but as a general rule you should not have more than 1.5% rejected shares. I rarely get even 1% rejected with my mining setups....... Also, 13mhs is going to cost your way more in electricity than you will ever make from it. CPU mining is not viable my friend. :/
Hello again,
It's a bad feeling thinking that I'm literally just wasting electricity and heating up my computer only to have *everything* rejected using cgminer for CPU only mining. Does anyone out there have any experience using it that is contrary?
Here are my current stats (with an edited username and block id). You can see the A (accepted) column is 0 across the board, and the R (rejected) column is incrementing steadily. Please help!
cgminer version 1.5.3 - Started: [2011-08-12 10:51:19]
--------------------------------------------------------------------------------
[(5s):13.2 (avg):12.9 Mh/s] [Q:6205 A:0 R:231 HW:0 E:0% U:0.00/m]
TQ: 1 ST: 4 LS: 0 SS: 2 DW: 6145 NB: 185 LW: 6443 LO: 21 RF: 0 I: 0
Connected to http://mining.bitcoin.cz:8332 as user MYUSERNAME
Block: 000000e5ff30f0NNNNNNNNNN0c04ef6b... Started: [07:42:15]
--------------------------------------------------------------------------------
[P]ool management [_S]ettings [D]isplay options [Q]uit
CPU 0: [3.5 / 3.2 Mh/s] [Q:1542 A:0 R:47 HW:0 E:0% U:0.00/m]
CPU 1: [3.5 / 3.2 Mh/s] [Q:1440 A:0 R:55 HW:0 E:0% U:0.00/m]
CPU 2: [3.3 / 3.2 Mh/s] [Q:1491 A:0 R:64 HW:0 E:0% U:0.00/m]
CPU 3: [3.2 / 3.2 Mh/s] [Q:1474 A:0 R:65 HW:0 E:0% U:0.00/m]
--------------------------------------------------------------------------------
[2011-08-13 04:45:00] New block detected on network, waiting on fresh work
[2011-08-13 04:46:04] Rejected 6c1dd24b CPU 2 thread 2
[2011-08-13 04:46:28] Rejected 7083ac50 CPU 2 thread 2
[2011-08-13 04:47:27] Rejected 7c401f1e CPU 1 thread 1
[2011-08-13 04:48:18] Rejected 2c473a4e CPU 0 thread 0
[2011-08-13 04:49:59] Rejected 54d8a53d CPU 0 thread 0
[2011-08-13 04:50:06] New block detected on network, waiting on fresh work
[2011-08-13 04:51:07] Rejected dc326b18 CPU 3 thread 3
[2011-08-13 04:57:14] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:59:19] Rejected a4891100 CPU 0 thread 0
[2011-08-13 05:00:51] Rejected 34b59436 CPU 0 thread 0
[2011-08-13 05:01:05] Rejected 4ce6a851 CPU 2 thread 2
[2011-08-13 05:04:41] Rejected bc3c841b CPU 3 thread 3
[2011-08-13 05:09:29] New block detected on network, waiting on fresh work
[2011-08-13 05:10:30] New block detected on network, waiting on fresh work
[2011-08-13 05:11:25] Rejected 4ca96738 CPU 0 thread 0
[2011-08-13 05:12:36] Rejected 00230846 CPU 0 thread 0
[2011-08-13 05:14:36] New block detected on network, waiting on fresh work
[2011-08-13 05:14:37] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 05:22:46] New block detected on network, waiting on fresh work
[2011-08-13 05:27:53] New block detected on network, waiting on fresh work
[2011-08-13 05:28:55] New block detected on network, waiting on fresh work
[2011-08-13 05:32:16] Rejected 00612249 CPU 1 thread 1
[2011-08-13 05:37:36] Rejected e8c02c4e CPU 3 thread 3
[2011-08-13 05:38:50] Rejected a4a27808 CPU 1 thread 1
[2011-08-13 05:39:40] Rejected 04474b06 CPU 2 thread 2
[2011-08-13 05:41:08] New block detected on network, waiting on fresh work
[2011-08-13 05:42:20] Rejected 28460d4a CPU 2 thread 2
[2011-08-13 05:46:22] Rejected 04590948 CPU 1 thread 1
[2011-08-13 05:47:21] Rejected 3cfa1019 CPU 2 thread 2
[2011-08-13 05:52:22] New block detected on network, waiting on fresh work
[2011-08-13 05:52:22] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 05:56:38] Rejected 940dd332 CPU 0 thread 0
[2011-08-13 06:01:45] Rejected 741f3933 CPU 2 thread 2
[2011-08-13 06:02:45] Rejected ccdc6a4b CPU 3 thread 3
[2011-08-13 06:03:47] Rejected 8cc6a74b CPU 3 thread 3
[2011-08-13 06:11:42] New block detected on network, waiting on fresh work
[2011-08-13 06:13:10] Rejected 94ace435 CPU 0 thread 0
[2011-08-13 06:18:50] New block detected on network, waiting on fresh work
[2011-08-13 06:18:51] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 06:23:43] Rejected f441eb39 CPU 2 thread 2
[2011-08-13 06:35:07] New block detected on network, waiting on fresh work
[2011-08-13 06:36:02] Rejected 7cba7f22 CPU 3 thread 3
[2011-08-13 06:55:34] Rejected 5c0e6719 CPU 2 thread 2
[2011-08-13 07:22:55] Rejected acf99a58 CPU 3 thread 3
[2011-08-13 07:30:03] Stale share detected, discarding
[2011-08-13 07:32:30] Rejected 74482d38 CPU 2 thread 2
[2011-08-13 07:37:51] Rejected 140e813b CPU 3 thread 3
[2011-08-13 07:42:15] New block detected on network, waiting on fresh work
[2011-08-13 07:43:54] Rejected dcfbf21d CPU 1 thread 1
[2011-08-13 07:44:13] Rejected 34943d3a CPU 2 thread 2
[2011-08-13 07:53:37] Rejected 680e394b CPU 2 thread 2
[2011-08-13 07:55:17] Rejected 1ca52e22 CPU 0 thread 0
[2011-08-13 08:02:31] Rejected 6c7c2452 CPU 2 thread 2
[2011-08-13 08:05:30] Rejected 5cf3b720 CPU 1 thread 1
[2011-08-13 08:06:37] Rejected 0c2ee453 CPU 0 thread 0
[2011-08-13 08:17:21] Rejected a4c51702 CPU 2 thread 2
It's a bad feeling thinking that I'm literally just wasting electricity and heating up my computer only to have *everything* rejected using cgminer for CPU only mining. Does anyone out there have any experience using it that is contrary?
Here are my current stats (with an edited username and block id). You can see the A (accepted) column is 0 across the board, and the R (rejected) column is incrementing steadily. Please help!
cgminer version 1.5.3 - Started: [2011-08-12 10:51:19]
--------------------------------------------------------------------------------
[(5s):13.2 (avg):12.9 Mh/s] [Q:6205 A:0 R:231 HW:0 E:0% U:0.00/m]
TQ: 1 ST: 4 LS: 0 SS: 2 DW: 6145 NB: 185 LW: 6443 LO: 21 RF: 0 I: 0
Connected to http://mining.bitcoin.cz:8332 as user MYUSERNAME
Block: 000000e5ff30f0NNNNNNNNNN0c04ef6b... Started: [07:42:15]
--------------------------------------------------------------------------------
[P]ool management [_S]ettings [D]isplay options [Q]uit
CPU 0: [3.5 / 3.2 Mh/s] [Q:1542 A:0 R:47 HW:0 E:0% U:0.00/m]
CPU 1: [3.5 / 3.2 Mh/s] [Q:1440 A:0 R:55 HW:0 E:0% U:0.00/m]
CPU 2: [3.3 / 3.2 Mh/s] [Q:1491 A:0 R:64 HW:0 E:0% U:0.00/m]
CPU 3: [3.2 / 3.2 Mh/s] [Q:1474 A:0 R:65 HW:0 E:0% U:0.00/m]
--------------------------------------------------------------------------------
[2011-08-13 04:45:00] New block detected on network, waiting on fresh work
[2011-08-13 04:46:04] Rejected 6c1dd24b CPU 2 thread 2
[2011-08-13 04:46:28] Rejected 7083ac50 CPU 2 thread 2
[2011-08-13 04:47:27] Rejected 7c401f1e CPU 1 thread 1
[2011-08-13 04:48:18] Rejected 2c473a4e CPU 0 thread 0
[2011-08-13 04:49:59] Rejected 54d8a53d CPU 0 thread 0
[2011-08-13 04:50:06] New block detected on network, waiting on fresh work
[2011-08-13 04:51:07] Rejected dc326b18 CPU 3 thread 3
[2011-08-13 04:57:14] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:57:15] New block detected on network, waiting on fresh work
[2011-08-13 04:59:19] Rejected a4891100 CPU 0 thread 0
[2011-08-13 05:00:51] Rejected 34b59436 CPU 0 thread 0
[2011-08-13 05:01:05] Rejected 4ce6a851 CPU 2 thread 2
[2011-08-13 05:04:41] Rejected bc3c841b CPU 3 thread 3
[2011-08-13 05:09:29] New block detected on network, waiting on fresh work
[2011-08-13 05:10:30] New block detected on network, waiting on fresh work
[2011-08-13 05:11:25] Rejected 4ca96738 CPU 0 thread 0
[2011-08-13 05:12:36] Rejected 00230846 CPU 0 thread 0
[2011-08-13 05:14:36] New block detected on network, waiting on fresh work
[2011-08-13 05:14:37] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 05:22:46] New block detected on network, waiting on fresh work
[2011-08-13 05:27:53] New block detected on network, waiting on fresh work
[2011-08-13 05:28:55] New block detected on network, waiting on fresh work
[2011-08-13 05:32:16] Rejected 00612249 CPU 1 thread 1
[2011-08-13 05:37:36] Rejected e8c02c4e CPU 3 thread 3
[2011-08-13 05:38:50] Rejected a4a27808 CPU 1 thread 1
[2011-08-13 05:39:40] Rejected 04474b06 CPU 2 thread 2
[2011-08-13 05:41:08] New block detected on network, waiting on fresh work
[2011-08-13 05:42:20] Rejected 28460d4a CPU 2 thread 2
[2011-08-13 05:46:22] Rejected 04590948 CPU 1 thread 1
[2011-08-13 05:47:21] Rejected 3cfa1019 CPU 2 thread 2
[2011-08-13 05:52:22] New block detected on network, waiting on fresh work
[2011-08-13 05:52:22] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 05:56:38] Rejected 940dd332 CPU 0 thread 0
[2011-08-13 06:01:45] Rejected 741f3933 CPU 2 thread 2
[2011-08-13 06:02:45] Rejected ccdc6a4b CPU 3 thread 3
[2011-08-13 06:03:47] Rejected 8cc6a74b CPU 3 thread 3
[2011-08-13 06:11:42] New block detected on network, waiting on fresh work
[2011-08-13 06:13:10] Rejected 94ace435 CPU 0 thread 0
[2011-08-13 06:18:50] New block detected on network, waiting on fresh work
[2011-08-13 06:18:51] Pool 0 http://mining.bitcoin.cz:8332 not responding!
[2011-08-13 06:23:43] Rejected f441eb39 CPU 2 thread 2
[2011-08-13 06:35:07] New block detected on network, waiting on fresh work
[2011-08-13 06:36:02] Rejected 7cba7f22 CPU 3 thread 3
[2011-08-13 06:55:34] Rejected 5c0e6719 CPU 2 thread 2
[2011-08-13 07:22:55] Rejected acf99a58 CPU 3 thread 3
[2011-08-13 07:30:03] Stale share detected, discarding
[2011-08-13 07:32:30] Rejected 74482d38 CPU 2 thread 2
[2011-08-13 07:37:51] Rejected 140e813b CPU 3 thread 3
[2011-08-13 07:42:15] New block detected on network, waiting on fresh work
[2011-08-13 07:43:54] Rejected dcfbf21d CPU 1 thread 1
[2011-08-13 07:44:13] Rejected 34943d3a CPU 2 thread 2
[2011-08-13 07:53:37] Rejected 680e394b CPU 2 thread 2
[2011-08-13 07:55:17] Rejected 1ca52e22 CPU 0 thread 0
[2011-08-13 08:02:31] Rejected 6c7c2452 CPU 2 thread 2
[2011-08-13 08:05:30] Rejected 5cf3b720 CPU 1 thread 1
[2011-08-13 08:06:37] Rejected 0c2ee453 CPU 0 thread 0
[2011-08-13 08:17:21] Rejected a4c51702 CPU 2 thread 2
Hello,
I'm new here and can't seem to find the answer to this, so I wanted to ask out right.
I have two machines with GPUs that are chugging along making some progress in the pooled mining over at bitcoin.cz. I have two other machines that do NOT have GPUs and I just got cgminer installed on them since it can do CPU-only mining. The problem is that I've been running them for days, and each day I check the stats. Typically, they look like this:
------------------------------------------------
$ ./cgminer -a 4way -o http://api2.bitcoin.cz:8332 -u USERNAME -p PASSWORD
Summary of runtime statistics:
Started at [2011-08-11 11:08:37]
Runtime: 13 hrs : 31 mins : 20 secs
Average hashrate: 13.0 Megahash/s
Queued work requests: 3516
Share submissions: 173
Accepted shares: 0
Rejected shares: 173
Reject ratio: 100.0
Hardware errors: 0
Efficiency (accepted / queued): 0%
Utility (accepted shares / min): 0.00/min
Discarded work due to new blocks: 3261
Stale submissions discarded due to new blocks: 1
Unable to get work from server occasions: 0
Work items generated locally: 5591
Submitting work remotely delay occasions: 0
New blocks detected on network: 95
Summary of per device statistics:
CPU 0: [3.0 / 3.2 Mh/s] [Q:830 A:0 R:34 HW:0 E:0% U:0.00/m]
CPU 1: [3.0 / 3.3 Mh/s] [Q:786 A:0 R:39 HW:0 E:0% U:0.00/m]
CPU 2: [2.8 / 3.3 Mh/s] [Q:936 A:0 R:47 HW:0 E:0% U:0.00/m]
CPU 3: [3.0 / 3.3 Mh/s] [Q:826 A:0 R:53 HW:0 E:0% U:0.00/m]
------------------------------------------------
I realize the computation rate is very slow compared to a GPU, but I'm wondering if something is wrong with the setup. One of my GPU machines has an old GPU (ATI RV710) that computes at only ~8 MHash, so compared to that, this 13 MHash rate shouldn't be totally worthless. Except everything is rejected by both of my CPU miners 100% of the time, and even the slow GPU miner is getting acceptable rates (e.g. ~2500 accepted, ~20 stale/invalid).
Any information here is appreciated, thanks!
I'm new here and can't seem to find the answer to this, so I wanted to ask out right.
I have two machines with GPUs that are chugging along making some progress in the pooled mining over at bitcoin.cz. I have two other machines that do NOT have GPUs and I just got cgminer installed on them since it can do CPU-only mining. The problem is that I've been running them for days, and each day I check the stats. Typically, they look like this:
------------------------------------------------
$ ./cgminer -a 4way -o http://api2.bitcoin.cz:8332 -u USERNAME -p PASSWORD
Summary of runtime statistics:
Started at [2011-08-11 11:08:37]
Runtime: 13 hrs : 31 mins : 20 secs
Average hashrate: 13.0 Megahash/s
Queued work requests: 3516
Share submissions: 173
Accepted shares: 0
Rejected shares: 173
Reject ratio: 100.0
Hardware errors: 0
Efficiency (accepted / queued): 0%
Utility (accepted shares / min): 0.00/min
Discarded work due to new blocks: 3261
Stale submissions discarded due to new blocks: 1
Unable to get work from server occasions: 0
Work items generated locally: 5591
Submitting work remotely delay occasions: 0
New blocks detected on network: 95
Summary of per device statistics:
CPU 0: [3.0 / 3.2 Mh/s] [Q:830 A:0 R:34 HW:0 E:0% U:0.00/m]
CPU 1: [3.0 / 3.3 Mh/s] [Q:786 A:0 R:39 HW:0 E:0% U:0.00/m]
CPU 2: [2.8 / 3.3 Mh/s] [Q:936 A:0 R:47 HW:0 E:0% U:0.00/m]
CPU 3: [3.0 / 3.3 Mh/s] [Q:826 A:0 R:53 HW:0 E:0% U:0.00/m]
------------------------------------------------
I realize the computation rate is very slow compared to a GPU, but I'm wondering if something is wrong with the setup. One of my GPU machines has an old GPU (ATI RV710) that computes at only ~8 MHash, so compared to that, this 13 MHash rate shouldn't be totally worthless. Except everything is rejected by both of my CPU miners 100% of the time, and even the slow GPU miner is getting acceptable rates (e.g. ~2500 accepted, ~20 stale/invalid).
Any information here is appreciated, thanks!
Jump to: