Hi everybody,
There are many guides on how to setup azure-servers for mining cryptocurrency. However, this one is different. If you follow this guide, you'll get these features:
- 5 minutes to setup
- After setup, it will run indefinitely - no need to even log in to azure after the initial setup (you'll need a MSDN-subscription with monthly free credits, though)
- Attractive hashrate - currently i get sustained 8 kH/s for my 150$ monthly free credits (check whattomine.com to see the potential payoff - note that this will change with the market-conditions, though)
So how is this possible? Well, first of all we'll be using the low-priority batch service to keep the cost down. Like this we can have several servers running for the complete month. After one month, your new monthly credits will arrive, leaving your servers and the complete setup running indefinitely.
The setup of the azure severs is so easy and fast because i already did the hard work for you: On my website (link see below) i have created some handy javascript which takes your wallet as input and spits out your personal customized startup-script for the azure-batch-service.
Lastly, the hashrate is so high because the script has a clever self-tuning feature which will adapt itself to the load of the physical server azure places your virtual machines on. If you are lucky, you'll have lots of idling neighboring VMs, and then the mining-software will be able to employ more of the precious L3-Cache of the Server.
Here's the link to the complete guide for mining Monero:
https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.htmlEverything is hosted on github. Check out the code if you have any doubts about the function of the script!
If you are interested in other Cryptonight or Cryptonight-Heavy-Coins, see this link:
https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency_detailed.htmlI have been mining like this since the beginning of 2018. So far, the azure-VMs have been running smoothly without any problem (unlike the VMs from google's or amazon's cloud-service, which apparently get automatically shutdown once they detect that you are mining cryptocurrency).
If you have any questions or problems feel free to PM me or reply in this thread.
Extra info: How to add a worker-ID. The procedure depends on the used pool (check the pool's documentation to find out more). If your pool is already running, you'll have to restart the nodes in your pool for the changes to take effect.
1. supportXMR.com (or similar pools expecting the worker-ID in the password-field)
The detailed script-generator has a field which will be passed on to the pool as the password. You can enter your worker-ID there.
2. xmrpool.eu (or similar pool expecting the ID as part of the wallet)
The pool expects the worker-ID as a suffix to the wallet. Check the pool's documentation to find out the exact format. xmrpool.eu expects a "+"-sign. This can be directly entered into the wallet-field in the html-form on my website. So instead of just putting e.g.
oYMhiShFLBqZHmFxmPD6oABafM5cVKc77yj3Fypvi9CDRTYEvDPL4999aeniCU9Ug67vs7yvyJTSkxVUZRirUYUerT66fqz
into the form, you would enter the string
oYMhiShFLBqZHmFxmPD6oABafM5cVKc77yj3Fypvi9CDRTYEvDPL4999aeniCU9Ug67vs7yvyJTSkxVUZRirUYUerT66fqz+superhash
into the form. With the generated startup-script you'll have the worker-ID "superhash".
3. Using the Azure-Pool-Name as worker-id: There are some pre-defined variables that you can also use:
- ${AZ_BATCH_POOL_ID} : The name of the azure-pool used
- ${AZ_BATCH_ACCOUNT_NAME} : The name of the azure-batch-account used
- ${AZ_BATCH_NODE_ID} : The name of the azure-pool-node. Typically this is a complicated name with some special characters. Use at your own risk!
Have look at the script generated by the quickstart-guide for an example how to use the variable ${AZ_BATCH_POOL_ID}.
Extra Info: Troubleshooting
Most problems can be diagnosed by looking at the output of the mining-software (xmrig). To see the output, go to your pool, then click on "Nodes" on the left pane (Note that it's normal that all nodes have the state "waiting for start-task" - that's due to the way the script works). The list of the nodes in your pool should appear, click on the node that is making trouble (or any of them if e.g. you have a hashrate of 0). At the bottom of the page you can see a list of the files on your node. The following files are interesting (enter the name into the search-box to filter the list)
- startup/wd/xmrig/build/logfile.txt (output of xmrig)
- startup/stdout.txt (output of the control-script)
- startup/stderr.txt (output of the control-script)
Some problems (like connection-problems to your pool) will be obvious when reading the output of xmrig. Otherwise you can post the relevant parts here and i will try to help you.
Full disclosure: The donation-level of the mining-software used is set to 4%. Half of this (2%) is going to the developers of the mining-software (xmrig), the other half is going to my pocket. You can view this as a convenience-fee for getting a tested and streamlined mining-script.
P.S.: Be aware that you need Azure-credits from a legitimate source, otherwise you will get banned.
Edit: added info about Sumokoin
Edit2: added info about workerid
Edit3: some more info about workerid: pre-defined variables
Edit4: added info about troubleshooting
Edit5: update info about troubleshooting, add link to NIM-script
Edit6: updated info about potential hashrate after the October-2018-fork
Edit7: some minor edits
Edit8: some minor edits
Edit9: removed option for mining NIM