All of a sudden the reject share rate went up rapidly...

Discuss issues with mining rigs and connectivity issues with experienced Prohashing miners.
Forum rules
Welcome to the mining rig and connectivity support forum!

This forum is for discussing issues with mining rigs and connectivity issues with experienced PROHASHING miners. This is a great place to ask questions about connecting specific hardware to PROHASHING.

Remember, PROHASHING employees do not closely monitor the forums like we do the official support channels, so this forum's purpose is to connect you with other PROHASHING miners who have experience with similar hardware/issues. If you have connectivity issues you are unable to resolve here on the forum, please submit a ticket through the official support channels.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
User avatar
DeafEyeJedi
Posts: 32
Joined: Wed May 25, 2022 11:38 pm
Location: USA

All of a sudden the reject share rate went up rapidly...

Post by DeafEyeJedi » Thu Aug 18, 2022 4:47 am

Out of the blue about an hour ago or so I’ve been getting tons of rejected share rates running ETHhash on my AMD cards with TRM — curious if anyone out there is experiencing the same phenomenon? It’s so bad if went from 100% to 94% and sometimes worse. What gives?

Because if I go to Flexpool.io (even with same OC settings) and all seems fine with no rejected share rates so I’m assuming this is on ProHashing end? I had no issues with this two rigs running TRM in ProHashing up until this point last night.
Last edited by DeafEyeJedi on Thu Aug 18, 2022 1:17 pm, edited 1 time in total.
Baseball and Mining. HaCkint0sh and Crypto. Magic Lantern never dies! :geek:
User avatar
Sarah Manter
Posts: 639
Joined: Fri Aug 13, 2021 11:15 am
Contact:

Re: All of a sudden the reject share rate went up rapidly...

Post by Sarah Manter » Thu Aug 18, 2022 6:34 am

DeafEyeJedi wrote: Thu Aug 18, 2022 4:47 am Out of the blue about an hour ago or so I’ve been getting tons of rejected share rate running ETHhash on my AMD cards with TRM — curious if anyone out there is experiencing the same phenomenon? It’s so bad if went from 100% to 94% and sometimes worse. What gives?

Because if I go to Flexpool.io (even with same OC settings) and all seems fine with no rejected share rates so I’m assuming this is on ProHashing end? I had no issues with this two rigs running TRM in ProHashing up until this point last night.
Hello, can you please put in an official support ticket so that I can pass it on to the engineers?
thundergun
Posts: 27
Joined: Tue Apr 13, 2021 7:58 am

Re: All of a sudden the reject share rate went up rapidly...

Post by thundergun » Thu Aug 18, 2022 9:28 am

The dag went over 5gig yesterday on ETH. How many gigs are the cards?
UbjfP2ZOJa
Posts: 21
Joined: Sat Dec 11, 2021 3:10 am

Re: All of a sudden the reject share rate went up rapidly...

Post by UbjfP2ZOJa » Thu Aug 18, 2022 10:40 am

I'm experiencing the same thing on an Nvidia 3070 (8GB), also using T-Rex. Here's the log when it started (times in PDT):

"20220817 13:57:14 [ OK ] 3320/3334 - 61.25 MH/s, 182ms ... GPU #0 | 3.93 G

---------------------20220817 13:57:40 ---------------------
Mining at prohashing.com:3339 [50.220.121.209], diff: 1.07 G
GPU #0: ASUS RTX 3070 - 61.25 MH/s, [T:56C, P:119W, F:80%, E:519kH/W], 3320/3334 R:0% I:0.42%
Shares/min: 3.161 (Avg. 3.294)
Max diff share was found by GPU #0, diff: 45.37 T
Uptime: 16 hours 48 mins 15 secs | Algo: ethash | Driver: 512.77 | T-Rex 0.26.5
WD: 16 hours 48 mins 16 secs, shares: 3320/3334

20220817 13:57:49 WARN: Connection with pool prohashing.com:3339 timed out. Trying to reconnect...
20220817 13:57:52 WARN: Can't connect to the mining pool, 50.220.121.209: No connection could be made because the target machine actively refused it
20220817 13:57:52 ERROR: No connection with prohashing.com:3339, retry after 10 seconds
20220817 13:58:04 WARN: Can't connect to the mining pool, 50.220.121.209: No connection could be made because the target machine actively refused it
20220817 13:58:04 ERROR: No connection with prohashing.com:3339, retry after 10 seconds

