Tons of expired shares with XMR Stak (minexmr.com)

[siggiboyminer]

Hello, I am just wondering if anyone can help. I have been mining Monero at minexmr.com with both Claymore and XMR Stak AMD. I seem to get fairly identical results, but I use 100 Watt less with XMR Stak AMD, so I kind of prefer that. But, for some reason I get an enormous amount of expired shares with XMR Stak AMD. In the last ten hours I have gotten around 400,000 expired shares.

I have a hashrate of around 3 KH/s.

Ps: With claymore I did not get any expired shares at all.

[psychocrypt]

do you see the expired shares soon after the start or very late if the miner is running over 12h?

Am 16.09.2017 23:03 schrieb "siggiboyminer" notifications@github.com:

Hello, I am just wondering if anyone can help. I have been mining Monero at minexmr.com with both Claymore and XMR Stak AMD. I seem to get fairly identical results, but I use 100 Watt less with XMR Stak AMD, so I kind of prefer that. But, for some reason I get an enormous amount of expired shares with XMR Stak AMD. In the last ten hours I have gotten around 400,000 expired shares.

I have a hashrate of around 3 KH/s.

Ps: With claymore I did not get any expired shares at all.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fireice-uk/xmr-stak-amd/issues/106, or mute the thread https://github.com/notifications/unsubscribe-auth/AYsxttTXnM0SlyMQ206J-BwudivfzL8Iks5sjDexgaJpZM4PZ8ra .

[anhphan]

The counting is wrong (double counting), so you only have half of that number expired shareds. #105 I also have high expired shares (4-6 % in result page) on nanopool. I use binary from release but opencl file from dev brand.

[siggiboyminer]

The errors start coming after about two hours of mining... Currently I have 963617671 accepted shares and 17901422 expired shares.

[kisow]

Expired Shares: These are shares which were submitted too late for the current block. It is normal for this to be less than 1% of your accepted shares.

it's above normal. your expired share rate is 1.85% greater than 1%. mine is 3.3%. (6.07 KH/s | 107340624 | 3556870).

[psychocrypt]

Please provide me with a log of a session with the hight expired rate. I will check how often the pool provide the miner with a new block.

Am 03.10.2017 18:24 schrieb "Jaehoon Kim" notifications@github.com:

Expired Shares: These are shares which were submitted too late for the current block. It is normal for this to be less than 1% of your accepted shares.

it's above normal. your expired share rate is 1.85% greater than 1%. mine is 3.3%. (6.07 KH/s | 107340624 | 3556870).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/fireice-uk/xmr-stak-amd/issues/106#issuecomment-333896038, or mute the thread https://github.com/notifications/unsubscribe-auth/AYsxtj2pCPtVi7lO-8pdDLKtI89oAbnkks5sol_AgaJpZM4PZ8ra .

[kisow]

I'm using window version of xmr-stak-amd because linux version does not work. look at that. there are a lot of Result rejected by the pool. By the way, there is no invalid shares in pool's stats. It seems that these are only expired shares.

[2017-10-04 01:40:42] : Result accepted by the pool.
[2017-10-04 01:41:00] : Result accepted by the pool.
[2017-10-04 01:41:07] : New block detected.
[2017-10-04 01:41:16] : Result accepted by the pool.
[2017-10-04 01:41:17] : Result accepted by the pool.
[2017-10-04 01:41:29] : Result accepted by the pool.
[2017-10-04 01:41:31] : Result accepted by the pool.
[2017-10-04 01:41:48] : Result accepted by the pool.
[2017-10-04 01:43:36] : Result accepted by the pool.
[2017-10-04 01:43:48] : New block detected.
[2017-10-04 01:43:51] : Result accepted by the pool.
[2017-10-04 01:44:10] : Result accepted by the pool.
[2017-10-04 01:44:10] : Result accepted by the pool.
[2017-10-04 01:44:22] : Result accepted by the pool.
[2017-10-04 01:45:01] : New block detected.
[2017-10-04 01:52:03] : Result rejected by the pool.
[2017-10-04 01:52:03] : Result rejected by the pool.
[2017-10-04 01:52:03] : Result rejected by the pool.
[2017-10-04 01:52:04] : Result rejected by the pool.
[2017-10-04 01:52:04] : Result rejected by the pool.
[2017-10-04 01:52:05] : Result rejected by the pool.
[2017-10-04 01:52:05] : Result rejected by the pool.
[2017-10-04 01:52:05] : New block detected.
[2017-10-04 01:52:05] : Result rejected by the pool.
[2017-10-04 01:52:06] : Result rejected by the pool.
[2017-10-04 01:52:06] : Result rejected by the pool.
[2017-10-04 01:52:07] : New block detected.
[2017-10-04 01:52:09] : New block detected.
[2017-10-04 01:52:10] : Result rejected by the pool.
[2017-10-04 01:52:10] : Result rejected by the pool.
[2017-10-04 01:52:11] : New block detected.
[2017-10-04 01:52:12] : Result rejected by the pool.
[2017-10-04 01:52:13] : New block detected.
[2017-10-04 01:52:14] : Result rejected by the pool.
[2017-10-04 01:52:14] : Result rejected by the pool.
[2017-10-04 01:52:14] : Result rejected by the pool.
[2017-10-04 01:52:15] : New block detected.
[2017-10-04 01:52:16] : Result rejected by the pool.
[2017-10-04 01:52:16] : Result rejected by the pool.
[2017-10-04 01:52:17] : Result rejected by the pool.
[2017-10-04 01:52:18] : Result accepted by the pool.
[2017-10-04 01:52:22] : Result accepted by the pool.
[2017-10-04 01:52:23] : Result accepted by the pool.
[2017-10-04 01:52:24] : Result accepted by the pool.
[2017-10-04 01:52:32] : Result accepted by the pool.

