Quote from: bark0de on December 20, 2013, 03:02:14 PM

Quote from: mobile on December 20, 2013, 01:46:36 AM

Quote from: midniteslide on December 19, 2013, 11:23:03 PM

Quote from: bark0de on December 19, 2013, 11:02:23 PM

Quote

What power supply are you running?
What mining program are you running & stratum proxy?
Any other relevant information you could share? Like, what is the LED doing? What does the web interface tell you.
What do you mean they "restart". I assume they continue to run in standby mode? If you prefer to keep this on the public board. feel free to quote this and reply back on the board. cheers.

My power supply is a Corsair CX800
I am connecting the blade and the cube via slush's proxy (since I can't seem to get the BFGminer proxy to work right)
I have tried both slush's pool and BTCGuild (i prefer BTCGuild)
They blade and cube are properly cooled in a server room with dedicated AC kept at 60 degrees F and fans blowing directly on them
They are connected directly to a dedicated DSL line (not the best, but I chose to do it this way because it bypasses my company firewall)

I haven't actually sat to observe the status LED, but I just went down now to check it out and I just see it blinking repeatedly.

They will hash fine for about 10 minutes and then they just suddenly stop receiving work. When this happens, I see on the mining proxy that it stops showing the messages where it shows the username for the blade and the username for the cube doing work, and it only shows messages like "new job xxxxxx" which seems to me like the proxy is still requesting jobs from the pool, but it's just not passing it to the ASICs for some reason.

On the web config, I notice that the running time for both the blade and the cube are always the same, meaning that they are restarting themselves at the exact same time.

My blade is the new blade model. My cube is from CanaryInTheMine's most recent batch.

I hope this is enough information

Is your IP for the proxy static?

My initial thought was this, something related to a networking issue. But he stated that the hardware is actually restarting themselves.see below.

Quote from: bark0de on December 19, 2013, 11:02:23 PM

On the web config, I notice that the running time for both the blade and the cube are always the same, meaning that they are restarting themselves at the exact same time.

But the thing is, if the hardware is rebooting itself, why isnt the software picking them back up again and relaying work to them. Strange.

bark0de, you mentioned that you couldnt get BFGMiner to work properly. I found it to be easier set up wise.If you are running windows PC
Have you tried passing this --->

Code:

--http-port 8330

in the target area. For example, on the gui I right click the gui and in the target area at that script

Code:

C:\mine\bfgminer-3.8.0-win32\bfgminer.exe --http-port 8330

and work from there, later saving to config file (forgive me if your way past this step and/or running linux.

Then again, maybe your better off with slushes proxy because I am still wondering if BFGMiner is responsible for my "Long Poll: inactive" question

The IP of the machine running the proxy is static (192.168.1.50) and the IP of the miners are static (192.168.1.100 and 192.168.1.101), and there is nothing else on this network. The entire network is just 1 laptop, 2 miners, a small switch (which I tried replacing already to rule that out), and a DSL modem which acts as the router.

Yes, the hardware is rebooting itself, but to answer your question, the proxy does eventually pick it back up and it starts to mine again automatically. But these constant disconnects are keeping my average hash rate much lower than what it should be.

When I run bfgminer I get a strange message which sates "Pool 0 is hiding blocks from us" and then BFGMiner closes. I am running it with these command line switches:
bfgminer.exe --http-port 8332 -o http://stratum.btcguild.com:3333 -u bark0de_proxy -p x

I execute this via a batch file which I run from the same directory as BFGminer.

I reached out to CanaryInTheMine and he told me that the miners are hardcoded to reboot themselves if they stop receiving work for a while. The question is, why do they stop receiving work?

When the miners stop getting work, I check the proxy console and I see that it stops showing the really fast messages that say " Submitting ####### from bark0de_cube accepted" and it only shows messages that say something like "new job #######" i forget what exactly it says, but basically it stops mentioning the ASICs and seems to just show messages that say something to the effect of "I just got another job from the pool and I am waiting for a worker to take this job"

Thanks for your help. I hope someone can help me get to the bottom of this

I had a very similar issue. It ended up being network hardware related. Try bringing your proxy machine and cube to a friend's house and connecting there.