 |
April 12, 2013, 08:20:36 PM |
|
I noticed my curiously dropping Hash rate on Deepbit, and when I went to check the machines I'd set up to mine for me, I saw that they all conspicously shared the same error saying the "job was finished" and went idle.
Job was certainly not finished. I stopped receiving shares 3 hours ago because of these miners going idle without warning and had no clue, nor have I ever experienced this sort of error before. I should be running at least 900 because of the number of machines I have access too, but currently am sitting on a whopping 0.00 with "workers not connected" stamped nice and red on Deepbit for me.
What's equally confounding is the lack of support the miner gives you to alleviate such problems, so I'm glad we have this forum: how do I tackle this belligerently annoying "job finished" error?
*None of my rigs have the bitcoin client installed, they are connected to my DeepBit pool which I monitor from an ancient laptop that actually has my wallet*
|