[psychocrypt]

Which OS and Pool. Have you changed something in the code?

Am 03.10.2017 7:02 Nachm. schrieb "Jaehoon Kim" notifications@github.com:

I'm using window version of xmr-stak-amd because linux version does not work. look at that. there are a lot of Result rejected by the pool. By the way, there is no invalid shares in pool's stats. It seems that these are only expired shares.

[2017-10-04 01:40:42] : Result accepted by the pool. [2017-10-04 01:41:00] : Result accepted by the pool. [2017-10-04 01:41:07] : New block detected. [2017-10-04 01:41:16] : Result accepted by the pool. [2017-10-04 01:41:17] : Result accepted by the pool. [2017-10-04 01:41:29] : Result accepted by the pool. [2017-10-04 01:41:31] : Result accepted by the pool. [2017-10-04 01:41:48] : Result accepted by the pool. [2017-10-04 01:43:36] : Result accepted by the pool. [2017-10-04 01:43:48] : New block detected. [2017-10-04 01:43:51] : Result accepted by the pool. [2017-10-04 01:44:10] : Result accepted by the pool. [2017-10-04 01:44:10] : Result accepted by the pool. [2017-10-04 01:44:22] : Result accepted by the pool. [2017-10-04 01:45:01] : New block detected. [2017-10-04 01:52:03] : Result rejected by the pool. [2017-10-04 01:52:03] : Result rejected by the pool. [2017-10-04 01:52:03] : Result rejected by the pool. [2017-10-04 01:52:04] : Result rejected by the pool. [2017-10-04 01:52:04] : Result rejected by the pool. [2017-10-04 01:52:05] : Result rejected by the pool. [2017-10-04 01:52:05] : Result rejected by the pool. [2017-10-04 01:52:05] : New block detected. [2017-10-04 01:52:05] : Result rejected by the pool. [2017-10-04 01:52:06] : Result rejected by the pool. [2017-10-04 01:52:06] : Result rejected by the pool. [2017-10-04 01:52:07] : New block detected. [2017-10-04 01:52:09] : New block detected. [2017-10-04 01:52:10] : Result rejected by the pool. [2017-10-04 01:52:10] : Result rejected by the pool. [2017-10-04 01:52:11] : New block detected. [2017-10-04 01:52:12] : Result rejected by the pool. [2017-10-04 01:52:13] : New block detected. [2017-10-04 01:52:14] : Result rejected by the pool. [2017-10-04 01:52:14] : Result rejected by the pool. [2017-10-04 01:52:14] : Result rejected by the pool. [2017-10-04 01:52:15] : New block detected. [2017-10-04 01:52:16] : Result rejected by the pool. [2017-10-04 01:52:16] : Result rejected by the pool. [2017-10-04 01:52:17] : Result rejected by the pool. [2017-10-04 01:52:18] : Result accepted by the pool. [2017-10-04 01:52:22] : Result accepted by the pool. [2017-10-04 01:52:23] : Result accepted by the pool. [2017-10-04 01:52:24] : Result accepted by the pool. [2017-10-04 01:52:32] : Result accepted by the pool.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/fireice-uk/xmr-stak-amd/issues/106#issuecomment-333911168, or mute the thread https://github.com/notifications/unsubscribe-auth/AYsxtq1aLL6Af6W23EnIOCygCEYIqZSDks5somiLgaJpZM4PZ8ra .

[kisow]

I'm just use or build, and this issue is not for only xmr-stak-amd, but also xmr-stak-nvidia too. For your information, I will write down the combination that I'm using.

• Pool : http://minexmr.com/