--------------------20220817 13:58:10 ---------------------
Mining at prohashing.com:3339 [no connection], diff: 1.07 G
GPU #0: ASUS RTX 3070 - 61.24 MH/s, [T:47C, P:26W, F:80%, E:696kH/W], 3320/3334 R:0% I:0.42%
Shares/min: 3.161 (Avg. 3.294)
Max diff share was found by GPU #0, diff: 45.37 T
Uptime: 16 hours 48 mins 45 secs | Algo: ethash | Driver: 512.77 | T-Rex 0.26.5
WD: 16 hours 48 mins 46 secs, shares: 3320/3334

20220817 13:58:16 Using protocol: stratum1.
20220817 13:58:16 Authorizing...
20220817 13:58:16 Authorized successfully.
20220817 13:58:33 [FAIL] 3320/3335 - This mining server just restarted and has not yet finished computing the DAG for this share., 475ms ... GPU #0 | 1.67 G

---------------------20220817 13:58:40 ---------------------
Mining at prohashing.com:3339 [50.220.121.209], diff: 1.07 G
GPU #0: ASUS RTX 3070 - 60.88 MH/s, [T:53C, P:118W, F:80%, E:761kH/W], 3320/3335 R:0.03% I:0.42%
Shares/min: 3.161 (Avg. 3.294)
Max diff share was found by GPU #0, diff: 45.37 T
Uptime: 16 hours 49 mins 15 secs | Algo: ethash | Driver: 512.77 | T-Rex 0.26.5
WD: 16 hours 49 mins 16 secs, shares: 3320/3335

20220817 13:58:47 [ OK ] 3321/3336 - 60.88 MH/s, 4857ms ... GPU #0 | 8.70 G
20220817 13:59:07 [FAIL] 3321/3337 - Both primary and merge mined shares are stale., 10089ms ... GPU #0 | 4.35 G
20220817 13:59:07 [FAIL] 3321/3338 - Both primary and merge mined shares are stale., 6884ms ... GPU #0 | 3.89 G
20220817 13:59:07 [FAIL] 3321/3339 - Both primary and merge mined shares are stale., 2084ms ... GPU #0 | 1.51 G
20220817 13:59:08 [ OK ] 3322/3340 - 60.98 MH/s, 106ms ... GPU #0 | 1.41 G"

I have rebooted computer and restarted the miner. Currently showing reject rate of 1.84%, invalid 0.05% (2086/2126) in 10 hours 26 minutes.

I did submit through support chat.
User avatar
DeafEyeJedi
Posts: 32
Joined: Wed May 25, 2022 11:38 pm
Location: USA

Re: All of a sudden the reject share rate went up rapidly...

Post by DeafEyeJedi » Thu Aug 18, 2022 12:23 pm

Sarah Manter wrote: Thu Aug 18, 2022 6:34 am Hello, can you please put in an official support ticket so that I can pass it on to the engineers?
Absolutely. Do I just go to the discord live channel or where do I find the support ticket requests? Thanks!
Baseball and Mining. HaCkint0sh and Crypto. Magic Lantern never dies! :geek:
User avatar
DeafEyeJedi
Posts: 32
Joined: Wed May 25, 2022 11:38 pm
Location: USA

Re: All of a sudden the reject share rate went up rapidly...

Post by DeafEyeJedi » Thu Aug 18, 2022 12:27 pm

thundergun wrote: Thu Aug 18, 2022 9:28 am The dag went over 5gig yesterday on ETH. How many gigs are the cards?
Hmmm that's an interesting speculation. My AMD cards are 8-16GB (5600XT, 5700XT, 6800, 6800XT & 6900XT) all from Sapphire.

Both rigs were in the low 90's for Reject Share Rates late last night and I decided to let it run overnight with Flexpool.io in the hopes that ProHashing will be sorted out by today which I'll be trying right now and will report back.
Baseball and Mining. HaCkint0sh and Crypto. Magic Lantern never dies! :geek:
User avatar
DeafEyeJedi
Posts: 32
Joined: Wed May 25, 2022 11:38 pm
Location: USA

