bobbywvz
Newbie
Offline
Activity: 35
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 03:46:56 AM |
|
My miner keeps restarting after around 2.5 minutes of running saw earlier in this thread that it is due to the proxy server and searching for work? How do you fix this though?
|
|
|
|
Damnsammit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 03:50:47 AM |
|
My miner keeps restarting after around 2.5 minutes of running saw earlier in this thread that it is due to the proxy server and searching for work? How do you fix this though?
Post up your settings and batch file that starts the proxy miner. That's the easiest way for us to help ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
bobbywvz
Newbie
Offline
Activity: 35
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:07:09 AM |
|
Thanks again sammit, the 12v 30a fuse must have worked to atleast get me to have it hash for a few minutes then restart, once this is fixed hopefully I can get up to a full 38 haha
Info is below
Clock high
IP 192.168.1.254 MASK: 255.255.255.0 Gateway 0.0.0.0 Web Port 8000 Primary DNS 192.168.1.1 Secondary DNS 8.8.8.8 Pool Ports 8332,3333 Pool Addresses 192.168.1.6;192.168.1.6
.bat mining_proxy.exe -o stratum.btcguild.com -p 3333
|
|
|
|
brush242
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:30:33 AM |
|
Thanks again sammit, the 12v 30a fuse must have worked to atleast get me to have it hash for a few minutes then restart, once this is fixed hopefully I can get up to a full 38 haha
Info is below
Clock high
IP 192.168.1.254 MASK: 255.255.255.0 Gateway 0.0.0.0 Web Port 8000 Primary DNS 192.168.1.1 Secondary DNS 8.8.8.8 Pool Ports 8332,3333 Pool Addresses 192.168.1.6;192.168.1.6
.bat mining_proxy.exe -o stratum.btcguild.com -p 3333 Well, for one, I think your Pool Ports need to match, e.g., 8332,8332. And, while the OP doesn't do it, Gateway and Primary DNS should match. Both should say 192.168.1.1. And, well, I would assume that btcguild needs "-u <user.worker>" and "-p <password>" in the .bat file. Try those.
|
Support sidehack miner development. Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
|
|
|
twib2
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 280
Merit: 250
Helperizer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:31:01 AM |
|
My miner keeps restarting after around 2.5 minutes of running saw earlier in this thread that it is due to the proxy server and searching for work? How do you fix this though?
If you have several computers or active IP machines on your subnet, try this: - Set the first pool address and first miner:pass to the correct place you are serving up proxied work - Set the second pool address to any other machine in your network that is NOT running a proxy (user:pass has to still be there, but the values don't matter). You might just be able to keep everything the same and choose any other port that is not serving as a proxy, too. What will happen is that the Cube will search for work, try the other pool, and bounce back to the first one without getting "confused/stuck-on-stupid" and rebooting. You keep hashing, and save a lot more hash than constantly restarting. This works for any single-instance of proxies you might have. Another solution that works only for slush's stratum proxy is to run 2 separate stratum proxies yourself and put them both on each cube. When the cube searches for work, it will go back and forth between the two with nary a hiccup. This second approach does not work for bfgminer proxies since the bfgminer proxy is managed and expects non-sick clients whereas slush's proxy is more "dumb" and just "speaks when spoken to." Anyway, this worked great for me so I hope it helps! Best, - Tye
|
|
|
|
twib2
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 280
Merit: 250
Helperizer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:33:23 AM |
|
Thanks again sammit, the 12v 30a fuse must have worked to atleast get me to have it hash for a few minutes then restart, once this is fixed hopefully I can get up to a full 38 haha
Info is below
Clock high
IP 192.168.1.254 MASK: 255.255.255.0 Gateway 0.0.0.0 Web Port 8000 Primary DNS 192.168.1.1 Secondary DNS 8.8.8.8 Pool Ports 8332,3333 Pool Addresses 192.168.1.6;192.168.1.6
.bat mining_proxy.exe -o stratum.btcguild.com -p 3333 Well, for one, I think your Pool Ports need to match, e.g., 8332,8332. And, while the OP doesn't do it, Gateway and Primary DNS should match. Both should say 192.168.1.1. Try that. Yep, most definitely need to have an accurate gateway address and not some dummy numbers like 0.0.0.0! Ports don't need to match if you use my anti-cube/blade-restarting solution as above, but then of course you will simply fail back to the primary side.
|
|
|
|
bobbywvz
Newbie
Offline
Activity: 35
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:38:15 AM |
|
Awesome! Thanks for the help, yeah don't know if the numbers I gave you were completely accurate (my cube is at the parents house) hopefully trying your methods above should do the trick! You guys rock ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
|
babaji.ca
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:41:39 AM |
|
0.01 BTC if someone will resolve my problem before 23.00 UTC of 02/01/2014
I have a big problem: i'm trying to fire up a cube, i have a coolermaster v700 (58A on the 12v rail), with the fuse the miner start and after a few second it shutdown, without the fuse the miner starts but the leds are all off and also if i try to navigate on 192.168.1.254:8000 the browser doesn't load anything...
If the cube shutdown within 1-2sec after powering up, your PSU probable got overloaded by the surge in the current draw. Try with a different PSU if you have. but only with the fkn fuse ![Angry](https://bitcointalk.org/Smileys/default/angry.gif) It's the power supply. I had the exact same problem with 3 cubes, many others here in this thread same, problem, usually with a Seasonic and also with some of the Corsair's with an "X' in the model name. Usually a rebadged Seasonic. It would run for 1.75 seconds then die once turned on or once the fuze was inserted. Don't waste your time openeing up(well you can check that everything is tight and the cards are in their slot) , it is not the reason for the problem you are having now. If you go back in the thread you can see there is a solution by putting some Capacitors in line with the power at the back of the cube, but it is a pain in the ass and can be fiddly. The two power supply's i have tested and are good to power 2 cubes at a time are the Corsair GS 800 and the thermaltake 840. Both worked fine for me. My Seasonic 1050w was a royal pain in the ass.
|
|
|
|
brush242
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:45:19 AM |
|
Yep, most definitely need to have an accurate gateway address and not some dummy numbers like 0.0.0.0!
Ports don't need to match if you use my anti-cube/blade-restarting solution as above, but then of course you will simply fail back to the primary side. Brush242: Tye "twib2", you are a ~madman~. When you stole that cow, and your friend tried to make it with the cow. I want to party with you, cowboy. The two of us together, forget it. I'm gonna go out on a limb here. I'm gonna volunteer twib2's leadership to this platoon. An army without leaders is like a foot without a big toe. And Sergeant Hulka isn't always gonna be here to be that big toe for us. I think that we owe a big round of applause to our newest, bestest buddy, and big toe...Twib2
|
Support sidehack miner development. Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
|
|
|
babaji.ca
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:50:09 AM |
|
Thanks again sammit, the 12v 30a fuse must have worked to atleast get me to have it hash for a few minutes then restart, once this is fixed hopefully I can get up to a full 38 haha
Info is below
Clock high
IP 192.168.1.254 MASK: 255.255.255.0 Gateway 0.0.0.0 Web Port 8000 Primary DNS 192.168.1.1 Secondary DNS 8.8.8.8 Pool Ports 8332,3333 Pool Addresses 192.168.1.6;192.168.1.6
.bat mining_proxy.exe -o stratum.btcguild.com -p 3333 Well, for one, I think your Pool Ports need to match, e.g., 8332,8332. And, while the OP doesn't do it, Gateway and Primary DNS should match. Both should say 192.168.1.1. And, well, I would assume that btcguild needs "-u <user.worker>" and "-p <password>" in the .bat file. Try those. Actually the numbers don't always have to match.... You could have two stratum servers running, a primary and a backup on the same or different machines with different port numbers configured.
|
|
|
|
twib2
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 280
Merit: 250
Helperizer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 05:13:52 AM |
|
Brush242: Tye "twib2", you are a ~madman~. When you stole that cow, and your friend tried to make it with the cow. I want to party with you, cowboy. The two of us together, forget it.
I'm gonna go out on a limb here. I'm gonna volunteer twib2's leadership to this platoon. An army without leaders is like a foot without a big toe. And Sergeant Hulka isn't always gonna be here to be that big toe for us. I think that we owe a big round of applause to our newest, bestest buddy, and big toe...Twib2
Well, okay, hotshot. We're gonna see what kind of soldier you are.
|
|
|
|
|
otsaku
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 78
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 10:35:21 AM |
|
Can you show us the Cube's status page, and the contents of your .bat file?
http://bayimg.com/PaFDpAaFNI don't have a bat file, I'm running the proxy on a mac. mining_proxy.py -o mint.bitminter.com -p 3333 or 443 or 5050
|
|
|
|
Apteryx
Newbie
Offline
Activity: 36
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 11:05:02 AM |
|
Enough of the doom and gloom
With the help of this forum, I managed to setup a cube and have it running in under 10 mins
after 57minutes uptime it is running 97.42% @ 32,160 MHS.
This is after disassembling and tightening the heat sinks (most were loose) and reseating the blades (several were misaligned).
Cube is running all 0's on low speed (will let it bed in for 24hrs or so b4 I overclock)
Next stage is to setup the stratum proxy on a rasberry PI, again, with the help of this forum.
I thank you all
|
|
|
|
otsaku
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 78
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 12:32:49 PM |
|
Why does the cube have to be connected to the router - isn't it possible to connect it via ethernet to a computer , either my mac or raspberry pi and have it share the wifi internet connection?
|
|
|
|
alexrossi
Legendary
Offline
Activity: 3836
Merit: 1745
Join the world-leading crypto sportsbook NOW!
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 01:50:20 PM |
|
0.01 BTC if someone will resolve my problem before 23.00 UTC of 02/01/2014
It's the power supply. I had the exact same problem with 3 cubes, many others here in this thread same, problem, usually with a Seasonic and also with some of the Corsair's with an "X' in the model name. Usually a rebadged Seasonic. It would run for 1.75 seconds then die once turned on or once the fuze was inserted. Don't waste your time openeing up(well you can check that everything is tight and the cards are in their slot) , it is not the reason for the problem you are having now. If you go back in the thread you can see there is a solution by putting some Capacitors in line with the power at the back of the cube, but it is a pain in the ass and can be fiddly. The two power supply's i have tested and are good to power 2 cubes at a time are the Corsair GS 800 and the thermaltake 840. Both worked fine for me. My Seasonic 1050w was a royal pain in the ass. Changed the psu and now everything is working well! Thank you!!!Drop me an address
|
|
|
|
otsaku
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 78
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 02:18:15 PM Last edit: January 03, 2014, 02:53:28 PM by otsaku |
|
Can you show us the Cube's status page, and the contents of your .bat file?
http://bayimg.com/PaFDpAaFNI don't have a bat file, I'm running the proxy on a mac. mining_proxy.py -o mint.bitminter.com -p 3333 or 443 or 5050 if I point the cube directly at bitminter on port 8332 or 80, it connects and tries and gives me a hashrate of 2.9 ghs... So the problem is deifinitely with the proxy. I've now got the mining proxy running on a RPi with the same result as when it's running on a mac. I've turned off the wifi on the RPi and plugged it into the router as well without any effect. Now going to try and give the cube an ip outside of the dhcp range Changed the ip from 192.168.1.153 to 192.168.1.200, pointed the cube at the proxy on the RPi and it has started receiving work from bitminter. But only appears to be running three blades at 5ghs... ASIC_01-16: O O O O O O O O O O O O O O O O ASIC_17-32: O O O O O O O O O O O O O O O O ASIC_33-48: O O O O O O O O O O O O O O O O ASIC_49-64: O O O O O O O O O O O O O O O O ASIC_65-80: O O O O O O O O O O O O O O O O ASIC_81-96: O O O O O O O O O O O O O O O O M_01-16: 081 180 147 016 147 065 196 049 131 163 180 196 376 245 212 081 M_17-32: 032 147 180 114 131 065 327 081 065 065 245 196 147 147 049 049 M_33-48: 180 049 065 098 065 098 049 114 000 000 000 000 000 000 000 000 M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 Jobs:0000000598 Accepted:0000000320 Rejected:0000000002 (0:4) F1 F2 F3 MHS:05242 Utility:072 Efficieny:053.51%
|
|
|
|
twib2
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 280
Merit: 250
Helperizer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 03:15:34 PM |
|
Can you show us the Cube's status page, and the contents of your .bat file?
http://bayimg.com/PaFDpAaFNI don't have a bat file, I'm running the proxy on a mac. mining_proxy.py -o mint.bitminter.com -p 3333 or 443 or 5050 if I point the cube directly at bitminter on port 8332 or 80, it connects and tries and gives me a hashrate of 2.9 ghs... So the problem is deifinitely with the proxy. I've now got the mining proxy running on a RPi with the same result as when it's running on a mac. I've turned off the wifi on the RPi and plugged it into the router as well without any effect. Now going to try and give the cube an ip outside of the dhcp range Changed the ip from 192.168.1.153 to 192.168.1.200, pointed the cube at the proxy on the RPi and it has started receiving work from bitminter. But only appears to be running three blades at 5ghs... ASIC_01-16: O O O O O O O O O O O O O O O O ASIC_17-32: O O O O O O O O O O O O O O O O ASIC_33-48: O O O O O O O O O O O O O O O O ASIC_49-64: O O O O O O O O O O O O O O O O ASIC_65-80: O O O O O O O O O O O O O O O O ASIC_81-96: O O O O O O O O O O O O O O O O M_01-16: 081 180 147 016 147 065 196 049 131 163 180 196 376 245 212 081 M_17-32: 032 147 180 114 131 065 327 081 065 065 245 196 147 147 049 049 M_33-48: 180 049 065 098 065 098 049 114 000 000 000 000 000 000 000 000 M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 Jobs:0000000598 Accepted:0000000320 Rejected:0000000002 (0:4) F1 F2 F3 MHS:05242 Utility:072 Efficieny:053.51% Glad to see it's hashing. Now that it's doing that but only with three blades, I've only seen this under a few circumstances: 1) Powersupply is too weak, regardless of what the numbers say (some are sensitive to initial draw, etc) 2) Some blades aren't seated properly and/or are running too hot - if you haven't already, open it up, tighten the heatsink screws and reseat the blades solidly. 3) (rarely) Cube is simply "confused" and clicking on the Update button on bottom right can restart it
|
|
|
|
bobbywvz
Newbie
Offline
Activity: 35
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 03:30:16 PM |
|
I blew my fuses as well because the ones that came with mine were 32V. Once I purchased 12V 30A ones I was fine. Just my two cents, hope that helps!
|
|
|
|
Damnsammit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 03, 2014, 04:23:35 PM |
|
I blew my fuses as well because the ones that came with mine were 32V. Once I purchased 12V 30A ones I was fine. Just my two cents, hope that helps!
They sent you 32V fuses with your Cube?! Man, no wonder you blew them both.
|
|
|
|
|