Incorrect worker #s

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
Dankfrank
Posts: 1
Joined: Mon Nov 01, 2021 3:17 pm

Incorrect worker #s

Post by Dankfrank » Mon Nov 01, 2021 3:20 pm

I've seen this question asked on the forum, but I'm not finding a definitive answer. I only have 1 miner running but #prohashing's "mining" dashboard is reporting 2 workers. Is this something to be concerned about, or nothing to see here?

Thanks in advanced.
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Incorrect worker #s

Post by Steve Sokolowski » Mon Nov 01, 2021 3:47 pm

Dankfrank wrote: Mon Nov 01, 2021 3:20 pm I've seen this question asked on the forum, but I'm not finding a definitive answer. I only have 1 miner running but #prohashing's "mining" dashboard is reporting 2 workers. Is this something to be concerned about, or nothing to see here?

Thanks in advanced.
This is a known issue that affects some customers, but nobody here has ever been able to reproduce it. Without being able to reproduce it, we can't determine its cause.
awb1
Posts: 18
Joined: Mon Aug 16, 2021 10:24 am

Re: Incorrect worker #s

Post by awb1 » Mon Nov 01, 2021 4:38 pm

I see this sometimes as well - I am using simple mining os and it usually happens whenever I restart a worker using a different password - but it doesn't always happen either. I do tend to see it more using ethash-lowmemory though.
User avatar
Mastermind007
Posts: 109
Joined: Wed Aug 25, 2021 2:02 pm

Re: Incorrect worker #s

Post by Mastermind007 » Mon Nov 01, 2021 6:37 pm

I have run into this from time to time. The phantom worker usually goes away and it has never caused an issue with mining or payouts.
I just assumed it was a browser cache issue or perhaps the server just finishing up something like clearing a share backlog.
robinsoz
Posts: 25
Joined: Wed Jan 16, 2019 10:05 am

Re: Incorrect worker #s

Post by robinsoz » Mon Nov 01, 2021 11:26 pm

I have seen it from time to time. It happens with my xmrig miners when they switch over to donate mode and then switch back. I think the system creates a new worker when the worker creates a new connection not knowing that the previous connection has closed. It could have even have something to do with something like a worker connecting through NAT and using a new TCP return port, creating a new TCP connection.
Locked