Incorrect worker #s

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.

Dankfrank wrote: 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.

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.

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.

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.