Current C
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 19, 2013, 10:43:32 PM |
|
Hi,
I have two version 2 blades. i have only one connected via ethernet as I am attempting to set it up at the moment. I can access it through my browser when powered on. I have proper cooling and mounting setup already as well as the molex cables to my corsair power supply with ample amperage available.
I cannot figure out how to get stratum working on my ubuntu 12.04 machine. I would really appreciate some help.
I have downloaded the mining proxy. I don't know what to do after this. I have attempted using the sudo (super user do) commands to install python. I am lost.
Please help.
|
|
|
|
Current C
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 20, 2013, 01:16:48 AM |
|
update i believe i have stratum working. now im trying to login to the slush pool, but for some reason its just forcing me to reset my password.
|
|
|
|
Current C
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 20, 2013, 02:08:00 AM |
|
ok, i most certainly do not have the stratum working correctly. I can login to slushes pool without any issue now. can anyone walk me through setting up the stratum proxy on ubuntu 12.04? the instructions are kind of vague. i have python installed. im positive. i have the files downloaded and extracted. these are the instructions i can find. Installation on Linux Download TGZ file from https://github.com/slush0/stratum-mining-proxy/tarball/master Unpack it by typing "tar xf slush0-stratum-mining_proxy*.tar.gz" Most likely you already have Python installed on your system. Otherwise install it by "sudo apt-get install python-dev" (on Ubuntu and Debian). Type "sudo python setup.py install" in the unpacked directory. You can start the proxy by typing "./mining_proxy.py" in the terminal window. Using default settings, proxy connects to Slush's pool interface. If you want to connect to another pool or change other proxy settings, type "mining_proxy.py --help". does "sudo python setup.py install" mean "sudo python ~/filecreatedforstratum/setup.py install" because if it does... typing "./mining_proxy.py" or "mining_proxy.py --help" does nothing. terminal does however start giving characters like < rather than the usual ":~$" prompt. very frustrated at the moment. =/
|
|
|
|
Current C
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 20, 2013, 03:07:29 AM |
|
now trying to figure out bfgminer. this is the current ppa from unit 3? https://launchpad.net/~unit3/+archive/bfgminerso i have that all setup. but i dont know what to do here do i need to put some commands into terminal now? once i have this cleared up ill post some updates just incase someone else gets into the same boat as me and ends up in 3 to 5 threads looking for answers.
|
|
|
|
vesperwillow
|
|
November 20, 2013, 04:47:46 AM |
|
Off the top of my head, try this from the bfgminer folder:
bfgminer -o stratum.bitcoin.cz:3333 -u slushworker -p slushpass --http-port 8332
(substitute whatever port you setup in your blades server settins for 8332 if necessary)
If that works, I can show you a simple script to make it work easier.
|
|
|
|
Ally_Rob
Newbie
Offline
Activity: 52
Merit: 0
|
|
November 20, 2013, 05:08:37 AM |
|
Hey... How did you run power to the board? I took a 4-pin-molex which was to power 2 sata. I snipped stripped and did as you see. 4 blacks; 2 yellows. Cant get the access via the webserver . The led flashes once in a blue moon. my router is setup, to end its dhcp server at 254, i just ungraded it to include 254. I still cant get access to the webserver. my internal ip is 192.168.2.xxx ive tried new ethernet cables, still cant wrapped my head around it.. thanks rob this is my power https://i.imgur.com/8dSjuAr.jpgmy board https://i.imgur.com/hY7QPLU.jpg
|
|
|
|
vesperwillow
|
|
November 20, 2013, 05:24:15 AM |
|
Hey... How did you run power to the board? I took a 4-pin-molex which was to power 2 sata. I snipped stripped and did as you see. 4 blacks; 2 yellows. Cant get the access via the webserver . The led flashes once in a blue moon. my router is setup, to end its dhcp server at 254, i just ungraded it to include 254. I still cant get access to the webserver. my internal ip is 192.168.2.xxx ive tried new ethernet cables, still cant wrapped my head around it.. thanks rob this is my power my board It's your IP setting probably, default blade address is 192.168.1.254, but you're on 192.168.2.x As long as your router is a switching router, just change on of your computer's IPs to 192.168.1.x (x = unused IP, say 20 or something), and then try connecting to the blade at http://192.168.1.254:8000
|
|
|
|
Ally_Rob
Newbie
Offline
Activity: 52
Merit: 0
|
|
November 20, 2013, 05:32:20 AM |
|
Just done! I was trolling, found another post which mentioned the router being x.x.1.254 default.. Its working, shit i killed like 3 hours working on this lol now just got to get the proxy and off to the races. thanks again
|
|
|
|
ccplz
|
|
November 20, 2013, 02:39:04 PM Last edit: November 20, 2013, 02:56:54 PM by ccplz |
|
Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page. What I did was: 1)Open mining proxy(on default settings) 2)Set both the server addresses to my IP(as seen in cmd using /ipconfig) 3)Set the ports to 3333,8332 4)Set the account info to username_workername:password,username_workername:password Now I'm getting two different results. On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0 On port 8332 nothing happens. Would appreciate any help,thanks in advance. P.S. My ISP uses dynamic IPs,is there any way to setup the configuration without having to change the server addresses all the time? EDIT:This is the batshit crazy part.
|
|
|
|
CarneMuerta
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 20, 2013, 03:07:16 PM |
|
Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.
What I did was:
1)Open mining proxy(on default settings) 2)Set both the server addresses to my IP(as seen in cmd using /ipconfig) 3)Set the ports to 3333,8332 4)Set the account info to username_workername:password,username_workername:password
Now I'm getting two different results.
On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0 On port 8332 nothing happens.
Would appreciate any help,thanks in advance.
3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps
|
|
|
|
ccplz
|
|
November 20, 2013, 03:14:29 PM |
|
Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.
What I did was:
1)Open mining proxy(on default settings) 2)Set both the server addresses to my IP(as seen in cmd using /ipconfig) 3)Set the ports to 3333,8332 4)Set the account info to username_workername:password,username_workername:password
Now I'm getting two different results.
On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0 On port 8332 nothing happens.
Would appreciate any help,thanks in advance.
3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps Thanks for the quick reply. Tried that too,still doesn't work Current Server: 192.168.1.X:8332 No hashes
|
|
|
|
xyzzy099
Legendary
Offline
Activity: 1066
Merit: 1098
|
|
November 20, 2013, 03:28:36 PM |
|
Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.
What I did was:
1)Open mining proxy(on default settings) 2)Set both the server addresses to my IP(as seen in cmd using /ipconfig) 3)Set the ports to 3333,8332 4)Set the account info to username_workername:password,username_workername:password
Now I'm getting two different results.
On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0 On port 8332 nothing happens.
Would appreciate any help,thanks in advance.
3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps Thanks for the quick reply. Tried that too,still doesn't work Current Server: 192.168.1.X:8332 No hashes Do you also have a Bitcoin-QT or bitcoind running on your machine? If so, it will use port 8332 by default and you will be conflicting. I use BFGMiner as the proxy on port 8330. I have never used the slush proxy, but I imagine you can tell it to use a different port than 8332 for incoming connections.
|
Libertarians: Diligently plotting to take over the world and leave you alone.
|
|
|
ccplz
|
|
November 20, 2013, 03:32:49 PM |
|
Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.
What I did was:
1)Open mining proxy(on default settings) 2)Set both the server addresses to my IP(as seen in cmd using /ipconfig) 3)Set the ports to 3333,8332 4)Set the account info to username_workername:password,username_workername:password
Now I'm getting two different results.
On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0 On port 8332 nothing happens.
Would appreciate any help,thanks in advance.
3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps Thanks for the quick reply. Tried that too,still doesn't work Current Server: 192.168.1.X:8332 No hashes Do you also have a Bitcoin-QT or bitcoind running on your machine? If so, it will use port 8332 by default and you will be conflicting. I use BFGMiner as the proxy on port 8330. I have never used the slush proxy, but I imagine you can tell it to use a different port than 8332 for incoming connections. Nope,no other programs running.
|
|
|
|
xyzzy099
Legendary
Offline
Activity: 1066
Merit: 1098
|
|
November 20, 2013, 03:46:25 PM |
|
Nope,no other programs running.
Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have ' http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header. That edit box should just contain '192.168.1.x, 192.168.1.x'.
|
Libertarians: Diligently plotting to take over the world and leave you alone.
|
|
|
ccplz
|
|
November 20, 2013, 03:51:04 PM |
|
Nope,no other programs running.
Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have ' http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header. That edit box should just contain '192.168.1.x, 192.168.1.x'. Negative,no HTTP in the address box.
|
|
|
|
xyzzy099
Legendary
Offline
Activity: 1066
Merit: 1098
|
|
November 20, 2013, 03:58:11 PM |
|
Nope,no other programs running.
Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have ' http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header. That edit box should just contain '192.168.1.x, 192.168.1.x'. Negative,no HTTP in the address box. Something is trying to talk HTTP to the proxy: See the protocol error? It is failing to decode an HTTP header. If you don't have any edit boxes in your configuration window with an 'http://' prefix, then I don't get it...
|
Libertarians: Diligently plotting to take over the world and leave you alone.
|
|
|
ccplz
|
|
November 20, 2013, 04:02:45 PM |
|
Nope,no other programs running.
Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have ' http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header. That edit box should just contain '192.168.1.x, 192.168.1.x'. Negative,no HTTP in the address box. Something is trying to talk HTTP to the proxy: See the protocol error? It is failing to decode an HTTP header. If you don't have any edit boxes in your configuration window with an 'http://' prefix, then I don't get it... That picture was from the previous error when I was trying to use port 3333. Now that I'm using port 8332,it's stuck at
|
|
|
|
xyzzy099
Legendary
Offline
Activity: 1066
Merit: 1098
|
|
November 20, 2013, 04:09:04 PM |
|
Can you post a screen shot of your blade config window (with your username/pw blanked)?
I have never used that proxy, but it looks like it is connected to the pool and just waiting on a miner to connect.
|
Libertarians: Diligently plotting to take over the world and leave you alone.
|
|
|
ccplz
|
|
November 20, 2013, 04:14:48 PM |
|
I'm banging my head against the wall,so I may have blanked some unnecessary parts.(6 hours of staring at the configuration screen will do that to you)
|
|
|
|
xyzzy099
Legendary
Offline
Activity: 1066
Merit: 1098
|
|
November 20, 2013, 04:21:37 PM |
|
Well, everything I can see looks right. As long as your user/pass field is 'user:passe,user:pass', the only other thing I can think of is a firewall issue that is blocking port 8332 between your blade and the proxy machine. If that's not it, I don't have any other suggestions.
|
Libertarians: Diligently plotting to take over the world and leave you alone.
|
|
|
|