Modified for Flux mining about aws-ethereum-miner HOT 11 CLOSED

Seems to be hanging on the Lambda instance filter creation process.?

from aws-ethereum-miner.

I am sure its something stupid that I missed... I've never worked with CF so I am not sure why the instance filter keeps failing.

from aws-ethereum-miner.

The instance filter simply filters the list of instances by availability and then sorts by their cost/performance ratio. It shouldn't take too long. By now it will probably have timed out - what errors do you see?
You can check the InstanceFilterLambda logs in CloudWatch logs.

from aws-ethereum-miner.

I found this in the Lambda logs:
[ERROR] Runtime.UserCodeSyntaxError: Syntax error in module 'index': invalid syntax (index.py, line 1)
Traceback (most recent call last):
  File "/var/task/index.py" Line 1
    %%{lambdas/instance-filter.min.py}%%

from aws-ethereum-miner.

from aws-ethereum-miner.

I have not had any problems running your version of the script, I just don't see how my version would change this part of the code at all.

from aws-ethereum-miner.

Well I found a number of problems with my template. The first is that the commands actually don't work, AND more importantly, for the AMI you are using, miniZ miner does not detect any CUDA gpu's. I looked up the AMI from a working ethminer I have running using your script, and then launched another instance using that AMI (which I assume has the cuda drivers and gpu's installed as a G4.xlarge instance). However, it could be that miniZ does not support the V4 GPU? This might be over my head to troubleshoot.

from aws-ethereum-miner.

Righto, you have based your mods on src/template-eth-default-vpc.yml which doesn't have the Lambdas included. You'll need to do your changes in the top directory's template-eth-default-vpc.yml instead. Or run "make" in the top directory but for that you'll need to install some extra tools - pyminifier, pylint, maybe some more. It's easier to port your changes to the compiled yml file in the top dir.

from aws-ethereum-miner.

And regarding the incompatibility with miniZ - I don't know to be honest. It could be that it doesn't support the newer GPUs or CUDA 11. You can try to force the template to g4dn.xlarge - that's got an older GPU, that may be supported. But since ETH is more profitable still I'd just mine that if I were you.

from aws-ethereum-miner.

Thanks! This was a great learning experience. I got to touch on many new things and see how they work. Flux is certainly not worth mining on AWS, and Eth is only worth doing if you have the extra compute to spare. I will try to incorporate the changes you mentioned and give it another shot. If successful I will upload the forked version so others can try different coins. Now, what would be super cool would be an encompassing CF template that ran a check on whattomine to see whats most profitable and run that, and dual mine a CPU coin like Raptoreum at the same time. :) (AND just as I was typing this, my template is working fine now.... THANKS!)

from aws-ethereum-miner.

Glad that it works now :)

The trouble with whattomine is that it doesn’t list the performance of the cards used by AWS. So it’s hard to use for our needs.

from aws-ethereum-miner.