hashrate	accepted shares	expired shares	invalid shares	mining tool	OS	build
3.50 KH/s	242720624	6496870	0	xmr-stak-amd	win10	binary release
466.67 H/s	38957938	1288441	0	xmr-stak-nvidia	arch linux	source compile with gcc-5.4 + cuda 8.0
150.00 H/s	10528666	0	0	xmr-stak-cpu	arch linux	source compile with gcc-7? may be

[buybuypc]

I usually got 3.8% of bad results after few fours on win10 & xmr-stak-amd (1800H) binary release. but I got 0% bad results everyday on win2012 & xmr-stak-cpu(210H) binary release. the pool is nano.

[rafise]

I'm having the same errors result rejected by the pool any know how to fix the errors? Thanks

[buybuypc]

just replace the pool with supportxmr, but its mining performance seems to be lower than nano... and below is the table, compare to the withdraw fee to local wallet address

nano withdraw 0.3XMR=0.292711433964 XMR supportxmr withdraw 0.3XMR=0.2996895903 XMR dwarf withdraw 0.24876992XMR=0.248769919999 XMR

[nhbn]

I'd like to chime in.

I also have/had to struggle with expired shares using xmr-stak on minexmr.com. Hardware is 12x GTX 1050ti on Xubuntu 17.04. I had a fresh install as described in docs linux compile guide. All good. Straight forward. With these settings for all GPU, I get stable 312-314 on each card.

  { "index" : 0,
    "threads" : 48, "blocks" : 18,
    "bfactor" : 8, "bsleep" :  100,
    "affine_to_cpu" : false, "sync_mode" : 3,
  }

Using the autoconfig resulted in uneven performance across cards (spreading up to 25H/s from 290-315). I could achieve slightly higher values with other settings, but this provided the highest sum with equal card performance (but different topic).

Autoconfig was:

  { "index" : 0,
    "threads" : 56, "blocks" : 18,
    "bfactor" : 2, "bsleep" :  0,
    "affine_to_cpu" : false, "sync_mode" : 3,
  },

I also observed that 4-6 of the 12 GPU have lower hashrates in many different configurations (usually the latter cards). All cards are the same brand and modell (MSI GTX 1050ti Aero ITX 4GB).

Anyway. As I increased the number of GPU in my rig, expired shares in total have risen (naturally). But also their share. I realized this yesterday evening when I completed my rig with 5 more cards (going from 7 to 12 gpu). Going around 10%, sometimes more sometimes less. This morning I played around with the settings of xmr-stak again. Installed and compiled system and miner from scratch. Checked for local network conflicts. Ping time from XMR-Stak to the pool is around 50ms. However, the same machine is reporting ~30ms when ping from regular console.

The 30ms is also what I get when I ping it from different computers in my home network. I am connected to the internet with 50MBit VDSL, usually a very reliable connection.

I also tried different difficulties and ports as well as hostnames of the pool, but the problem stayed the same. I had the impression, then when I was using softer settings (e.g. yielding 290H/s) I had a lower share of expired shares.

Then I switched pool to nanopool. Either I have tomatoes on my eyes or I am too stupid to find expired shared. However hashrates reported from nanopool seemed pretty spot on to what I have locally after one hour.

I switched back to minexmr.com an hour ago and for the recent time it is sailing pretty smooth with very little expired shares and their share dropping (though I didn't change someting).

So, at the end I am none then wiser (though I learned a few things as a novice). And it may be a temporary problem of the pool.

My beginners observation is, that this may have something to do with the network/connection.

And I am not sure this is actually an issue of xmr-stak (except for the 20ms offset in pingtime reporting). Since the 20ms offset seems persistent but I observe varying levels of expired shares, it could also be something between my internet access and the servers of the pool.

I hope this helps in narrowing down potential reasons. If I can provide info or test certain settings. Let me know what you need.

[buybuypc]

forgot xmr-stak-xxx, throw it to the trash can. and use others instead. you will be happy.

[redestones]

I have noticed a very large loss of shares sent and my balance when I started on minexmr.com had a promise of 0.01 xmr per day for a power of 1000h / s or 1k h / s now the promise is only 0.004 for every 1k h /s..in my mining log claymore or xmrstak> does not show any invalid or expired share, plus my hashrate is 1030 h / seo site shows most of the time 670 h / s my conclusion is that minexmr.com is receiving lots of moneros and not going over to the miners ... we are looking for a better pool .minexmr.com seems to be passing me by, and I do not like to waste time with boys trying to be experts.

[arnalph]

I too am using XMR Stak. With MineXMR, 2.87% of my shares go invalid. Is there a way to reduce that or do I have to change my software?

[psychocrypt]

Please post the exact error message. There is a difference between invalid and outdated shares. Press the key 'r' and post the log.