betarigs pool gets ignored when a new rental is latched onto its stratum

[platinum4]

Not sure if this is a service issue or a pool-priority respect issue, but I've noticed within the last week, without fail, if a rental goes through on betarigs, sgminer5 fails to walk back up the pool-priority chain and acknowledge that the pool is alive and has work being [ready to be] served. Upon sgminer5 restart, it immediately hits the pool with no problems and starts hashing as it should, and I'm not particularly worried about where or which pool down the chain it goes afterward; just want people to quit bitching at me and my inbox as if I'm robbing them of precious non-profit mining minutes. My config file is found here: https://bitcointalk.org/index.php?topic=632503.msg7680589#msg7680589

This is an issue valid for builds AFTER July 2nd, 2014, which ystarnaud's [3rd] test build of that day has been working flawlessly. This may be pre-jansson push, not sure.

[mrbrdo]

small chance but https://github.com/sgminer-dev/sgminer/issues/328 could also be related

[ystarnaud]

Are you sure it's being ignored? How much time do you give it? With miningrigrentals I noticed a good 2 minutes before the pool itself would register that my rig got rented and finally show up alive in sgminer (that is actually let me login to stratum). After that sgminer would test the pool for stability for a good minute or two before finally switching.

The whole process can take a good 5 minutes depending on how quickly the pool lets you in. For MRR anyway... And I suspect that stratum doesn't become active until the renter enters his target pool information.

[platinum4]

@ystarnaud it was a full 20 minutes this time before rig renter started shitting on my inbox. I've seen it take up to an hour over the weekend. Once manually restarted, it snaps right to br stratum, so I know the work has been served for up to or at least the whole time. I'm completely with you on the 2-5-10 minutes even, that it may take for rental stratums to hook up; but 20-60 minutes on an alive pool confirmed working, seems to be some sort of d/c between stratum and sgminer5 until the instance is restarted.

[mrbrdo]

CGWatcher logs don't tell much, it would be much better to have actual sgminer logs. Is it possible to tell CGWatcher (I don't use it) to start sgminer like this sgminer -c ... 2> debug.log, so to append 2> debug.log at the end? This will make a full debug log file but will not otherwise impact how sgminer works.

[mrbrdo]

I just merged --log-file option from bfgminer, now you just need to add it to config, I guess that should be possible with CGWatcher. Docs: https://github.com/sgminer-dev/sgminer/blob/v5_0/doc/configuration.md#log-file

[platinum4]

@mrbrdo I have a new nightly build from @kenshirothefist, so I will test this in practice (with "logfile") and report back to see if the issue is replicated; if so, will post a log; else, may be a non-issue squashed by a few of the latest commits.

[mrbrdo]

thanks!

[platinum4]

@mrbrdo is this more helpful? Hashed fine for 9 hours, dropped stratum, never picked back up til a restart of sgminer.

[18:32:48] Submitting share 42e62d9d to br x15 platinum4.3 [18:32:49] Submitting share ec597cbd to br x15 platinum4.3 [18:32:49] Submitting share 344459e8 to br x15 platinum4.3 [18:32:49] Submitting share 285aad8f to br x15 platinum4.3 [18:32:49] Submitting share 717fa4a2 to br x15 platinum4.3 [18:32:49] Setting GPU 2 engine clock to 1000 [18:32:49] Submitting share 23e3a090 to br x15 platinum4.3 [18:32:49] Submitting share 67ece9cb to br x15 platinum4.3 [18:32:50] Closing socket for stratum br x15 platinum4.3 [18:32:50] Stratum connection to br x15 platinum4.3 interrupted [18:32:50] Cleared 1 work items due to stratum disconnect on pool 0 18:32:50:10.47M (avg):9.333Mh/s | A:0 R:0 HW:0 WU:0.139/m [18:32:51] Setting GPU 2 engine clock to 1000 [18:32:53] Closing socket for stratum mrr x15 platinum4.3 (2) [18:32:53] Closing socket for stratum mrr x15 platinum4.3 (2) [18:32:53] Setting GPU 2 engine clock to 1000 18:32:57:6.515M (avg):8.198Mh/s | A:0 R:0 HW:0 WU:0.119/m [18:33:00] Waiting for work to be available from pools. [18:33:02] br x15 platinum4.3 difficulty changed to 0.001 [18:33:03] Stratum extranonce subscribe for nh x15 multi [18:33:03] Stratum extranonce subscribe for nh x11 multi [18:33:03] nh x15 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [18:33:03] Closing socket for stratum nh x15 multi [18:33:03] nh x11 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [18:33:03] Closing socket for stratum nh x11 multi 18:33:03:3.828M (avg):7.309Mh/s | A:0 R:0 HW:0 WU:0.106/m [18:33:05] Work available from pools, resuming. [18:33:05] Work update message received [18:33:05] New block: 0000000004f46a890fa9d52d71e39305b25c904e6e9efc555553827e554ecbcb... diff 31 [18:33:05] Work update message received [18:33:06] br x15 platinum4.3 stale share detected, submitting (user) [18:33:06] Submitting share 5d06155b to br x15 platinum4.3 [18:33:06] br x15 platinum4.3 JSON stratum auth failed: [ 24, "unauthorized worker", null ] [18:33:06] Closing socket for stratum br x15 platinum4.3 [18:33:06] br x15 platinum4.3 not responding! [18:33:06] Switching to nh x13 multi [18:33:06] Cleared 1 work items due to stratum disconnect on pool 0 [18:33:06] Submitting share 9561a701 to br x15 platinum4.3 [18:33:06] br x15 platinum4.3 stratum share submission failure [18:33:07] Failed to connect to stratum on stratum.nicehash.com:3339 [18:33:07] setup_stratum_socket() on nh x15 multi failover failed [18:33:07] Cannot subscribe to mining.extranonce on hh x14 [18:33:07] Stratum authorisation success for hh x14 [18:33:07] Stratum extranonce subscribe for mrr x13 platinum4.3 [18:33:07] Stratum authorisation success for mrr x13 platinum4.3 [18:33:07] Setting GPU 2 engine clock to 1000

