xmr-stak and xmrig-proxy compatibility?

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

aij

Active Member
May 7, 2017
101
43
28
I started using xmrig-proxy, and more recently switched from the xmrig docker image to using xmr-stak.

It seemed to work fine, other than xmrig-proxy reporting some duplicate jobs from dwarfpool and occasional batches of rejected shares. (Less than 1%, so annoying, but not a huge deal.)

I ignored it for a week, and today I noticed my overall hash rate on dwarfpool was around 1/2 of what it should have been.


[2018-04-27 06:02:23] 4.00 kH/s, shares: 65972/776 +12, upstreams: 12, miners: 12 (max 16) +0/-0
[2018-04-27 06:03:20] * speed (1m) 2.67, (10m) 6.03, (1h) 5.79, (12h) 5.42, (24h) 3.77 kH/s
[2018-04-27 06:03:23] 3.00 kH/s, shares: 65981/776 +9, upstreams: 12, miners: 12 (max 16) +0/-0
WORKER NAME | LAST IP | COUNT | ACCEPTED | REJ | 10 MINUTES | 24 HOURS |
m1 | 10.0.9.11 | 1 | 752 | 0 | 0.00 kH/s | 0.00 kH/s |
m0 | 10.0.1.10 | 1 | 17257 | 200 | 1.10 kH/s | 0.92 kH/s |
m4 | 192.168.1.23 | 1 | 1602 | 8 | 0.50 kH/s | 0.01 kH/s |
c1n3 | 10.0.1.167 | 1 | 7766 | 101 | 0.77 kH/s | 0.62 kH/s |
c2n3 | 10.0.1.173 | 1 | 5768 | 83 | 0.57 kH/s | 0.35 kH/s |
c1n0 | 10.0.1.163 | 1 | 4178 | 52 | 0.73 kH/s | 0.37 kH/s |
c2n2 | 10.0.1.161 | 1 | 5574 | 18 | 0.60 kH/s | 0.36 kH/s |
c2n0 | 10.0.1.169 | 1 | 5129 | 80 | 0.00 kH/s | 0.05 kH/s |
c1n2 | 10.0.1.165 | 1 | 8071 | 119 | 0.87 kH/s | 0.70 kH/s |
c0n1 | 10.0.1.178 | 1 | 3276 | 29 | 0.00 kH/s | 0.00 kH/s |
c1n1 | 10.0.1.176 | 1 | 2876 | 18 | 0.00 kH/s | 0.05 kH/s |
c2n1 | 10.0.1.171 | 1 | 3739 | 68 | 0.77 kH/s | 0.36 kH/s |​


m1 should be the fastest worker on that list, but it turns out xmrig-proxy was silently rejecting all it's shares for some time, with "Invalid job id". Only 8% of shares had been accepted. m4 had the same issue, and I had just restarted it in the screenshot above, hence the much lower 24h hashrate. (13% success rate)

Now it's happening again, starting at 2018-04-27 11:43:04. I'm not sure if it's a bug in xmrig-proxy or xmr-stak, or just some weird incompatibility. Is anyone else seeing anything similar? (Either with xmrig-proxy + xmr-stak, or some subset thereof.)

This is with the latest versions: xmrix-proxy 2.5.2 and xmr-stak 2.4.2.
 

vudu

Member
Dec 30, 2017
62
22
8
63
May have been the pool. Had some issues with Dwarfpool. Lots of rejects for some hours. Seems to have been fixed.