Topic: [Guide] Dogie's Comprehensive ASICMiner Cube Setup [HD] - page 50. (Read 187363 times)

How did you set up your proxy. I tried and got the same result as not using a proxy.

I had my cube working yesterday using a 600 watt psu. I needed to change the worker information so after changing the info, I clicked refresh. Then I got all x's. So I shut off the psu and restarted it after a few minutes, now I am getting all o's but when I try to connect to the server using my bat file I get


E:\Users\john2\Downloads\Software\bfgminer\bfgminer-3.4.0-win32>mining_proxy.exe
 -o us1.ghash.io -p 3333 -gp 8332
E:\Users\john2\Downloads\Software\bfgminer\bfgminer-3.4.0-win32\mining_proxy.exe
\twisted\web\util.py:372: DeprecationWarning: Passing filenames or file objects
to XMLFile is deprecated since Twisted 12.1.  Pass a FilePath instead.
2014-01-11 11:47:31,888 INFO proxy jobs. # C extension for midstate not
available. Using default implementation instead.
2014-01-11 11:47:31,890 WARNING proxy mining_proxy.main # Stratum proxy version:
 1.5.2
2014-01-11 11:47:31,892 WARNING proxy mining_proxy.test_update # Checking for up
dates...
2014-01-11 11:47:32,571 WARNING proxy mining_proxy.main # Trying to connect to S
tratum pool at us1.ghash.io:3333
2014-01-11 11:47:32,793 INFO stats stats.print_stats # 1 peers connected, state
changed 1 times
2014-01-11 11:47:32,795 INFO proxy mining_proxy.on_connect # Connected to Stratu
m pool at us1.ghash.io:3333
2014-01-11 11:47:32,795 INFO proxy mining_proxy.on_connect # Subscribing for min
ing jobs
2014-01-11 11:47:33,009 WARNING proxy mining_proxy.main # ----------------------
-------------------------------------------------
2014-01-11 11:47:33,009 WARNING proxy mining_proxy.main # PROXY IS LISTENING ON
ALL IPs ON PORT 3333 (stratum) AND 8332 (getwork)
2014-01-11 11:47:33,009 WARNING proxy mining_proxy.main # ----------------------
-------------------------------------------------
2014-01-11 11:47:33,426 INFO proxy client_service.handle_event # Setting new dif
ficulty: 16
2014-01-11 11:47:33,427 INFO proxy client_service.handle_event # New job 63ac594
5 for prevhash cb2c94fa, clean_jobs=False

I have tried 3 different power supplies -- 500, 600 and 800 watt, and the result is the same.  Why does it work one day and then completely stop working the next day.  I swear this was the worst investment that I have made since I got into mining.

Isn't the port supposed to be 8332? You have 8334. Perhaps that is the problem.

Need Help Please:

Set up my first Cube on Monday. It hashed away no problem until today it shutdown. I also received Cube #2 yesterday and set up. Both were working fine all night and this morning.

Got home and both cubes were shutdown and both went down at the same time. I figured out what caused them to shutdown. It was my network IP address changed. Not sure why but I am looking into that. The issue Cube 2 I finally got up and running. Cube 1 however is showing all X's. I have taken it apart and made sure everything is seated properly and tightened down the heatsinks (many were loose) put it all back together and still all X's. I even changed out PSU. One thing I forget to include I am running each cube on their own PSU. I have stuck any suggestions would greatly be appreciated.
PSU 1: Corsair 600w
PSU 2: Apex 500w

I had the same issue with my three cubes, one or two of them randomly shuts off. My impression is that the cube is kind of sensitive to the power supply. Well, I tried a couple of power supplies I had to power one cube (up to 750W, don't remember the brand), while none work until I bought this one: Cooler Master Silent Pro Gold - 1200W Power Supply with 80 PLUS Gold Certification and Semi-Modular Cables. So this should be powerful and enough for three cubes, as they are designed to be only 600W in total (without overclock). This did work for some time (two weeks or so), then it won't. Sounds very strange to me. Ok, this is what happed. I can start three cubes when power on and they last maybe a couple of minutes. I can find them through subnetwork, showing that they are active. After that, one stops to mine (cannot find it anymore), luckly another one stops as well. When two are working, I re-plug the wire of the third (pull out and in), so it starts working (the red LED blinking); however, one of the two immediatesly stops (red LED gone and never come back), once the third is up and runs. From this experiment, I do think this a kind of power supply problem. Either the power supply becomes worse (unlikely to me, since it can still support two overclocked), or the cubes consume more power (my impression is that it stablizes at the factory value but there is temporary a higher power consumption at a very short period). Not sure about this. Anyway, I'll try to power on the third one when my new ordered power supply arrives soon. By the way, cubes runs in 192.168.0.x; I'll try 192.168.1.x and see any differences.

Houston we have a problem.
My Blade is tossing up XXXXXXXX
I wont get into too many details but this blade was sold working, user couldnt get it to work sent back and now its showing me all XXXXX.
http://s14.postimg.org/c2bajzmnl/XXX.png
Its a V2
Anything I can do / test.
I am using a PS setup that works with another V2 blade.

I just wanted to chime in here about the long polling/restarting issue some people have been having. My cube worked fine on one network. When I moved it to a different location/network, I started having the same problem. This is a network problem. I haven't been able to determine what exactly the problem is or how to correct it in my situation, but I do have a kludgie work around that got my cube up and mining again by using two different proxy machines as primary and backup.

The cube mines for a little while, gets stuck on the one proxy, fails over to the other proxy, mines for a little while, and back and forth. It takes a bit of a performance hit this way, but it's currently the only way I can get the thing to mine on the network it's currently on. Hope this helps...

I told you I'm glad you fixed it !

i'm still getting reboot after 2min

can you explain what you added to your configuration to get it finally hashing



EDIT:

FIXED

The reason was the switch and also the router.

I hooked the CUBE and the Laptop to a "TP-LINK POE Switch" and it immediately start mining as expected. I guess the reboot comes from a watch dog which reboots when it fails to mine.

Of course the POE function of the switch is useless but at least the switch enables the Miner to mine.

A little follow-up...
Removed the other miners, swapped the cables it's using to what another miner was using, still going half-off after a couple minutes...very annoying!

So not sure at all what's up with this right now. May have to take it apart and dig in further beyond the brief looks I gave earlier.

My Kill-A-Watt says something like 340 W for OC'd and I think I remember 260 W for non-OC'd - and besides not all 860W are on the 12V rails (sometimes it's only 75% of the total rating!), and the ratings are max, not constant-draw.  But it's more than that, these things are persnickety - first thing after configuration settings and physically ensuring heatsinks and blades are properly installed, IMHO, should *always* be to ensure that the problems still replicate with no way for power to be part of the problem.  Second thing is to do the same for network "cleanliness" (i.e. nothing on your subnet but the miner and its proxy).  If the problems still persist, then it could certainly be something with your hardware or setup that you missed.

Don't the cubes pull 200w each? (These are NON-oc'd, OCing them, even with JUST the 2 on the PSU and they go all X's after about 30-60 minutes). So that's 400. And the BFL miner shouldn't be THAT much (the PSU previously ran 3 cubes, until surprise surprise the BFL PSU died) but who knows maybe my math is way wrong. So I have a new PSU coming in the next day or so but I'm not convinced this is a power delivery thing...but then maybe it is and my issues will all go away in a day when I get another PSU to hook things up to.

Aha.  That's definitely your problem - for the configuration page, you're supposed to give it the IP of the machine running your proxy, the port you give it is your proxy's port (by default it's 8332 unless you set it with the "-gp" switch as I described above.  I don't have the pics/page handy but there are plenty of posts here explaining EXACTLY what to put into each field of the cube configuration page.   You definitely HAVE to get that stuff right, or it just won't work - that's the info it needs to know for communication.

All the info you need is in the OP:  https://bitcointalk.org/index.php?PHPSESSID=vd5gt0c3htsfgm4opne7okoom5&topic=352658.0

I think my problem is in the parameters to be included on the cube's configuration page.
I do not know the IP address of coinex.ps to be included in the field addresses Pool, the Pool ports do not know if I should put the money which ones I'm looking for or is the port where my cube is connected?

That's a lot on just one 860 W PSU.  I have a 850 that won't power two cubes just on its own.  Keep in mind that not all cubes have the same sensitivity to power.  My first question would be that if it's the same cube always, does it still doe that if you put the other cube on its own PSU?

Ok this is not the fuse, I also unplugged the working one, it still shuts off. I will try to replace the fan...

For Windows, just replace the "python mining_proxy.py" part above with "mining_proxy.exe".  The parts that follow are the command switches for how to run that executable.  You can either create a shortcut and mofify in the shortcut, or you can creat a runproxy.bat file with that command in there.

I don't know what you mean by "in the text file inside the folder where there is the mining_proxy" - in mine, there are multiple text files.  Again, what I gave you is the command for how to invoke the mining_proxy.exe exectutable file.  There's more info on slush's pool about how to set up and use the proxy if you like, but I think there might be a language difficulty here, or perhaps you are unfamiliar with how to run and configure executables?

Having absolutely the same issue... I replaced the fuse, wait & see...

I've been having a weird issue where one of my cubes randomly shuts "off"
I say off in quotes because it's still getting some power, but only 1 of the 2 power lights will be on (the 2 vertically stacked, the top stays on) and the fan continues to blow, but it pushes cold air and the device doesn't hash or respond to web requests. I can then un-plug and re-plug one of the 2 plugs (doesn't matter which) and it magically whirs to life again, for some random amount of time.

I have 2 cubes (and 1 BFL miner, no oc, total power should be < 700w) running of a Corsair AX860i, and it's always the same cube having the issue so I don't think it's a power issue. The fuse looks fine and I don't see anything wrong looking at the board.

Anyone else have this problem?

I use windows 7.
settings that you wrote to me I have to enter them in the text file inside the folder where there is the mining_proxy, right?
I have to change settings on the cube's configuration page?