Re: All of a sudden the reject share rate went up rapidly...

Post by DeafEyeJedi » Thu Aug 18, 2022 12:38 pm

UbjfP2ZOJa wrote: Thu Aug 18, 2022 10:40 am I'm experiencing the same thing on an Nvidia 3070 (8GB), also using T-Rex. Here's the log when it started (times in PDT):

"20220817 13:57:14 [ OK ] 3320/3334 - 61.25 MH/s, 182ms ... GPU #0 | 3.93 G

---------------------20220817 13:57:40 ---------------------
Mining at prohashing.com:3339 [50.220.121.209], diff: 1.07 G
GPU #0: ASUS RTX 3070 - 61.25 MH/s, [T:56C, P:119W, F:80%, E:519kH/W], 3320/3334 R:0% I:0.42%
Shares/min: 3.161 (Avg. 3.294)
Max diff share was found by GPU #0, diff: 45.37 T
Uptime: 16 hours 48 mins 15 secs | Algo: ethash | Driver: 512.77 | T-Rex 0.26.5
WD: 16 hours 48 mins 16 secs, shares: 3320/3334

20220817 13:57:49 WARN: Connection with pool prohashing.com:3339 timed out. Trying to reconnect...
20220817 13:57:52 WARN: Can't connect to the mining pool, 50.220.121.209: No connection could be made because the target machine actively refused it
20220817 13:57:52 ERROR: No connection with prohashing.com:3339, retry after 10 seconds
20220817 13:58:04 WARN: Can't connect to the mining pool, 50.220.121.209: No connection could be made because the target machine actively refused it
20220817 13:58:04 ERROR: No connection with prohashing.com:3339, retry after 10 seconds

--------------------20220817 13:58:10 ---------------------
Mining at prohashing.com:3339 [no connection], diff: 1.07 G
GPU #0: ASUS RTX 3070 - 61.24 MH/s, [T:47C, P:26W, F:80%, E:696kH/W], 3320/3334 R:0% I:0.42%
Shares/min: 3.161 (Avg. 3.294)
Max diff share was found by GPU #0, diff: 45.37 T
Uptime: 16 hours 48 mins 45 secs | Algo: ethash | Driver: 512.77 | T-Rex 0.26.5
WD: 16 hours 48 mins 46 secs, shares: 3320/3334

20220817 13:58:16 Using protocol: stratum1.
20220817 13:58:16 Authorizing...
20220817 13:58:16 Authorized successfully.
20220817 13:58:33 [FAIL] 3320/3335 - This mining server just restarted and has not yet finished computing the DAG for this share., 475ms ... GPU #0 | 1.67 G

---------------------20220817 13:58:40 ---------------------
Mining at prohashing.com:3339 [50.220.121.209], diff: 1.07 G
GPU #0: ASUS RTX 3070 - 60.88 MH/s, [T:53C, P:118W, F:80%, E:761kH/W], 3320/3335 R:0.03% I:0.42%
Shares/min: 3.161 (Avg. 3.294)
Max diff share was found by GPU #0, diff: 45.37 T
Uptime: 16 hours 49 mins 15 secs | Algo: ethash | Driver: 512.77 | T-Rex 0.26.5
WD: 16 hours 49 mins 16 secs, shares: 3320/3335

20220817 13:58:47 [ OK ] 3321/3336 - 60.88 MH/s, 4857ms ... GPU #0 | 8.70 G
20220817 13:59:07 [FAIL] 3321/3337 - Both primary and merge mined shares are stale., 10089ms ... GPU #0 | 4.35 G
20220817 13:59:07 [FAIL] 3321/3338 - Both primary and merge mined shares are stale., 6884ms ... GPU #0 | 3.89 G
20220817 13:59:07 [FAIL] 3321/3339 - Both primary and merge mined shares are stale., 2084ms ... GPU #0 | 1.51 G
20220817 13:59:08 [ OK ] 3322/3340 - 60.98 MH/s, 106ms ... GPU #0 | 1.41 G"

