Topic: [SRC] Noobproof VPS SecureCoin/QuarkCoin All-In-One Pool Mining Script (Read 16410 times)
February 12, 2014, 03:20:12 AM
just a noob question: can I connect 2 VPS to a same worker ? do they increase the speed of worker or when VPS1 connect and the VPS2 can't connect?
December 13, 2013, 10:38:20 PM
In case anyone was looking to sign up and try to increase the cap of 5, Digital Ocean has a hard cap on cpuminers at the moment. Understandable but hopefully in the future it can be increased.
Quote
Hello!
Cryptocurrency mining is very CPU intensive, and due to the shared nature of our CPU allocations large-scale cryptocurrency mining will seriously affect the quality of service we can provide to the neighbouring servers on the same hypervisors as servers running cryptocurrency mining operations.
So, while we do not specifically prohibit cryptocurrency mining, we do restrict accounts doing so to prevent large-scale operations from affecting our infrastructure.
Therefore, at this time, we do not provide droplet limit increases to accounts currently engaging in this activity. This includes opening additional accounts for the purpose of mining.
We apologize for this inconvenience, but we have to do our best to provide fair usage for all our users.
Regards,
Support Team
DigitalOcean
Cryptocurrency mining is very CPU intensive, and due to the shared nature of our CPU allocations large-scale cryptocurrency mining will seriously affect the quality of service we can provide to the neighbouring servers on the same hypervisors as servers running cryptocurrency mining operations.
So, while we do not specifically prohibit cryptocurrency mining, we do restrict accounts doing so to prevent large-scale operations from affecting our infrastructure.
Therefore, at this time, we do not provide droplet limit increases to accounts currently engaging in this activity. This includes opening additional accounts for the purpose of mining.
We apologize for this inconvenience, but we have to do our best to provide fair usage for all our users.
Regards,
Support Team
DigitalOcean
December 13, 2013, 06:38:41 PM
Is anyone trying to create a droplet on Digital Ocean right now? I'm unable to.
On topic: I've got the script running great, thanks giga. 1 thread isn't a real performer but seriously, you can't knock the ROI.
Couple questions about D.O... How do you increase your droplet quantity above 5? And.. does it matter if all droplets are reporting to your pool as the same worker?
On topic: I've got the script running great, thanks giga. 1 thread isn't a real performer but seriously, you can't knock the ROI.
Couple questions about D.O... How do you increase your droplet quantity above 5? And.. does it matter if all droplets are reporting to your pool as the same worker?
December 13, 2013, 05:07:43 AM
I just bought a vps ubuntu 12.04 64bit and on this vps it seems it doesnt work
/root/build-securecoin: line 5: cd: /root/quarkcoin-cpuminer/src: No such file or directory
make: *** No rule to make target `clean'. Stop.
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat `./minerd': No such file or directory
Starting securecoin miner
update-rc.d: warning: /etc/init.d/cron missing LSB information
update-rc.d: see
System start/stop links for /etc/init.d/cron already exist.
==========================================================
All Done!
securecoin pool miner should be up and running
Run ~/start-securecoind to start securecoind and begin mining
Run ~/stop-securecoind to stop securecoind and stop mining
Run ~/build-securecoin to update and rebuild securecoind
Run ~/peek to check on your mining status
root@xihn6obbrq:~#
/root/build-securecoin: line 5: cd: /root/quarkcoin-cpuminer/src: No such file or directory
make: *** No rule to make target `clean'. Stop.
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat `./minerd': No such file or directory
Starting securecoin miner
update-rc.d: warning: /etc/init.d/cron missing LSB information
update-rc.d: see
System start/stop links for /etc/init.d/cron already exist.
==========================================================
All Done!
securecoin pool miner should be up and running
Run ~/start-securecoind to start securecoind and begin mining
Run ~/stop-securecoind to stop securecoind and stop mining
Run ~/build-securecoin to update and rebuild securecoind
Run ~/peek to check on your mining status
root@xihn6obbrq:~#
September 23, 2013, 03:39:25 AM
August 31, 2013, 12:45:54 PM
I just tried this, and I get Downloading and building securecoin...
Cloning into 'quarkcoin-cpuminer'...
error: The requested URL returned error: 503 Service Temporarily Unavailable while accessing http://github.com/uncle-bob/quarkcoin-cpuminer.git/info/refs?service=git-upload-pack
fatal: HTTP request failed
Cloning into 'quarkcoin-cpuminer'...
error: The requested URL returned error: 503 Service Temporarily Unavailable while accessing http://github.com/uncle-bob/quarkcoin-cpuminer.git/info/refs?service=git-upload-pack
fatal: HTTP request failed
That would be github running into problems. They get hit with DDoS attacks fairly frequently.
You have two options: rerun the script as a whole, or just rerun the rebuild and run scripts:
~/stop-securecoind; ~/build-securecoin; ~/start-securecoind
August 31, 2013, 07:13:05 AM
I just tried this, and I get Downloading and building securecoin...
Cloning into 'quarkcoin-cpuminer'...
error: The requested URL returned error: 503 Service Temporarily Unavailable while accessing http://github.com/uncle-bob/quarkcoin-cpuminer.git/info/refs?service=git-upload-pack
fatal: HTTP request failed
/root/build-securecoin: line 10: cd: /root/quarkcoin-cpuminer: No such file or directory
/root/build-securecoin: line 11: ./autogen.sh: No such file or directory
/root/build-securecoin: line 12: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat â./minerdâ: No such file or directory
Starting securecoin miner
update-rc.d: warning: /etc/init.d/cron missing LSB information
update-rc.d: see
System start/stop links for /etc/init.d/cron already exist.
==========================================================
All Done!
securecoin pool miner should be up and running
Run ~/start-securecoind to start securecoind and begin mining
Run ~/stop-securecoind to stop securecoind and stop mining
Run ~/build-securecoin to update and rebuild securecoind
Run ~/peek to check on your mining status
Cloning into 'quarkcoin-cpuminer'...
error: The requested URL returned error: 503 Service Temporarily Unavailable while accessing http://github.com/uncle-bob/quarkcoin-cpuminer.git/info/refs?service=git-upload-pack
fatal: HTTP request failed
/root/build-securecoin: line 10: cd: /root/quarkcoin-cpuminer: No such file or directory
/root/build-securecoin: line 11: ./autogen.sh: No such file or directory
/root/build-securecoin: line 12: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat â./minerdâ: No such file or directory
Starting securecoin miner
update-rc.d: warning: /etc/init.d/cron missing LSB information
update-rc.d: see
System start/stop links for /etc/init.d/cron already exist.
==========================================================
All Done!
securecoin pool miner should be up and running
Run ~/start-securecoind to start securecoind and begin mining
Run ~/stop-securecoind to stop securecoind and stop mining
Run ~/build-securecoin to update and rebuild securecoind
Run ~/peek to check on your mining status
August 30, 2013, 05:32:24 PM
Why the two core instance? Isn't the single core cheapest one more cost effective?
Haven't tried, just fired one of the single core ones and it worked like a charm.
Expect some btc soon
Haven't tried, just fired one of the single core ones and it worked like a charm.
Expect some btc soon
August 30, 2013, 03:01:39 PM
Hate building your VPS nodes manually? Wish you could just copy paste them? You can!
(Note: this guide is for DigitalOcean only. Other providers like Linode also offer a cloning system, although a bit more complicated.)
Step 1: Build a node using the latest version of the setup script. If you've built the node previously, you might want to rebuild it. Older versions didn't include a "run at startup" routine which is required for this guide to be useful.
Step 2: Once you have your node configured, shut down the mining software gracefully. The command should be like ~/stop-something
Step 3: Shut down your Droplet from the droplet screen. Only do this once you're sure you've completed step 2 correctly.
Step 4: Once the node has shutdown, create a snapshot of the node in it's powered-off state. Give the snapshot a name (although it's not terribly important).
Step 4.5: Your snapshot process should now start. It can take anywhere from 30 seconds to 5 minutes, so be patient.
Step 5: This step is optional. If you wish to clone your node to regions besides the one your parent node was in, you'll need to distribute the snapshot. It can take anywhere from 3 to 15 minutes to complete. Doing this allows you to make a snapshot in NewYork and clone it to SanFrancisco or Amsterdam. This can be good for diversifying your node locations.
Step 6: Create a new Droplet and give it a name. Select the node type you'd like to build, then scroll all the way to the bottom. Don't click Create yet!
Step 6.5: Select a region for your node. If you skipped Step 5, it must be the same region as "parent" node.
Instead of selecting an operating system, click the "My Images" tab and select the image you created in Step 4.
Step 7: Congratulations! You've cloned a node! As soon as it comes online, it should automatically begin mining.
Please note that your new node has a different password! You'll need to check your email address to find out what it is. Feel free to change the password by logging in and running the passwd command.
Note: You can only have so many Droplets running at one time. To see how many you can create, click the gear button at the bottom left.
Be sure to check your Droplet limit regularly! The longer you're a customer, the more nodes you can have running at once.
If you enjoyed this mini-guide, feel free to donate or use any of the VPS referral links from the main posts.
BTC: 1E2egHUcLDAmcxcqZqpL18TPLx9Xj1akcV
Ψ: AWHJbwoM67Ez12SHH4pH5DnJKPoMSdvLz2
SRC: sMCD2p55fkPD6s8EzDrL7vVp8EYqPkJ6mo
(Note: this guide is for DigitalOcean only. Other providers like Linode also offer a cloning system, although a bit more complicated.)
Step 1: Build a node using the latest version of the setup script. If you've built the node previously, you might want to rebuild it. Older versions didn't include a "run at startup" routine which is required for this guide to be useful.
Step 2: Once you have your node configured, shut down the mining software gracefully. The command should be like ~/stop-something
Step 3: Shut down your Droplet from the droplet screen. Only do this once you're sure you've completed step 2 correctly.
Step 4: Once the node has shutdown, create a snapshot of the node in it's powered-off state. Give the snapshot a name (although it's not terribly important).
Step 4.5: Your snapshot process should now start. It can take anywhere from 30 seconds to 5 minutes, so be patient.
Step 5: This step is optional. If you wish to clone your node to regions besides the one your parent node was in, you'll need to distribute the snapshot. It can take anywhere from 3 to 15 minutes to complete. Doing this allows you to make a snapshot in NewYork and clone it to SanFrancisco or Amsterdam. This can be good for diversifying your node locations.
Step 6: Create a new Droplet and give it a name. Select the node type you'd like to build, then scroll all the way to the bottom. Don't click Create yet!
Step 6.5: Select a region for your node. If you skipped Step 5, it must be the same region as "parent" node.
Instead of selecting an operating system, click the "My Images" tab and select the image you created in Step 4.
Step 7: Congratulations! You've cloned a node! As soon as it comes online, it should automatically begin mining.
Please note that your new node has a different password! You'll need to check your email address to find out what it is. Feel free to change the password by logging in and running the passwd command.
Note: You can only have so many Droplets running at one time. To see how many you can create, click the gear button at the bottom left.
Be sure to check your Droplet limit regularly! The longer you're a customer, the more nodes you can have running at once.
If you enjoyed this mini-guide, feel free to donate or use any of the VPS referral links from the main posts.
BTC: 1E2egHUcLDAmcxcqZqpL18TPLx9Xj1akcV
Ψ: AWHJbwoM67Ez12SHH4pH5DnJKPoMSdvLz2
SRC: sMCD2p55fkPD6s8EzDrL7vVp8EYqPkJ6mo
August 30, 2013, 12:52:04 PM
It is interesting that when i look at the digitalocean cpu graph, it shows what appears to be a limit to 63% of cpu usuage..
Depending on what graph you're looking at, it may be the moving average.
*nix is really, really strange with things like that.
I'd check the process listing with "ps fu" or "ps aux" and verify it's using 100% like it should be.
August 30, 2013, 12:23:19 PM
It is interesting that when i look at the digitalocean cpu graph, it shows what appears to be a limit to 63% of cpu usuage..
August 30, 2013, 12:05:44 PM
working for me as well.
August 30, 2013, 12:05:26 PM
Working now. Verified with ~/peek.
Thanks!
-tb-
Thanks!
-tb-
August 30, 2013, 11:59:45 AM
August 30, 2013, 11:58:39 AM
Whats the easiest way to monitor or verify mining is running?
If you want to verify CPU usage:
Code:
ps aux | grep -v grep | grep -i minerd
If you want numbers:
Code:
~/peek
Says no such file or directory for peek.
I don't think the script completely ran. Going to reboot and try again..
Last time, I promise. I found the bug with the script, so it should work now, {}s and all.
Turns out bash was gobbling the "run-miner" file section.
Thanks!
August 30, 2013, 11:56:16 AM
Whats the easiest way to monitor or verify mining is running?
If you want to verify CPU usage:
Code:
ps aux | grep -v grep | grep -i minerd
If you want numbers:
Code:
~/peek
Says no such file or directory for peek.
I don't think the script completely ran. Going to reboot and try again..
Last time, I promise. I found the bug with the script, so it should work now, {}s and all.
Turns out bash was gobbling the "run-miner" file section. I forgot that "!" has special meaning at the command line.
August 30, 2013, 11:52:30 AM
Whats the easiest way to monitor or verify mining is running?
If you want to verify CPU usage:
Code:
ps aux | grep -v grep | grep -i minerd
If you want numbers:
Code:
~/peek
Says no such file or directory for peek.
I don't think the script completely ran. Going to reboot and try again..
August 30, 2013, 11:50:14 AM
Whats the easiest way to monitor or verify mining is running?
If you want to verify CPU usage:
Code:
ps aux | grep -v grep | grep -i minerd
If you want numbers:
Code:
~/peek
August 30, 2013, 11:43:52 AM
Whats the easiest way to monitor or verify mining is running?
August 30, 2013, 11:42:37 AM
Still having the problem.. being left at the > prompt
Try something for me real quick? Remove the first line, the one that starts "#!/bin/bash" and try again?
Let me know if that works.
I've updated the script and removed the "#!/bin/bash", so hopefully that fixes it.
No, still leaves me at the > prompt and a return just gives me another.
Thanks for the help, i am a linux weakling - windows guy (oh no!)
I am using digital ocean if that makes a difference. Also, when I paste i am at a: ~# prompt
I ran the script again without the {} and now the script is running and doing its thing.
-tb-
Just figured out the same thing! Thanks!
Jump to: