 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
I have updated the scripts and the script-generator. Now there are 3 options on the site https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency_detailed.html: - Monero (CryptonightV7): Use this option for mining Monero. I will always update the scripts/xmr-stak so that there will be uninterrupted Monero-mining with this setting (updates are required because Monero is planning to keep on changing the PoW to fight off ASICs)
- Generic CryptonightV7: Use this options for other CNv7-Coins. Or for multi-coin-pools like moneroocean.stream or miningpoolhub.com(?)
- Generic Cryptonight-Heavy: Use this options for other CN-Heavy-Coins
Personally, right now i am trying out moneroocean.com (multi-coin for increased profitability) and LOKI (just to test the CN-Heavy-performance). I'll report my experience in a later post. If you have a previously generated startup-script it will of course continue to work. |
|
|
|
So the "official" Sumo-team has decided to stop the rebranding to RYO and change the algo back to normal CN (i.e. support ASIC): https://www.reddit.com/r/sumokoin/comments/8npdvf/official_announcement_hardfork_happening_update/The algo-change is scheduled for monday (4th of June 2018). If you are currently mining SUMO with my script, i advise you to switch to some other currency as soon as possible! Your miners won't be able to mine SUMO after monday! If you don't mine SUMO (e.g. if you mine Monero), then you are not affected by this change and you don't have to change anything. I am currently working on updating the scripts to the new situation (i won't support the old CN-algo, though... profitability just won't be worthwhile due to the asics). |
|
|
|
My Azure credits has run out last month and I now need to start the script again.
How and where do I start it manually?
Once your free credits run out azure will delete your pools. To restart you'll have to setup everything again, just follow the guide at https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.html from the point where the creation of the pools is described. Note that this only happens if you create too many nodes in your pool... if you set the number of nodes according to the table in my guide your azure-credits will last the whole month and it will just keep on running forever. |
|
|
|
I was looking for the azure-ToS, and on the website this chat-windows pops up. So i start chatting: Is crypto-currency-mining forbidden in the azure-cloud? Welcome to Azure Chat! Let me just check, please allow me minute. You are allow to do it in the Azure cloud but please be aware of your need a large Virtual Machine. actually a friend of mine told me that his account was disabled the support told him that this was due to a violation of the ToS Azure Security Center helps customers deal with myriads of threats using advanced analytics backed by global threat intelligence. In addition, a team of security researchers often work directly with customers to gain insight into security incidents affecting Microsoft Azure customers, with the goal of constantly improving Security Center detection and alerting capabilities - https://azure.microsoft.com/es-mx/blog/how-azure-security-center-detects-a-bitcoin-mining-attack/Yes, i have already seen that link. but this does not apply to my friend's situation the link talks about some kind of virus, which does the mining against the will of the subscriber However, my friend intentionally does the mining all by himself. They can be other reason for that, unfortunately I can't see the exact case as we are the pre-sales team which means we don't have any access to any accounts and we are not allowed to provide any information regarding someones else account. azure.microsoft.comhttps://azure.microsoft.com/en-us/support/legal/subscription-agreement-nov-2014/ Ok, thanks for your help. After reading the ToS i come to the same conclusion as the chat-agent: mining (or having 100% CPU-load for any other purpose) is not specifically forbidden. To the people who actually got banned from azure: Are you sure that the supposed breach of the ToS was not related to the way you have created your account? Maybe you had multiple accounts, phoney credit-card-numbers, obvious fake names, etc? All i can say is that so far i never had this kind of problem, and i've been mining non-stop for over 6 months now. However, when signing up i also made a point to only use legit information (real name, real address, etc. ). Maybe that is the difference? |
|
|
|
I ended up getting about 13 sumo coins after about 4 days of mining. hashrate was around 2000 h/s and I think I also used close to $100 of the $200 free credits.
And then.... Banned! Yep, I totally got banned for violating terms of service. Hope this doesn't mess with my MCSE certification! lol
Did azure give you some more details what behavior exactly they didn't like? |
|
|
|
|
FYI: I have added some information about connecting to a node of your pool in the original post. After connecting, you can view the output of the mining-software (xmr-stak). This is useful when diagnosing problems.
|
|
|
|
Is it possible to get workername as same as pool name or subscription ID/name ?
Update: There is now an option to use the pool-name as the worker-ID. I have updated the quickstart-instructions to do this automatically, i.e. if you create a new startup-script with the quickstart-instructions your miner will use the azure-pool's name as the worker-id. If you are using my detailed-script, there are some variables which let you configure the worker-id any way you want: - ${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!
Just place one of these variables where you would normally put the worker-id, and when the miner is started it will get replaced with the corresponding content. You can have a look at the script generated by the quickstart-instructions to see an example for using the variable ${AZ_BATCH_POOL_ID}. |
|
|
|
How many hash did you get already ?  I'm moving to MPH, seem better luck ... I am satisfied with the performance of supportXMR. Since i am just burning my free credits from azure i don't need to optimize for the last few %. But then... how much better is Mining Pool Hub? Is it really worthwhile switching? (MPH = Mining Pool Hub ?) |
|
|
|
|
Ok, the attack on supportXMR seems to be over. As far as i can see things work normally again.
|
|
|
|
A weird coincidence... apparently supportXMR.com is under a DDoS-Attack right now: https://www.reddit.com/r/MoneroMining/comments/8kksag/whats_up_with_supportxmr/However, as far as i can tell really only the dashboard of the pool is affected, the mining is still going on normally. This also means that adding a backup-server as suggested in my previous post will not change anything (from the point of view of the mining-software everything is ok since the shares get accepted and it will continue just working with the primary server). |
|
|
|
Great work !
Is it possible to get workername as same as pool name or subscription ID/name ?
Or even set a name same as vm name like this :
Initially i also thought of doing something with the VM-name. But would that really be useful? Sometimes the nodes get switched off (cheap low-priority-nodes), azure might assign a new name to the node when it comes back. Also, the names do not seem to indicate the pool the node belongs to. Using the pool-name sounds like a better idea. I'll have to research whether the script can actually somehow get access to the name of the pool. I'll have a look at it (it might take some more time until i can implement this). |
|
|
|
workername... try adding ".worker" after your wallet address in config script
e.g. 4999aeniCU9Ug67vs7yvyJTSkxVUZRirUYUerT66fqzoYMhiShFLBqZHmFxmPD6oABafM5cVKc77yyy yyyyyyyyyyyyyyyyy.worker
or change password.
Thanks for trying to help, but in this case it works a little different. Have a look at the first post in this thread, i already put a description how to set the worker-ID there. |
|
|
|
Any update about WokerName yet ?
I added a paragraph about the worker-ID in the initial post. As always: if you have trouble getting it to work just post a message here. |
|
|
|
just an after thought; if you are worried about them monitoring your traffic to known mining sites; just use a VPN service for any of its connections Yes, that's a good idea. I'm putting this on my to-do-list... |
|
|
|
I was talking about the azure account, the VMs defintely stopped, I can still login, the batch service is still there, but it displays "No Access" when i try to access Pools menu, I also cant add a new pools. and with the subscription disabled, i cant choose any subscription to create a new group
I'll try the support today
Thanks for the update. When you get a reply from the support, please share it here. |
|
|
|
Running 3 subscriptions now.
Are you talking about actual MSDN-subscriptions with free monthly azure-credit, not just one-off Azure-accounts? May i ask you how you got the 3 subscriptions? |
|
|
|
M60 can run ZEC at 320H/s or lyra2v2 at 26MH/s, plus 6 CPU
May be we can get something better than 20 CPU core to mine XMR ?
When i started setting up the scripts i experimented with the GPU-VMs from Azure. The GPU of course is capable of a higher hashrate, but it is also more expensive. I found that in the end the profit is approximately the same, but setting it up is by far more difficult. For the GPU to work i have to install some external NVIDIA CUDA-packages and reboot the VM a few times. Setting it up was a fight even with the official guide from azure. I checked the hashrates you gave at whattomine.com and it did not show a higher profit than Monero (assuming 1600H/S), even if you take into account the extra 6 CPUs. I know profit-calculators are not really exact... do you think that the numbers are so far off that in the end using the GPU would yield a better result than CPU-mining? |
|
|
|
After delete all old ResoureGroups and do it again, thing done well now !  I will looking at the bill to see if it really cost lest than 150$ If possible please add some options to the script : wokername and email to notify. Thank you for the script. I'm glad to hear that it's working for you. Thanks for the suggestion about the workername. I'll write up the options for adding a workername in a later post. |
|
|
|
|