I have rebooted computer and restarted the miner. Currently showing reject rate of 1.84%, invalid 0.05% (2086/2126) in 10 hours 26 minutes.

I did submit through support chat.
Here's what mine looks like...

------------------------------------------------------------------------------------------------
[2022-08-18 09:28:08] Mining ethash with 8 GPU workers
[2022-08-18 09:28:08] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC Power ETH Cfg
[2022-08-18 09:28:08] 0 03:00.0 40 1080 950 910 45C 51C 70C 90.98% 3094 718 mV 89 W R600
[2022-08-18 09:28:08] 1 06:00.0 60 1100 872 1069 53C 59C 64C 76.86% 2541 656 mV 98 W R952
[2022-08-18 09:28:08] 2 0a:00.0 40 1080 950 910 47C 56C 76C 90.98% 3094 718 mV 74 W R608
[2022-08-18 09:28:08] 3 0d:00.0 36 950 950 895 46C 52C 74C 90.98% 3094 675 mV 80 W R576
[2022-08-18 09:28:08] 4 10:00.0 36 1100 950 910 51C 60C 82C 90.98% 3185 687 mV 84 W R576
[2022-08-18 09:28:08] 5 13:00.0 72 1100 1200 1069 41C 47C 58C 70.98% 2414 637 mV 94 W R1092
[2022-08-18 09:28:08] 6 16:00.0 80 1100 1200 1069 45C 47C 58C 70.98% 2414 643 mV 90 W R1280
[2022-08-18 09:28:08] 7 19:00.0 40 1080 1085 925 45C 57C 78C 90.98% 3094 718 mV 87 W R612
[2022-08-18 09:28:08]
[2022-08-18 09:28:08] Stats Uptime: 0 days, 00:25:04
[2022-08-18 09:28:08] ----------------------------------------- GPU Status -------------------------------------------
[2022-08-18 09:28:08] GPU 0 [45C, fan 90%] ethash: 55.93Mh/s, avg 55.29Mh/s, pool 72.29Mh/s a:101 r:0 hw:0
[2022-08-18 09:28:08] GPU 1 [53C, fan 76%] ethash: 61.61Mh/s, avg 61.02Mh/s, pool 59.42Mh/s a:83 r:1 hw:0
[2022-08-18 09:28:08] GPU 2 [47C, fan 90%] ethash: 55.93Mh/s, avg 55.28Mh/s, pool 51.55Mh/s a:72 r:0 hw:0
[2022-08-18 09:28:08] GPU 3 [46C, fan 90%] ethash: 41.48Mh/s, avg 40.94Mh/s, pool 40.10Mh/s a:56 r:1 hw:0
[2022-08-18 09:28:08] GPU 4 [51C, fan 90%] ethash: 55.90Mh/s, avg 55.25Mh/s, pool 37.96Mh/s a:53 r:0 hw:0
[2022-08-18 09:28:08] GPU 5 [41C, fan 70%] ethash: 62.28Mh/s, avg 61.80Mh/s, pool 52.29Mh/s a:73 r:1 hw:0
[2022-08-18 09:28:08] GPU 6 [45C, fan 70%] ethash: 62.32Mh/s, avg 61.88Mh/s, pool 62.32Mh/s a:87 r:0 hw:0
[2022-08-18 09:28:08] GPU 7 [45C, fan 90%] ethash: 56.87Mh/s, avg 56.28Mh/s, pool 53.73Mh/s a:75 r:0 hw:0
[2022-08-18 09:28:08] Total ethash: 452.3Mh/s, avg 447.7Mh/s, pool 429.7Mh/s a:600 r:3
[2022-08-18 09:28:08] ----------------------------------------- Pool Status ------------------------------------------
[2022-08-18 09:28:08] prohashing.com ethash: 451.0Mh/s, avg 442.8Mh/s, pool 429.5Mh/s a:600 r:3
[2022-08-18 09:28:08] ------------------------------------------------------------------------------------------------
[2022-08-18 09:28:08] Pool prohashing.com received new job. (job_id: 0x8c79353e3d3..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:09] Pool prohashing.com share accepted. (GPU4) (a:601 r:3) (101 ms) (diff 1.33 GH)
[2022-08-18 09:28:09] Pool prohashing.com share accepted. (GPU5) (a:602 r:3) (100 ms) (diff 19.58 GH)
[2022-08-18 09:28:09] Pool prohashing.com received new job. (job_id: 0x92abb0e29f1..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:09] Pool prohashing.com share rejected. (GPU1) Error code: -2 - Both primary and merge mined shares are stale
. (a:602 r:4u) (151 ms) (diff 22.58 GH)

