BitShares Forum
Other => Graveyard => BitShares PTS => Topic started by: K20 on January 03, 2014, 09:35:19 am
-
This guide will teach you how to use Amazon Web Services to mine Protoshares with ypool.
This first part of this guide will be very similar to Lord FireFox's AWS Guide, probably up to about Step 9. You can find the guide at the link below, however I will put the content here too with some changes:
https://docs.google.com/document/d/1pPjVvNCDMeUwDBd4M9ysH8O-Ogu_Ca2J0HkOAW20ZRk/edit
Software
Some software you will need to download and install:
WinSCP: http://winscp.net/eng/index.php
PuTTY: https://blog.splunk.net/64bit-putty/ You will want the Windows Installer with Everything because you will be using PuTTYgen.
Get your Amazon AWS set up:
Step 1. Sign up for a free Amazon AWS. Don't worry we won't be using the freebie options.
Step 2. Credit your account. The $100 promo credit will work just fine. http://aws.amazon.com/big-data/powerof60/
Step 3. Buy an Amazon AWS EC2 Spot Instance. Try to get a good price. $0.50 seems to work reasonable well.
A. Click on Services and go to EC2 dashboard.
B. Click the Launch Instance button.
C. Select Ubuntu Server 12.04.3 LTS for HVM Instances , make sure the 64-bit option is selected and then click the Select button.
D. On the “2. Choose Instance Type” page you want to select Compute Optimized.
E. Click on cc2.8xlarge. Then click the button labeled “Next: Configure Instance Details”.
F. Since we're testing this instance we only need 1.
G. Put a checkmark in the “Request Spot Instances” option. Enter your Maximum price per hour for “Maximum price”. Refer to the table above to look at the current rates.Leave everything else as default. Then click “Next: Add Storage”.
H. Leave Storage as default.
I. Click on “Next: Tag Instance”. Give it a meaningful name (example: PROTOSHARES).
J. Click on “Next: Configure Security Group” Give it a meaningful name (the default names work just fine) and configure it for your IP only. Under Source click the Drop-down box labeled “Anywhere” and change it to “My IP” and enter your IP address. Leave everything else default.
[NOTE: If you're on a Dynamic IP host (your ISP uses Dynamic IP Network) You will have to leave it set to “Anywhere” otherwise you will have problems accessing it later. I haven't tested it but you might be able to work around this with a free DynDNS service.]
K. You will get a warning on the next screen saying that this setup doesn't qualify for the Free AWS version. You can ignore this warning if you successfully received the AWS $100 credit. At this point you will get a dialog wanting you to create a private key ( YOU WILL NEED THIS), follow the instructions and make sure to save your key to your local hard drive or thumb drive somewhere in a directory you can find later because you're going to need it.
L. Click “Launch” Button and wait. You will be taken to the “Spot Requests” Screen If your Spot Request is accepted it will take a bit for it to be configured and then it will turn Green indicating it's now running. You can then click on the “instances” link on the left and view the EC2 instance running.
Step 4. Now on to the “fun” Linux stuff; Make sure you copy/paste into a Notepad or Wordpad document, because we're going to need these later:
A. The ID of the Instance from the Instance ID column.
B. The Public DNS name of the instance from the Public DNS column.
Step 5. The private key we got from earlier needs to be converted to a file PuTTY can use.
A. Start PuTTYgen from the start menu (you did remember to install PuTTY right?).
B. Under “Type of key to generate”, select “SSH-2 RSA”.
C. Click “Load” and select the option to display files of all types.
D. Select your private key .pem file (located where you saved it earlier). Click “Open” and then click “OK” on the confirmation dialog box.
E. Click “Save private key” to save your key in a format PuTTY can use. You will of course get a warning dialog saying that you're saving it without a passphrase, you can go ahead and ignore this because if you use a passphrase you cannot use any automated scripts to log in to your Instance. Just click “Yes”
F. VERY IMPORTANT! Use the same name for the key that you used for the key pair (example: my-key-pair). PuTTY automatically adds its .ppk file extension.
Step 6. Start PuTTY from the start menu.
Step 7. In the Category pane, select “Session”
A. In the Host name field enter user_name@public_dns_name. Make sure you're using the right user name for your AMI. For Example since we're on an Ubuntu instance the user name is ubuntu. So in this field you put ubuntu@<insert your public DNS name you copied to Notepad from Step 4 earlier>.
B. Under “Connection Type”, select SSH
C. Leave the port number at 22.
Step 8. Back in the Category pane, expand SSH, and then select Auth.
A. Click the “Browse” button.
B. Select the .ppk file that we generated with PuTTYgen earlier, and then click “Open”.
C. It's optional but recommended to save the session information for future use. Select “Session” in the “Category” tree, enter a name for the session in “Saved Sessions”, click the “Save” button and you're done.
D. Click the “Open” button and you will start your PuTTY session. HOORAY! LINUX!
Step 9. You will get a security alert asking if you trust the host you're connecting to just click “Yes”.
Step 10: Download yvg19000's yam by typing the following:
wget https://dl.dropboxusercontent.com/u/28534583/yam-yvg1900-M7i-linux64-sandy-bridge.tgz
Step 11: Unzip the miner by typing the following:
tar xvf yam-yvg1900-M7i-linux64-sandy-bridge.tgz
Step 12: Navigate to yam with the following command:
cd yam-yvg1900-M7i-linux64-sandy-bridge/linux64-sandy-bridge/
Step 13: Now you need to run yam with your ypool details like follows and be sure to change the parts in blue:
./yam -M xpt2h://<username>.<miner>:<password>@mining.ypool.net:10034:8080:8081:8082:8083:8084:8085:8086:8087/pts -P pts:av=0 -P pts:m=2048
All going well, you should start to see the miner working and your PTS appearing in ypool.
If this has been helpful and you wish to donate, please send PTS to Pt9XNjs3CXEzQ5p3RFh68nfb9upGBtYpzh
-
Still getting error.....tough nut to crack. I've tried just about everything......
Except the right thing apparently ::)
YAM - Yet Another Miner by yvg1900
yam M7i-linux64-sandy-bridge/yvg1900
***************************************************
* Supported coins: PTS *
* Author: yvg1900 (Twitter @yvg1900) *
* XPT protocol: jh (http://ypool.net) *
* *
* Addresses for Thanks and Donations: *
* PTS: PZxsEQoiMeB6tHcW2ZySBEiCPio1WkxbEL *
* XPM: AW2388DEWNEfMH4rP9kcj9yKcMq1QywYT4 *
* DTC: D6PmUogMigWvXurgFTqm5VLxQeVpXdYQj3 *
* LTC: Lby4YjhcAxhmbsdHFb4nYydrwGoiJezZt1 *
* BTC: 1FxekeK5La7AuF3oxiLzPKnjXyLMrux6VT *
* NMC: N9KXqmzEqP7gB2dGHpEZiRMgFjUHNM38FR *
***************************************************
Checking PTS optimizations compatibility...
Illegal instruction (core dumped)
ubuntu@ip-172-31-14-243:~/yam-yvg1900-M7i-linux64-sandy-bridge/linux64-sandy-bridge$
-
Dose it profitable? what's the speed of 8x large instance? thanks.
-
Still getting error.....tough nut to crack. I've tried just about everything......
Except the right thing apparently ::)
YAM - Yet Another Miner by yvg1900
yam M7i-linux64-sandy-bridge/yvg1900
***************************************************
* Supported coins: PTS *
* Author: yvg1900 (Twitter @yvg1900) *
* XPT protocol: jh (http://ypool.net) *
* *
* Addresses for Thanks and Donations: *
* PTS: PZxsEQoiMeB6tHcW2ZySBEiCPio1WkxbEL *
* XPM: AW2388DEWNEfMH4rP9kcj9yKcMq1QywYT4 *
* DTC: D6PmUogMigWvXurgFTqm5VLxQeVpXdYQj3 *
* LTC: Lby4YjhcAxhmbsdHFb4nYydrwGoiJezZt1 *
* BTC: 1FxekeK5La7AuF3oxiLzPKnjXyLMrux6VT *
* NMC: N9KXqmzEqP7gB2dGHpEZiRMgFjUHNM38FR *
***************************************************
Checking PTS optimizations compatibility...
Illegal instruction (core dumped)
ubuntu@ip-172-31-14-243:~/yam-yvg1900-M7i-linux64-sandy-bridge/linux64-sandy-bridge$
That's strange. Did you take out the cc2.8xlarge server?
-
Wasn't available...used c3.2large with all different command line options....same thing.
It's supposed to be under compute optimized?
I've tried core2 and generic with 13.10 and get boost errors....been trying this for awhile...lol
-
the 100$ amazon credit no longer exists, it redirects you to amazon aws main page now.
-
Anyone successfully running yam-yvg1900-M7i on an Amazon instance?
Please update as Op's method does not seem to work.
-
Anyone successfully running yam-yvg1900-M7i on an Amazon instance?
Please update as Op's method does not seem to work.
It will work but you said you're not using cc2.8xlarge which means your using a different cpu so probably will use a different instruction set
Follow the instructions. I've just followed them myself to the letter and can confirm it works fine
-
Amazon does not offer the cc2.8xlarge with Ubuntu Server 12.04.3 LTS so I think therein lies the problem. I will try with Amazon Linux AMI (HVM) 2013.09.2 and
see if that works. That is the only instance I see that offers the cc2.8xlarge.
Ok....I used the Linux AMI (HVM) and got a little further....you have to login with: ec2-user
As soon as it starts it gets killed...
Ok....changed it to 1024 instaed of 2048 and we're mining. Will attempt further fine tuning...... :D
Another tip...Use screen to detach your mining session so it can continue to mine if your computer shuts down for any reason.
Type "screen" at beginning of session then setup miner. After miner is running press, control-A then control-D. This will detach your screen session but leave your
processes running.
To bring back your miner type "screen -r". This will resume your session.
Checking PTS optimizations compatibility...
OK: PTS optimizations are compatible
Checking target [xpt2h://xxxxxxxx.PTS_1:x@mining.ypool.net:10034:8080:8081:8082:8083:8084:8085:8086:8087/pts] OK
Checking params [pts:av=0] OK
Checking params [pts:m=2048] OK
ProtoShares: Memory usage 2048M per thread, determine Algorithm Variation by finetuning
Using 32 mining threads
Will mine 128 rounds for miner developers to support development of the next version
Follow @yvg1900 on Twitter to get information on new version availability on time
xpt: Logged in with xxxxxxxx.PTS_1
New ProtoShares Block 39563
ProtoShares Aggregated CPM: ?; Rounds Complete/Incomplete: 0/0, Donated Complete/Incomplete: 0/0; Config/Thread CPM: ?/? on 0 rounds with AV=1, ART=? ms; Fine-tuning: IN PROGRESS, AV/RT: 1/0, Best AV/RT: 1/0
mining.ypool.net: On-line, Shares Submitted 0, Accepted 0
Killed
[ec2-user@ip-172-31-5-235 linux64-sandy-bridge]$
-
Seriously. Follow the instructions. It works and there is a HVM instance for 12.04 on cc2.8xlarge:
(http://i.imgur.com/9jym3I1.png)
(http://i.imgur.com/WxWKkIT.png)
-
Very cool...found it in N. Virginia. Not available on the Asian/Far East instances I usually use.
Still had to use 1024 instead of 2014.
Seriously, you could be a little more detailed in your walk through :P
-
At this time, no cc2.8xlarge offered in N. Virginia nor in other locations :-(
Would it be possible to have a the same kind of nice work through document for a c3.4xlarge size ?
-
I'm seeing them under Ubuntu Server 12.04.3 LTS for HVM Instances in N. Virginia at the moment. Look in compute optimized.
It's very possible it will work with the smaller machines....give it a try. You might have to experiment with the -m (memory size per thread in megabytes) parameter.
-
ok, it works fine with a ubuntu on c3.2xlarge instance running yam-yvg1900-M7i-linux64-generic
I just had to use the m=1024 parameter (m=2048 caused miner to be killed, because of lack of memory)
seems to stabilize on 165 CPM
concerning the earnings, I still have some doubts : the miner seems to submit around 17share value/h, which makes less than 0.004 pts/h (0.08$/h) to be compared with the hourly price of the c3.2xlarge instance...
am I calculating something wrong ?
-
ok, it works fine with a ubuntu on c3.2xlarge instance running yam-yvg1900-M7i-linux64-generic
I just had to use the m=1024 parameter (m=2048 caused miner to be killed, because of lack of memory)
seems to stabilize on 165 CPM
concerning the earnings, I still have some doubts : the miner seems to submit around 17share value/h, which makes less than 0.004 pts/h (0.08$/h) to be compared with the hourly price of the c3.2xlarge instance...
am I calculating something wrong ?
no, it just isn't profitable. but that doesnt stop people from wasting money
-
(http://www7.pic-upload.de/thumb/13.01.14/mbgd3vri6ro.png) (http://www.pic-upload.de/view-21941247/Bildschirmfoto-2014-01-13-um-19.02.15.png.html)
Thanks :)
1k cpm on 2.8xlarge