Lease Rig with BAMT

[koldshot]

Anyone using lease rig with BAMT?

As soon as I put the IP address in api-allow option, hashing goes to 0.
If I put 127.0.0.1 everything is fine. I've tried different ports and my firewall is fine
when 127.0.0.1 checkmyports shows the port is open. Using Leaserigs IP, it's closed.

[squiggie]

Use http://www.betarigs.com/

IMO, it's a better option as you don't have to open up your API to someone else. It just uses a proxy so you list it as the first pool, and when someone isn't leasing your rig, it will fail over to your backup pool. That a more elegant approach.

Sorry, that doesn't really answer your question, but it might be an alternative for you.

[koldshot]

I'm familiar with Betarigs too but the price is much lower. As a renter, Leaserigs shows a graph for live speed over last hour so monitoring is easier too. Apart from that the api thing not working is just something I want to figure out.

Also looking at JSON.karasoft.com using API parser, to manage pools and multiple cgminer rigs which is more what I'm after.

sort of on the same topic... kudos to hash.io for allowing us to create one account and flip our miner from pool to pool, but also for not having to create a million accounts for 500 pools...why did that take so long? Another story to tell our kids I guess.

[miaviator]

Anyone using lease rig with BAMT?

As soon as I put the IP address in api-allow option, hashing goes to 0.
If I put 127.0.0.1 everything is fine. I've tried different ports and my firewall is fine
when 127.0.0.1 checkmyports shows the port is open. Using Leaserigs IP, it's closed.

https://bitcointalk.org/index.php?topic=417092.0

FYI, for those using BAMT, the save call in the api will create a new cgminer.conf under /.cgminer/cgminer.conf  .
This is of course useless since BAMT starts cgminer pointed to /etc/bamt/cgminer.conf

A workaround is to schedule a job to check for updates to /.cgminer/cgminer.conf and overwrite /etc/bamt/cgminer.conf . This will restore your customers pools in the event that you need to reboot/power outage/etc. Unfortunately the cgminer.conf created is a bit over-complicated, and duplicates values for each of your GPUs, even if the values are the same for all of them... regardless it does work, and is the best for the customer.

Login to your BAMT box using ssh and perform the following:
sudo crontab -e
Add the following to the bottom of the crontab (This will check for updates every 5 minutes and only overwrite when changes are made)
Code:
*/5 * * * * cp -u /.cgminer/cgminer.conf /etc/bamt/cgminer.conf >/dev/null 2>&1
Exit (and save)


Also, please keep in mind that SMOS linux has a script that will periodically mine for the developers, thus robbing your customers of time. Use BAMT or SMOS bee edition

[zneww]

I will try to make this as simple as it gets as a revised version of guide (Method B) this is if you have a static ip and are using a config file (BAMT)

Forward your port, standard in BAMT is 4028. So you can do that for now, I suggest changing it however for security reasons.
- Go to http://checkmyports.com/ on your miner and see if it is open. If it is then you are good. Also, if you do not know your external IP this is where you can obtain it easily as you will need it for LeaseRig.

Configure cgminer, bfgminer,...(since many miners share same API, just follow this regardless of which miner you use)

You have to enable API listening on your cgminer. Following config options have to be added in cgminer config

Code:

"api-port" : "4028", (this will be whatever port you have forwarded)
"api-allow" : "P:23.236.58.114,W:127.0.0.1",
"api-groups" : "P:switchpool:addpool:removepool:restart:save:*"

Then go to your LeaseRig admin page, configuration, then put your externalIP:port into "Mining rig address (including port)*:"  So it should look something like this "Mining rig address (including port)*: 50.122.333.222:4028"

Update, enable your rig. And you should be good to go.

You will also want to do this:

FYI, for those using BAMT, the save call in the api will create a new cgminer.conf under /.cgminer/cgminer.conf  .
This is of course useless since BAMT starts cgminer pointed to /etc/bamt/cgminer.conf

A workaround is to schedule a job to check for updates to /.cgminer/cgminer.conf and overwrite /etc/bamt/cgminer.conf . This will restore your customers pools in the event that you need to reboot/power outage/etc. Unfortunately the cgminer.conf created is a bit over-complicated, and duplicates values for each of your GPUs, even if the values are the same for all of them... regardless it does work, and is the best for the customer.

Login to your BAMT box using ssh and perform the following:
sudo crontab -e
Add the following to the bottom of the crontab (This will check for updates every 5 minutes and only overwrite when changes are made)
Code:

Code:

*/5 * * * * cp -u /.cgminer/cgminer.conf /etc/bamt/cgminer.conf >/dev/null 2>&1

Exit (and save)


Also, please keep in mind that SMOS linux has a script that will periodically mine for the developers, thus robbing your customers of time. Use BAMT or SMOS bee edition, or manually remove the offending code.