[2022-08-18 09:28:09] Pool prohashing.com received new job. (job_id: 0x09dd363c0bd..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:10] Pool prohashing.com share accepted. (GPU3) (a:603 r:4) (95 ms) (diff 1.81 GH)
[2022-08-18 09:28:11] Pool prohashing.com share accepted. (GPU0) (a:604 r:4) (97 ms) (diff 3.77 GH)
[2022-08-18 09:28:12] Pool prohashing.com received new job. (job_id: 0x88f09eec426..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:15] Pool prohashing.com share accepted. (GPU5) (a:605 r:4) (410 ms) (diff 3.35 GH)
[2022-08-18 09:28:15] Pool prohashing.com received new job. (job_id: 0xd2bf104f9bf..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:17] Pool prohashing.com share accepted. (GPU4) (a:606 r:4) (97 ms) (diff 1.11 GH)
[2022-08-18 09:28:18] Pool prohashing.com received new job. (job_id: 0x77557191193..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:19] Pool prohashing.com received new job. (job_id: 0xe57ce068133..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:19] Pool prohashing.com received new job. (job_id: 0x517084e213e..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:19] Pool prohashing.com share accepted. (GPU4) (a:607 r:4) (97 ms) (diff 11.01 GH)
[2022-08-18 09:28:20] Pool prohashing.com share accepted. (GPU4) (a:608 r:4) (95 ms) (diff 1.17 GH)
[2022-08-18 09:28:22] Pool prohashing.com share accepted. (GPU5) (a:609 r:4) (94 ms) (diff 4.01 GH)
[2022-08-18 09:28:22] Pool prohashing.com received new job. (job_id: 0x67396672f6d..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:22] Pool prohashing.com received new job. (job_id: 0x5cace609a40..., diff 0.250 / 1074 MH)
[2022-08-18 09:28:22] Pool prohashing.com received new job. (job_id: 0x9fb1bc3dd90..., diff 0.250 / 1074 MH)


Another Stale moment:

2022-08-18 09:35:26] Pool prohashing.com received new job. (job_id: 0x2111bf9ee5f..., diff 0.250 / 1074 MH)
[2022-08-18 09:35:27] Pool prohashing.com share accepted. (GPU2) (a:805 r:8) (241 ms) (diff 4.18 GH)
[2022-08-18 09:35:27] Pool prohashing.com share accepted. (GPU4) (a:806 r:8) (102 ms) (diff 2.62 GH)
[2022-08-18 09:35:29] Pool prohashing.com received new job. (job_id: 0x59545ae526a..., diff 0.250 / 1074 MH)
[2022-08-18 09:35:30] Pool prohashing.com share accepted. (GPU4) (a:807 r:8) (304 ms) (diff 21.57 GH)
[2022-08-18 09:35:30] Pool prohashing.com share accepted. (GPU5) (a:808 r:8) (124 ms) (diff 4.94 GH)
[2022-08-18 09:35:32] Pool prohashing.com received new job. (job_id: 0x0057ce3f25d..., diff 0.250 / 1074 MH)
[2022-08-18 09:35:33] Pool prohashing.com share accepted. (GPU0) (a:809 r:8) (595 ms) (diff 1.17 GH)
[2022-08-18 09:35:35] Pool prohashing.com received new job. (job_id: 0xd4dcd4d47aa..., diff 0.250 / 1074 MH)
[2022-08-18 09:35:35] Pool prohashing.com received new job. (job_id: 0xafb089a8bba..., diff 0.250 / 1074 MH)
[2022-08-18 09:35:35] Pool prohashing.com share rejected. (GPU2) Error code: -2 - Both primary and merge mined shares are stale
. (a:809 r:9u) (138 ms) (diff 1.53 GH)