I think that error is pretty indicative of my rental hashing over at TMB, it's the only one I've seen that has unauthorized worker or rejected untracked stratum share.

However, this doesn't explain why it takes a long time to start up as well. Once it's unauthorized, does it just quit trying to get back up the priority chain again?

[platinum4]

Lag time on latching on to betarigs stratum has been drastically reduced/solved as of build July 8th, 2014.

[23:41:34] Testing br x15 platinum4.3 [23:41:34] br x15 platinum4.3 alive, testing stability [23:41:34] Testing nh x15 multi [23:41:34] Testing nh x11 multi [23:41:34] Setting GPU 2 engine clock to 1000 [23:41:35] Stratum extranonce subscribe for nh x11 multi [23:41:35] Stratum authorisation success for br x15 platinum4.3 [23:41:35] nh x11 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [23:41:35] Closing socket for stratum nh x11 multi [23:41:35] Testing nh nist5 multi 23:41:36:12.87M (avg):12.50Mh/s | A:8 R:0 HW:0 WU:0.176/m [23:41:36] Setting GPU 2 engine clock to 1000 [23:41:37] Stratum extranonce subscribe for nh nist5 multi [23:41:37] nh nist5 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [23:41:37] Closing socket for stratum nh nist5 multi [23:41:37] Testing nh keccak multi [23:41:38] Stratum extranonce subscribe for nh keccak multi [23:41:38] Setting GPU 2 engine clock to 1000 [23:41:39] nh keccak multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [23:41:39] Closing socket for stratum nh keccak multi [23:41:39] GPU 1: Share above target [23:41:40] Submitting share 8a6610d7 to nh x13 multi [23:41:40] GPU 0: Share above target [23:41:40] Accepted Coin 687 Diff 0.394/0.100 GPU 2 at nh x13 multi [23:41:40] GPU 0: Share above target [23:41:40] Setting GPU 2 engine clock to 1000 [23:41:41] New block: 00000000033bbd4d043ae639721f2891cf68c95aa1e6b099789909819eb1a8c4... diff 54 23:41:41:12.99M (avg):12.50Mh/s | A:8 R:0 HW:0 WU:0.176/m [23:41:42] Setting GPU 2 engine clock to 1000 [23:41:44] Stratum extranonce subscribe for nh x15 multi [23:41:44] Setting GPU 2 engine clock to 1000 [23:41:45] nh x15 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [23:41:45] Closing socket for stratum nh x15 multi 23:41:46:12.21M (avg):12.50Mh/s | A:8 R:0 HW:0 WU:0.176/m [23:41:46] Setting GPU 2 engine clock to 1000 [23:41:48] Setting GPU 2 engine clock to 1000 [23:41:50] Setting GPU 2 engine clock to 1000 23:41:52:12.98M (avg):12.50Mh/s | A:8 R:0 HW:0 WU:0.175/m [23:41:52] GPU 0: Share above target [23:41:52] Setting GPU 2 engine clock to 1000 [23:41:54] Setting GPU 2 engine clock to 1000 [23:41:56] GPU 2: Share above target [23:41:56] Setting GPU 2 engine clock to 1000 23:41:57:12.20M (avg):12.50Mh/s | A:8 R:0 HW:0 WU:0.175/m [23:41:58] Setting GPU 2 engine clock to 1000 [23:41:59] GPU 0: Share above target [23:42:01] Setting GPU 2 engine clock to 1000 [23:42:01] GPU 1: Share above target 23:42:02:11.75M (avg):12.49Mh/s | A:8 R:0 HW:0 WU:0.175/m [23:42:03] Setting GPU 2 engine clock to 1000 [23:42:05] Setting GPU 2 engine clock to 1000 [23:42:07] Setting GPU 2 engine clock to 1000 23:42:07:12.20M (avg):12.49Mh/s | A:8 R:0 HW:0 WU:0.175/m [23:42:09] br x15 platinum4.3 stable for 30 seconds [23:42:09] Switching to br x15 platinum4.3 [23:42:09] Setting GPU 2 engine clock to 1000 [23:42:09] Cleared 1 work items due to stratum disconnect on pool 3 [23:42:09] Testing nh x15 multi [23:42:09] Testing nh x11 multi [23:42:09] GPU 0: Share above target [23:42:09] Applying pool settings for br x15 platinum4.3... [23:42:09] Init GPU thread 0 GPU 0 virtual GPU 0 [23:42:09] CL Platform vendor: Advanced Micro Devices, Inc. [23:42:09] CL Platform name: AMD Accelerated Parallel Processing [23:42:09] CL Platform version: OpenCL 1.2 AMD-APP (1526.3) [23:42:09] Platform devices: 3 [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] List of devices: [23:42:09] 0 Hawaii [23:42:09] Selected 0: Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] Initialising kernel bitblock.cl with bitalign, unpatched BFI, nfactor 0, n 0 [23:42:09] initCl() finished. Found Hawaii [23:42:09] Init GPU thread 1 GPU 0 virtual GPU 0 [23:42:09] CL Platform vendor: Advanced Micro Devices, Inc. [23:42:09] CL Platform name: AMD Accelerated Parallel Processing [23:42:09] CL Platform version: OpenCL 1.2 AMD-APP (1526.3) [23:42:09] Platform devices: 3 [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] List of devices: [23:42:09] 0 Hawaii [23:42:09] Selected 0: Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] Initialising kernel bitblock.cl with bitalign, unpatched BFI, nfactor 0, n 0 [23:42:09] initCl() finished. Found Hawaii [23:42:09] Init GPU thread 2 GPU 1 virtual GPU 1 [23:42:09] CL Platform vendor: Advanced Micro Devices, Inc. [23:42:09] CL Platform name: AMD Accelerated Parallel Processing [23:42:09] CL Platform version: OpenCL 1.2 AMD-APP (1526.3) [23:42:09] Platform devices: 3 [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] List of devices: [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] Selected 1: Hawaii [23:42:09] 2 Hawaii [23:42:09] Initialising kernel bitblock.cl with bitalign, unpatched BFI, nfactor 0, n 0 [23:42:09] initCl() finished. Found Hawaii [23:42:09] Init GPU thread 3 GPU 1 virtual GPU 1 [23:42:09] CL Platform vendor: Advanced Micro Devices, Inc. [23:42:09] CL Platform name: AMD Accelerated Parallel Processing [23:42:09] CL Platform version: OpenCL 1.2 AMD-APP (1526.3) [23:42:09] Platform devices: 3 [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] List of devices: [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] Selected 1: Hawaii [23:42:09] 2 Hawaii [23:42:09] Initialising kernel bitblock.cl with bitalign, unpatched BFI, nfactor 0, n 0 [23:42:09] initCl() finished. Found Hawaii [23:42:09] Init GPU thread 4 GPU 2 virtual GPU 2 [23:42:09] CL Platform vendor: Advanced Micro Devices, Inc. [23:42:09] CL Platform name: AMD Accelerated Parallel Processing [23:42:09] CL Platform version: OpenCL 1.2 AMD-APP (1526.3) [23:42:09] Platform devices: 3 [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] List of devices: [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] Selected 2: Hawaii [23:42:09] Initialising kernel bitblock.cl with bitalign, unpatched BFI, nfactor 0, n 0 [23:42:09] initCl() finished. Found Hawaii [23:42:09] Init GPU thread 5 GPU 2 virtual GPU 2 [23:42:09] CL Platform vendor: Advanced Micro Devices, Inc. [23:42:09] CL Platform name: AMD Accelerated Parallel Processing [23:42:09] CL Platform version: OpenCL 1.2 AMD-APP (1526.3) [23:42:09] Platform devices: 3 [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] List of devices: [23:42:09] 0 Hawaii [23:42:09] 1 Hawaii [23:42:09] 2 Hawaii [23:42:09] Selected 2: Hawaii [23:42:09] Initialising kernel bitblock.cl with bitalign, unpatched BFI, nfactor 0, n 0 [23:42:09] initCl() finished. Found Hawaii [23:42:10] Stratum extranonce subscribe for nh x11 multi [23:42:11] nh x11 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [23:42:11] Closing socket for stratum nh x11 multi [23:42:11] Testing nh nist5 multi [23:42:11] Setting GPU 2 engine clock to 1000 [23:42:12] Stratum extranonce subscribe for nh nist5 multi [23:42:12] nh nist5 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [23:42:12] Closing socket for stratum nh nist5 multi [23:42:12] Testing nh keccak multi [23:42:13] New best share: 0.165 [23:42:13] Submitting share 124b2df3 to br x15 platinum4.3 23:42:13:2.297M (avg):0.000h/s | A:0 R:0 HW:0 WU:0.155/m [23:42:13] Setting GPU 2 engine clock to 1000 [23:42:13] Accepted Coin 54 Diff 0.165/0.010 GPU 1 at br x15 platinum4.3

