possible equihash mining issue

GregoryGHarding
Archived posts: 630
Joined: Apr 16, 2017

possible equihash mining issue

by GregoryGHarding · · Post #17262

throughout the day il pop in on my console and babysit my GPU rig for a bit, several times i see the following error:

Code:

03/19/18-22:57:57 - SHARE FOUND - (GPU 4)
Share accepted (109 ms)!
No new jobs were received for 12 mins - something wrong with the pool, disconnect.
Stratum - connecting to 'prohashing.com' port 3333 (unsecure)
seems as if randomly work is not getting passed to the client and has to drop connection and reconnect to be issued work.

thoughts?
zafar177
Archived posts: 55
Joined: Aug 21, 2017

Re: possible equihash mining issue

by zafar177 · · Post #17264

I also am getting random disconnects for my equihash miner. In order to reconnect I have to restart the miner. Unfortunately I have no monitoring software and therefore I am unable to assess how often this happens forcing me to randomly check during the day.
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: possible equihash mining issue

by Steve Sokolowski · · Post #17274

GregoryGHarding wrote:throughout the day il pop in on my console and babysit my GPU rig for a bit, several times i see the following error:

Code:

03/19/18-22:57:57 - SHARE FOUND - (GPU 4)
Share accepted (109 ms)!
No new jobs were received for 12 mins - something wrong with the pool, disconnect.
Stratum - connecting to 'prohashing.com' port 3333 (unsecure)
seems as if randomly work is not getting passed to the client and has to drop connection and reconnect to be issued work.

thoughts?
From what I read, there's nothing we can do about this problem.

The coin network that we're mining, in this case, has long block times, and no block was found within 12 minutes. Your software is configured to disconnect after no new jobs were sent within 12 minutes, and it should not be doing that because the current work is still valid.

I'll see if there's anything we can do, but the best solution is to find a configuration setting to disable this feature in the mining software.