[2022-08-18 09:35:36] Pool prohashing.com received new job. (job_id: 0x0a15c46f4c4..., diff 0.250 / 1074 MH)
[2022-08-18 09:35:36] Pool prohashing.com share accepted. (GPU2) (a:810 r:9) (224 ms) (diff 1.14 GH)
[2022-08-18 09:35:38] ------------------------------------------------------------------------------------------------
[2022-08-18 09:35:38] Mining ethash with 8 GPU workers
[2022-08-18 09:35:38] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC Power ETH Cfg
[2022-08-18 09:35:38] 0 03:00.0 40 1080 950 910 45C 51C 70C 90.98% 3094 718 mV 89 W R600
[2022-08-18 09:35:38] 1 06:00.0 60 1100 872 1069 53C 58C 62C 76.86% 2541 656 mV 98 W R952
[2022-08-18 09:35:38] 2 0a:00.0 40 1080 950 910 47C 56C 76C 90.98% 3094 718 mV 73 W R608
[2022-08-18 09:35:38] 3 0d:00.0 36 950 950 895 46C 53C 74C 90.98% 3094 675 mV 80 W R576
[2022-08-18 09:35:38] 4 10:00.0 36 1100 950 910 51C 60C 80C 90.98% 3185 687 mV 84 W R576
[2022-08-18 09:35:38] 5 13:00.0 72 1100 1200 1069 42C 47C 58C 70.98% 2414 637 mV 94 W R1092
[2022-08-18 09:35:38] 6 16:00.0 80 1100 1200 1069 46C 47C 58C 70.98% 2414 643 mV 90 W R1280
[2022-08-18 09:35:38] 7 19:00.0 40 1080 1085 925 45C 57C 78C 90.98% 3094 718 mV 87 W R612
[2022-08-18 09:35:38]
[2022-08-18 09:35:38] Stats Uptime: 0 days, 00:32:34
[2022-08-18 09:35:38] ----------------------------------------- GPU Status -------------------------------------------
[2022-08-18 09:35:38] GPU 0 [45C, fan 90%] ethash: 55.93Mh/s, avg 55.45Mh/s, pool 66.62Mh/s a:121 r:0 hw:0
[2022-08-18 09:35:38] GPU 1 [53C, fan 76%] ethash: 61.62Mh/s, avg 61.13Mh/s, pool 60.57Mh/s a:110 r:3 hw:0
[2022-08-18 09:35:38] GPU 2 [47C, fan 90%] ethash: 55.93Mh/s, avg 55.44Mh/s, pool 58.38Mh/s a:106 r:1 hw:0
[2022-08-18 09:35:38] GPU 3 [46C, fan 90%] ethash: 41.48Mh/s, avg 41.07Mh/s, pool 40.76Mh/s a:74 r:2 hw:0
[2022-08-18 09:35:38] GPU 4 [51C, fan 90%] ethash: 55.90Mh/s, avg 55.40Mh/s, pool 49.57Mh/s a:90 r:0 hw:0
[2022-08-18 09:35:38] GPU 5 [42C, fan 70%] ethash: 62.27Mh/s, avg 61.92Mh/s, pool 53.99Mh/s a:98 r:1 hw:0
[2022-08-18 09:35:38] GPU 6 [46C, fan 70%] ethash: 62.32Mh/s, avg 61.99Mh/s, pool 62.81Mh/s a:114 r:1 hw:0
[2022-08-18 09:35:38] GPU 7 [45C, fan 90%] ethash: 56.87Mh/s, avg 56.42Mh/s, pool 53.45Mh/s a:97 r:1 hw:0
[2022-08-18 09:35:38] Total ethash: 452.3Mh/s, avg 448.8Mh/s, pool 446.1Mh/s a:810 r:9
[2022-08-18 09:35:38] ----------------------------------------- Pool Status ------------------------------------------
[2022-08-18 09:35:38] prohashing.com ethash: 442.5Mh/s, avg 444.0Mh/s, pool 446.0Mh/s a:810 r:9
[2022-08-18 09:35:38] ------------------------------------------------------------------------------------------------