[platinum4]

Fucking getting tired of this shit.

"Latest message from your customer Pizza 27 minutes ago:

rig offline??"

"Latest message from your customer Ciumete 27 minutes ago:

your rig is offline !!! "

This is well outside of "5 minutes" now.

[platinum4]

Latest message from your customer Erocebootcamp 17 minutes ago:

rig went offline... 

[mrbrdo]

Thanks for the logs (the old ones). Does sgminer display any message regarding the betarigs pool at all? In the cases where it doesn't connect.

[mrbrdo]

Oh it's probably the one named "br x15", I missed it. Although it looks like it's hashing on it from the log, but keeps losing connection. That's kind of weird, it would be nice to get a confirmation from some other user. It doesn't happen if you use an older miner?

[mrbrdo]

Also it seems like the pool is saying your authorisation isn't correct. It could be due to many reasons, either sgminer doesn't send it correctly, or betarigs has a bug, or you don't have it set correctly (although I'm assuming it works if you restart sgminer so it's not that then). Does it always say that when it fails to work properly?

[platinum4]

Ok @mrbrdo, why does this happen, is it an extranonce-subscribe issue?

[20:18:04] Closing socket for stratum nh x15 multi [20:18:04] Testing nh x15 multi [20:18:04] Testing nh nist5 multi [20:18:04] GPU 1: Share above target [20:18:05] Stratum extranonce subscribe for nh nist5 multi [20:18:05] GPU 1: Share above target [20:18:06] nh nist5 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:18:06] Closing socket for stratum nh nist5 multi [20:18:06] Testing nh keccak multi [20:18:07] Stratum extranonce subscribe for nh keccak multi [20:18:08] nh keccak multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:18:08] Closing socket for stratum nh keccak multi [20:18:08] Testing mrr x15 platinum4.2 [20:18:08] Testing mrr x15 platinum4.2 (2) [20:18:08] Testing mrr x15 platinum4.2 (3) [20:18:08] mrr x15 platinum4.2 (3) alive [20:18:08] Testing mrr x15 platinum4.2 (4) [20:18:08] mrr x15 platinum4.2 (4) alive [20:18:08] Testing mrr x15 platinum4.2 (5) [20:18:08] New block: 0000000001b223703527296fbee145463e334fd1855b957d8d1d2b26854024ef... diff 102 [20:18:08] Work update message received 20:18:08:10.88M (avg):10.61Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:09] Stratum extranonce subscribe for mrr x15 platinum4.2 (2) [20:18:09] Stratum authorisation success for mrr x15 platinum4.2 (2) [20:18:09] Submitting share 3ee20a26 to br x15 platinum4.2 [20:18:10] GPU 2: Share above target [20:18:10] Pool 0 stratum share result lag time 1 seconds [20:18:10] Accepted Coin 103 Diff 0.014/0.010 GPU 0 at br x15 platinum4.2 [20:18:11] GPU 2: Share above target [20:18:11] GPU 2: Share above target [20:18:12] Submitting share b97dcab2 to br x15 platinum4.2 [20:18:12] Accepted Coin 103 Diff 0.212/0.010 GPU 2 at br x15 platinum4.2 [20:18:12] GPU 2: Share above target [20:18:13] Submitting share 3bc453b2 to br x15 platinum4.2 [20:18:13] Accepted Coin 103 Diff 0.022/0.010 GPU 1 at br x15 platinum4.2 20:18:14:10.40M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:15] GPU 1: Share above target [20:18:15] Submitting share 4533b308 to br x15 platinum4.2 [20:18:15] New block: 00000000017852743ac1d62811d8d0cb2286a4d234d0da2776b85accecf434cd... diff 107 [20:18:15] Work update message received [20:18:16] Pool 0 stratum share result lag time 1 seconds [20:18:16] Rejected Coin 103 Diff 0.010/0.010 GPU 0 br x15 platinum4.2 (job not found) [20:18:16] Submitting share bdad9745 to br x15 platinum4.2 [20:18:17] Pool 0 stratum share result lag time 1 seconds [20:18:17] Accepted Coin 108 Diff 0.013/0.010 GPU 0 at br x15 platinum4.2 [20:18:17] Submitting share 14d5d45c to br x15 platinum4.2 [20:18:18] GPU 0: Share above target [20:18:18] GPU 1: Share above target [20:18:18] Pool 0 stratum share result lag time 1 seconds [20:18:18] Accepted Coin 108 Diff 0.011/0.010 GPU 0 at br x15 platinum4.2 [20:18:19] GPU 0: Share above target 20:18:19:10.89M (avg):10.61Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:20] GPU 2: Share above target [20:18:20] GPU 2: Share above target [20:18:21] GPU 2: Share above target [20:18:21] Submitting share 24112185 to br x15 platinum4.2 [20:18:21] Accepted Coin 108 Diff 0.013/0.010 GPU 1 at br x15 platinum4.2 [20:18:22] GPU 0: Share above target 20:18:25:10.63M (avg):10.61Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:25] Stratum extranonce subscribe for mrr x15 platinum4.2 (5) [20:18:26] Stratum authorisation success for mrr x15 platinum4.2 (5) [20:18:26] GPU 2: Share above target [20:18:26] Stratum extranonce subscribe for mrr x15 platinum4.2 [20:18:26] Stratum authorisation success for mrr x15 platinum4.2 [20:18:27] Submitting share f2f1527e to br x15 platinum4.2 [20:18:27] Accepted Coin 108 Diff 0.013/0.010 GPU 1 at br x15 platinum4.2 [20:18:27] Submitting share 4d94ab5f to br x15 platinum4.2 [20:18:28] Pool 0 stratum share result lag time 1 seconds [20:18:28] Accepted Coin 108 Diff 0.232/0.010 GPU 2 at br x15 platinum4.2 [20:18:28] GPU 2: Share above target [20:18:30] GPU 0: Share above target [20:18:30] Setting GPU 0 fan percentage to 81 [20:18:30] New block: 000000000032009e2051507a13a838709ed11ae3181a60927c712b3e22fb9480... diff 119 [20:18:30] Work update message received [20:18:30] GPU 2: Share above target 20:18:31:10.49M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.137/m [20:18:31] Submitting share 800a8622 to br x15 platinum4.2 [20:18:31] Accepted Coin 120 Diff 0.012/0.010 GPU 1 at br x15 platinum4.2 [20:18:32] Setting GPU 0 fan percentage to 80 [20:18:33] Submitting share cc7b09b4 to br x15 platinum4.2 [20:18:33] Accepted Coin 120 Diff 0.053/0.010 GPU 2 at br x15 platinum4.2 [20:18:34] GPU 0: Share above target [20:18:35] Stratum extranonce subscribe for nh x15 multi [20:18:35] nh x15 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:18:35] Closing socket for stratum nh x15 multi 20:18:36:10.07M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.137/m [20:18:38] Testing nh x15 multi [20:18:38] Testing nh nist5 multi [20:18:39] Stratum extranonce subscribe for nh nist5 multi [20:18:39] GPU 2: Share above target [20:18:39] nh nist5 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:18:39] Closing socket for stratum nh nist5 multi [20:18:39] Testing nh keccak multi [20:18:40] Stratum extranonce subscribe for nh keccak multi [20:18:41] nh keccak multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:18:41] Closing socket for stratum nh keccak multi [20:18:41] GPU 1: Share above target 20:18:42:10.59M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:43] GPU 2: Share above target [20:18:44] Submitting share 2c0a4649 to br x15 platinum4.2 [20:18:45] Pool 0 stratum share result lag time 1 seconds [20:18:45] Accepted Coin 120 Diff 0.010/0.010 GPU 0 at br x15 platinum4.2 [20:18:45] GPU 1: Share above target [20:18:45] New block: 00000000008b1dac2a471db03747ff680fbee84a4f8c45379ea4f7d202b8fb1c... diff 131 [20:18:45] Work update message received [20:18:46] GPU 1: Share above target [20:18:46] GPU 2: Share above target [20:18:47] GPU 1: Share above target 20:18:47:10.60M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.137/m [20:18:47] Suspending stratum on mrr x15 platinum4.2 (3) [20:18:47] Closing socket for stratum mrr x15 platinum4.2 (3) [20:18:47] Submitting share 9b31eacd to br x15 platinum4.2 [20:18:48] Stratum connection to mrr x15 platinum4.2 (2) resumed [20:18:48] mrr x15 platinum4.2 (2) alive [20:18:48] Suspending stratum on mrr x15 platinum4.2 (2) [20:18:48] Closing socket for stratum mrr x15 platinum4.2 (2) [20:18:48] Stratum connection to mrr x15 platinum4.2 resumed [20:18:48] mrr x15 platinum4.2 alive [20:18:48] Suspending stratum on mrr x15 platinum4.2 [20:18:48] Closing socket for stratum mrr x15 platinum4.2 [20:18:48] Pool 0 stratum share result lag time 1 seconds [20:18:48] Accepted Coin 132 Diff 0.020/0.010 GPU 0 at br x15 platinum4.2 [20:18:48] Suspending stratum on mrr x15 platinum4.2 (4) [20:18:48] Closing socket for stratum mrr x15 platinum4.2 (4) [20:18:48] Stratum connection to mrr x15 platinum4.2 (5) resumed [20:18:48] mrr x15 platinum4.2 (5) alive [20:18:48] Suspending stratum on mrr x15 platinum4.2 (5) [20:18:48] Closing socket for stratum mrr x15 platinum4.2 (5) [20:18:49] GPU 2: Share above target [20:18:49] GPU 0: Share above target [20:18:52] Submitting share 2416f181 to br x15 platinum4.2 20:18:53:10.54M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:53] Pool 0 stratum share result lag time 1 seconds [20:18:53] Accepted Coin 132 Diff 0.021/0.010 GPU 1 at br x15 platinum4.2 [20:18:53] GPU 1: Share above target [20:18:54] GPU 0: Share above target 20:18:58:10.00M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:18:59] GPU 1: Share above target [20:19:00] Submitting share 8a6ef9ba to br x15 platinum4.2 [20:19:01] Pool 0 stratum share result lag time 1 seconds [20:19:01] Accepted Coin 132 Diff 0.012/0.010 GPU 2 at br x15 platinum4.2 [20:19:01] GPU 1: Share above target [20:19:03] Submitting share f0433d7d to br x15 platinum4.2 [20:19:03] Accepted Coin 132 Diff 0.039/0.010 GPU 2 at br x15 platinum4.2 20:19:04:10.74M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.136/m [20:19:05] Submitting share cb1a1029 to br x15 platinum4.2 [20:19:05] Submitting share 8a23f40a to br x15 platinum4.2 [20:19:05] Accepted Coin 132 Diff 0.018/0.010 GPU 2 at br x15 platinum4.2 [20:19:05] Accepted Coin 132 Diff 0.010/0.010 GPU 1 at br x15 platinum4.2 [20:19:06] Submitting share 1464b465 to br x15 platinum4.2 [20:19:06] GPU 1: Share above target [20:19:06] Accepted Coin 132 Diff 0.024/0.010 GPU 2 at br x15 platinum4.2 [20:19:06] GPU 2: Share above target [20:19:07] Stratum extranonce subscribe for nh x15 multi [20:19:07] nh x15 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:19:07] Closing socket for stratum nh x15 multi [20:19:07] GPU 2: Share above target [20:19:08] GPU 1: Share above target [20:19:09] Submitting share 5fde953b to br x15 platinum4.2 [20:19:09] Accepted Coin 132 Diff 0.010/0.010 GPU 0 at br x15 platinum4.2 20:19:09:10.70M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.137/m [20:19:10] GPU 2: Share above target [20:19:10] GPU 1: Share above target [20:19:11] Testing nh x15 multi [20:19:11] Testing nh nist5 multi [20:19:12] Stratum extranonce subscribe for nh nist5 multi [20:19:13] nh nist5 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:19:13] Closing socket for stratum nh nist5 multi [20:19:13] Testing nh keccak multi [20:19:13] GPU 0: Share above target [20:19:14] GPU 1: Share above target [20:19:14] Stratum extranonce subscribe for nh keccak multi 20:19:14:10.27M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.137/m [20:19:14] GPU 0: Share above target [20:19:14] nh keccak multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:19:14] Closing socket for stratum nh keccak multi [20:19:15] GPU 0: Share above target [20:19:15] GPU 0: Share above target [20:19:16] GPU 1: Share above target [20:19:17] GPU 0: Share above target [20:19:18] GPU 2: Share above target [20:19:18] GPU 2: Share above target 20:19:19:10.45M (avg):10.60Mh/s | A:3 R:0 HW:0 WU:0.137/m [20:19:20] GPU 2: Share above target [20:19:20] GPU 2: Share above target [20:19:20] GPU 0: Share above target [20:19:21] GPU 1: Share above target [20:19:21] Submitting share 70ecd422 to br x15 platinum4.2 [20:19:22] Pool 0 stratum share result lag time 1 seconds [20:19:22] Accepted Coin 132 Diff 0.017/0.010 GPU 1 at br x15 platinum4.2 [20:19:23] GPU 0: Share above target [20:19:23] Submitting share e85ba1eb to br x15 platinum4.2 [20:19:23] Submitting share 287472fe to br x15 platinum4.2 [20:19:24] Pool 0 stratum share result lag time 1 seconds [20:19:24] Accepted Coin 132 Diff 0.072/0.010 GPU 1 at br x15 platinum4.2 [20:19:24] Pool 0 stratum share result lag time 1 seconds [20:19:24] Accepted Coin 132 Diff 0.026/0.010 GPU 0 at br x15 platinum4.2 [20:19:24] GPU 2: Share above target 20:19:25:10.59M (avg):10.60Mh/s | A:4 R:0 HW:0 WU:0.138/m [20:19:26] Submitting share de1f6c4d to br x15 platinum4.2 [20:19:26] Accepted Coin 132 Diff 0.032/0.010 GPU 1 at br x15 platinum4.2 [20:19:28] GPU 0: Share above target [20:19:29] GPU 1: Share above target [20:19:29] GPU 1: Share above target [20:19:29] GPU 1: Share above target 20:19:30:10.49M (avg):10.60Mh/s | A:4 R:0 HW:0 WU:0.138/m [20:19:30] GPU 0: Share above target [20:19:30] Setting GPU 0 fan percentage to 81 [20:19:32] GPU 0: Share above target [20:19:32] Setting GPU 0 fan percentage to 80 [20:19:32] GPU 0: Share above target [20:19:33] GPU 1: Share above target [20:19:33] GPU 1: Share above target [20:19:35] GPU 0: Share above target 20:19:36:10.47M (avg):10.60Mh/s | A:4 R:0 HW:0 WU:0.138/m [20:19:37] GPU 0: Share above target [20:19:37] GPU 1: Share above target [20:19:37] GPU 2: Share above target [20:19:38] Stratum extranonce subscribe for nh x15 multi [20:19:38] Submitting share dd5ff002 to br x15 platinum4.2 [20:19:39] GPU 1: Share above target [20:19:39] Pool 0 stratum share result lag time 1 seconds [20:19:39] Accepted Coin 132 Diff 0.020/0.010 GPU 0 at br x15 platinum4.2 [20:19:39] Stratum authorisation success for nh x15 multi [20:19:39] Stratum connection to nh x15 multi resumed

It actually kicks it off of pool-priority zero, which is br x15.

"pools" : [ { "name" : "br x15 platinum4.2", "url" : "stratum+tcp://r6214.g50.rigs.eu.betarigs.com:9045", "user" : "platinumstephen-6214", "pass" : "x", \ "pool-priority" : "0", "algorithm" : "bitblock", "intensity" : "19", "gpu-engine" : "1000", "gpu-memclock" : "1250", "gpu-threads" : "2", "thread-concurrency" : "8193" }, { "name" : "hashbusters x11 test", "url" : "stratum+tcp://192.99.148.34:5555", "user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq", "pass" : "x", "pool-priority" : "1", "algorithm" : "darkcoin-mod", "intensity" : "19", "gpu-engine" : "1000", "gpu-memclock" : "1250", "gpu-threads" : "2", "thread-concurrency" : "8193", "state" : "disabled" }, { "name" : "nh x15 multi", "url" : "stratum+tcp://stratum.nicehash.com:4339", "user" : "19VAeHKFfo91wxPhXQAEvHbkV4B2t5yRgq", "pass" : "d=0.100;f0=2.95;f2=1.45;f3=16.2;f4=12;f5=1440;f6=10.8;f7=42.3;c0=2.9;c2=2.9;c3=1.8;c4=1.8;c5=2.4;c6=1.8;c7=1.6", \ "pool-priority" : "2", "algorithm" : "bitblock", "intensity" : "19", "pool-gpu-engine" : "1000", "pool-gpu-memclock" : "1250", "gpu-threads" : "2", "thread-concurrency" : "8193" },

[platinum4]

15 seconds after this particular part

[20:19:39] Accepted Coin 132 Diff 0.020/0.010 GPU 0 at br x15 platinum4.2 [20:19:39] Stratum authorisation success for nh x15 multi [20:19:39] Stratum connection to nh x15 multi resumed

This occurs, and it never looks back up the chain of priorities.

[20:19:39] nh x15 multi alive, testing stability [20:19:40] GPU 1: Share above target [20:19:41] Work update message received 20:19:41:10.46M (avg):10.60Mh/s | A:4 R:0 HW:0 WU:0.138/m [20:19:42] GPU 2: Share above target [20:19:43] GPU 2: Share above target [20:19:43] GPU 1: Share above target [20:19:44] GPU 2: Share above target [20:19:44] nh x15 multi stable for 30 seconds [20:19:44] Switching to nh x15 multi [20:19:44] Cleared 1 work items due to stratum disconnect on pool 0 [20:19:44] Testing nh nist5 multi [20:19:45] New block: 0000000000906107754d45fa283e62f4b8bc3e77886b1d5eb2939a865d64f7bb... diff 342 [20:19:45] No settings change from pool nh x15 multi... [20:19:45] Work update message received [20:19:46] Stratum extranonce subscribe for nh nist5 multi [20:19:46] nh nist5 multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:19:46] Closing socket for stratum nh nist5 multi [20:19:46] Testing nh keccak multi 20:19:46:10.01M (avg):10.59Mh/s | A:4 R:0 HW:0 WU:0.138/m [20:19:46] GPU 0: Share above target [20:19:47] Submitting share 6aa59744 to nh x15 multi [20:19:47] GPU 0: Share above target [20:19:47] Accepted Coin 342 Diff 0.016/0.008 GPU 1 at nh x15 multi [20:19:47] Stratum extranonce subscribe for nh keccak multi [20:19:48] nh keccak multi JSON stratum auth failed: [ 24, "Current algorithm not most profitable.", null ] [20:19:48] Closing socket for stratum nh keccak multi [20:19:48] GPU 2: Share above target 20:19:52:10.59M (avg):10.60Mh/s | A:4 R:0 HW:0 WU:0.138/m [20:19:52] GPU 0: Share above target [20:19:52] Submitting share 54ff8762 to nh x15 multi [20:19:53] Pool 2 stratum share result lag time 1 seconds [20:19:53] Accepted Coin 342 Diff 0.010/0.008 GPU 2 at nh x15 multi