Another one here...

Pool prohashing.com received new job. (job_id: 0x7ec6ccd99ea..., diff 0.250 / 1074 MH)
[2022-08-18 09:50:57] Pool prohashing.com received new job. (job_id: 0x9d2e552a130..., diff 0.250 / 1074 MH)
[2022-08-18 09:50:57] Pool prohashing.com received new job. (job_id: 0x582a2f3934d..., diff 0.250 / 1074 MH)
[2022-08-18 09:50:57] Pool prohashing.com share rejected. (GPU3) Error code: -2 - Both primary and merge mined shares are stale
. (a:1182 r:15u) (96 ms) (diff 1.25 GH)

[2022-08-18 09:50:57] Pool prohashing.com share accepted. (GPU3) (a:1183 r:15) (96 ms) (diff 1.68 GH)
[2022-08-18 09:50:59] Pool prohashing.com share accepted. (GPU0) (a:1184 r:15) (99 ms) (diff 2.97 GH)
[2022-08-18 09:50:59] Pool prohashing.com share accepted. (GPU3) (a:1185 r:15) (142 ms) (diff 1.35 GH)
[2022-08-18 09:51:00] Pool prohashing.com received new job. (job_id: 0x304cf1639

Seriously what gives?
Baseball and Mining. HaCkint0sh and Crypto. Magic Lantern never dies! :geek:
User avatar
Sarah Manter
Posts: 639
Joined: Fri Aug 13, 2021 11:15 am
Contact:

Re: All of a sudden the reject share rate went up rapidly...

Post by Sarah Manter » Thu Aug 18, 2022 1:22 pm

DeafEyeJedi wrote: Thu Aug 18, 2022 12:23 pm
Sarah Manter wrote: Thu Aug 18, 2022 6:34 am Hello, can you please put in an official support ticket so that I can pass it on to the engineers?
Absolutely. Do I just go to the discord live channel or where do I find the support ticket requests? Thanks!
Thank you. You can click one of the support options at the top right of the forums, but the best way is always to click the support button in the footer of the website. If you haven't submitted one already, you may have to wait a few minutes if you go that route because we're in the process of upgrading the website right now.
User avatar
DeafEyeJedi
Posts: 32
Joined: Wed May 25, 2022 11:38 pm
Location: USA

Re: All of a sudden the reject share rate went up rapidly...

Post by DeafEyeJedi » Thu Aug 18, 2022 1:38 pm

Sarah Manter wrote: Thu Aug 18, 2022 1:22 pm
DeafEyeJedi wrote: Thu Aug 18, 2022 12:23 pm
Sarah Manter wrote: Thu Aug 18, 2022 6:34 am Hello, can you please put in an official support ticket so that I can pass it on to the engineers?
Absolutely. Do I just go to the discord live channel or where do I find the support ticket requests? Thanks!
Thank you. You can click one of the support options at the top right of the forums, but the best way is always to click the support button in the footer of the website. If you haven't submitted one already, you may have to wait a few minutes if you go that route because we're in the process of upgrading the website right now.
Excellent. Email sent. Thank you again and I look forward to getting this resolved.
Baseball and Mining. HaCkint0sh and Crypto. Magic Lantern never dies! :geek:
User avatar
Sarah Manter
Posts: 639
Joined: Fri Aug 13, 2021 11:15 am
Contact:

Re: All of a sudden the reject share rate went up rapidly...

Post by Sarah Manter » Thu Aug 18, 2022 1:57 pm

DeafEyeJedi wrote: Thu Aug 18, 2022 1:38 pm
Sarah Manter wrote: Thu Aug 18, 2022 1:22 pm
DeafEyeJedi wrote: Thu Aug 18, 2022 12:23 pm

Absolutely. Do I just go to the discord live channel or where do I find the support ticket requests? Thanks!
Thank you. You can click one of the support options at the top right of the forums, but the best way is always to click the support button in the footer of the website. If you haven't submitted one already, you may have to wait a few minutes if you go that route because we're in the process of upgrading the website right now.
Excellent. Email sent. Thank you again and I look forward to getting this resolved.
Thank you. Forwarded on to Vance.
Post Reply