[mrbrdo]

Hm yes it definitely seems to be a bug. Could be related to extranonce (although I would guess not, I don't see how) or to configuration parser. CC @ystarnaud

[platinum4]

I've changed my configs on all rigs to

"extranonce-subscription" : false

and will report back in the next 24-48 hours, depending on if rentals catch or not.

[mrbrdo]

great idea, didn't think of that (btw, I'm guessing nicehash won't work without that)

[platinum4]

"extranonce-subscription" : false

did not "disconnect" me from nicehash, and actually, still allows me to stay on their deal A-OK. After 24 hours however, probably 12 of those being nicehash nist5, it appears now that betarigs stratum proxy won't even recognize my rigs are online, it's marking them as offline. Is that perhaps, too many hours of an unknown algorithm that it stops and quits?

[04:28:02] Testing br x15 platinum4.3 [04:28:03] Closing socket for stratum br x15 platinum4.3 [04:28:03] Closing socket for stratum br x15 platinum4.3

Then it doesn't even try anymore, for the remainder of the mining instance. I'm getting actually more confused.

[mrbrdo]

Well there is actually a possible issue I've been looking into recently, which may or may not be related.

The possible bug is this:

• here auth_stratum will only be called if extranonce subscribe succeeds or is disabled: https://github.com/sgminer-dev/sgminer/blob/v5_0/sgminer.c#L5562
• if auth_stratum fails it will suspend the pool: https://github.com/sgminer-dev/sgminer/blob/v5_0/util.c#L2000
• however if subscribe_extranonce fails it will not suspend the pool: https://github.com/sgminer-dev/sgminer/blob/v5_0/util.c#L1957 but of course auth_stratum will not be called

I believe this can cause various problems, but I want to get a word on it from bitbandi who added extranonce subscribe.

A possible and best solution might be to ignore if extranonce subscribe fails, I think it should still try to auth and use the pool even if this feature is not supported.

[platinum4]

Any reason why it would show the rigs as offline, even when it's pool priority zero and at the top? Only just recently noticed this when nist5 has been running for over 12 hours now. It knocks the rigs offline on betarigs but you know that's not the case, they're still hashing something, just not a recognizable algo. Also, I don't get any hashrates showing in MRR either, it says rigs are online, but no hashrates to show.

[mrbrdo]

Not sure but it may be related, perhaps the connection stays open but does not ever do auth with betarigs and so it never tells it that it's working. But I am just guessing. Hopefully bitbandi can clear up the mentioned issue.

[platinum4]

Just changed to "extranonce-subscription" : true and rigs showed up instantaneously on betarigs as Not Rented.

So that does have something to do with it...

[mrbrdo]

Can you try this branch: https://github.com/sgminer-dev/sgminer/tree/mrbrdo_testing I have not tested, but implements the solution as I was saying. Leave extranonce set to true.

[platinum4]

@mrbrdo you'd have to get me compiled Windows binaries... I just don't have the correct environment set up to build. My latest nightly builds I get now from nicehash, and idk what branch they build from. If you have a dropbox link for me I'm 100% willing to test, as always. I know I've been a bit annoying with reporting some of these bugs, yet, sort of a necessary evil. ;D

[mrbrdo]

Not annoying at all but very useful. Unfortunately I don't have a Windows build environment. @troky can you help perhaps?

[badman74]

here is the latest testing build (https://mega.co.nz/#!qd4yiZbR!UGVawOyct0EGVol3Vme2iqe21DcDqikRrzkNTCEvSdM) finally got a build env up and working again.... try cygwin, it was fairly easy to set up

[badman74]

hmm nevermind it looks like this has to be run from cygwin if it was built with it....

[troky]

mrbrdo_testing latest build: https://mega.co.nz/#!0IBkyIqT!f-Uv_A7cyl3nus9aLoQ2FK9lQX0z5fZEps4jcHOoPUU

v5_0 latest build: https://mega.co.nz/#!kRIhDQyT!cq8gig11QBakt0Yl1bkBj82vA8K81nVjjuJ0mK4uHCU

[platinum4]

MSVCR100.dll missing and I have both 2010 Redistributables x86 and x64 installed.

[platinum4]

@troky I can run your previous Jansson test build that you wrapped up for me in IRC chat a few weeks ago, but this newest one (mrbrdo_test) is saying it's missing the .dll

Both were built with your MSVS method, correct?

[troky]

Here is release build of mrbrdo_testing:

https://mega.co.nz/#!wF5mDCZY!aPq7eHzcYM9YBpLZis53jzq7Q-rsIv53hT5qAZTWheA

[mrbrdo]

Hm it's definitely possible. Although it seems that option has been present for a very long time?

[mrbrdo]

[18:33:06] br x15 platinum4.3 JSON stratum auth failed: [
24,
"unauthorized worker",
null
]

do you still get these errors with the mrbrdo_testing version?

[mrbrdo]

Let's keep it open for now. So it seems mrbrdo_testing maybe helped with it? I think it does not have anything to do with algorithm (e.g. NIST5).

[mfiano]

For the last week I noticed this problem too....I have to manually switch to betarigs when I get a message from my renter saying it's not mining

[mfiano]

For the record, this is not specific to Betarigs - it occurs with at least MRR as well. @mrbrdo I have not tried your testing branch as I finally have a codebase that has had no problems in a few days. Ironically thats only the unstable develop branch :)

[platinum4]

Some of my rigs appear offline and unrentable, as well, this is with v5_0 build from 7-25

[mfiano]

@mrbrdo I previously mentioned that develop branch fixes this. I was wrong. I just missed a day's worth of 4 rentals. sgminer decided to never switch. The only thing that has changed since it did switch. Usually I am mining the 2nd to the last pool in my failover list...yesterday I decided to manually switch to the last pool and mied for a couple hours before manually switching back to the 2nd to last pool. MiningRigRentals, the pool that missed a rental, is in slot #2 (under Betarigs). MRR shows as "Alive" but sometimes never switches. This is the case on all 3 of my rigs simultaneously. I will try out mrbrdo_testing sometime soon when I have some free time.

[ystarnaud]

I don't know but I think there's a bit more involved here than sgminer itself. Maybe we need to add more detailed information as to why a pool is dead or not switching but I do not believe this is an issue with sgminer. Rental services have another component to factor in: the renter.

First off, I will say that I do not use betarigs so I can't speak for it but I am fairly sure that it works exactly like MRR, which I use every single day. That said I have had instances where I would check my farm and notice that half or all my rigs were happily hashing on Nicehash, for example, while I was rented on MRR. In those instances, I asked the MRR admins on IRC to check if something was wrong with the rental. Every single time, the problem was that the renter was using a broken or bad pool with no backup.

Services like MRR (and im sure betarigs) are simply stratum proxies that will block your connection if you are not rented. When you are rented and the end point does not respond properly or blocks connections, there is not much that can be done other than contacting the renter. sgminer doesn't just decide to not connect to a pool - At least I have never seen it behave that way. If it doesn't switch, then it sees a problem. Also, note that when a pool becomes alive from "dead" status, sgminer will only switch to that pool if it stays alive for 60 seconds to make sure its stable. The pool might be labeled alive but not be usable yet.

Next time this happens, you should watch the logs for a few minutes and see what it says about pool connection attempts/failures or maybe contact your rental service to see if they can detect any problems. I don't mean to say sgminer is flawless, but in my everyday experience, I have not experienced these issues without having a clueless renter involved.

[mfiano]

@ystarnaud, about the logs - during the times that it doesn't work, there is actually 0 log activity related to the rental pool. I realize it won't switch to it until a minute or so, but we're talking a whole day's worth of a rental never switching during 24h rentals. MRR has actually contacted me over repeated issues, saying that it was my fault. Infact, they just rolled out a feature to cancel/refund if there is no connection within 20 minutes because of this pattern lately.

[ystarnaud]

@mfiano I just had it happen to be again for the second time this weekend. I contacted the renter to check his pool, to which he saw nothing wrong. Half my rigs were reporting MRR as dead. He decided to go ahead and try a different pool and bam... within seconds all my rigs were on MRR. I don't know your circumstances but I just wanted to point out that theres more to rentals than just sgminer connecting to the rental stratum.

On MRR does it show "online" or "offline" when MRR won't switch? If it says "online" then your sgminer is communicating with their stratum and the problem should almost always be on the renter's end point.

[mfiano]

@ystarnaud The problem is not related, as it is marked "Alive" for me, just never switches, and it occurs with every rental until I restart sgminer. Upon restart, or manually switching to MRR, it happily hashes. Please tell me how it can be another end's fault when it hashes if I tell it to do so?

[mfiano]

Another thing to prove it is definitely sgminer. Scenario:

• 3 rigs, each with identical configuration files.
• Each rig has the same pools configured in failover mode, with the same order.
• On one of my rigs, I manually switched to my own pool briefly to test mining on it, but then went back to the pool the others were mining on.
• No rigs were restarted, or had their configuration modified, by file or at runtime.

I got a rental today on MRR. Immediately the 2 rigs that I wasn't manually switching with, switched to MRR. The other rig is still mining on the same pool (not MRR).

This leads me to believe manually switching pools is messing with the failover list somehow. I have no clue how to further debug this. Hope this helps somewhat.

[badman74]

i don't know if this is relevant but i have found that p2pool doesn't work unless i set "no-extranonce" : true, in the pool section for that pool

[platinum4]

mine's been hit or miss on rigs catching on to stratums. I usually have to message the renter first so they don't bitch

On Wed, Aug 6, 2014 at 5:27 PM, badman74 notifications@github.com wrote:

i don't know if this is relevant but i have found that p2pool doesn't work unless i set "no-exranonce" : true, in the pool section for that pool

— Reply to this email directly or view it on GitHub https://github.com/sgminer-dev/sgminer/issues/332#issuecomment-51406363.

[ystarnaud]

Do you guys switch pools manually often? I never do this might be the problem.

[ystarnaud]

Actually it is... upon looking at the code, switching manually to a specific pool forces that pool to become top priority. Doing this is the only way to ensure the miner will switch to it otherwise the top priority pool would stay selected no matter what you switch to. I don't think this is a bug per say.

[badman74]

would it help to manually set the pool priority in the pool config?