Topic: [GUIDE] How to rent your rig on LEASERIG.NET - Scrypt & SHA256 - page 12. (Read 33446 times)

Updated proxy; changelog is:


All providers using linux, you this update is mandatory. It should fix all crashes happening on linux.

Try to install: http://sourceware.org/ml/libc-alpha/2012-03/msg00836.html

When running the proxy with SMOS I get


Any ideas?  I am using V 0.03b

Could you give me some login details for this pool (PM me), will test on my own and see what happens.

I'm getting the same problem. I'm running the proxy on a VM, and trying to direct my AntMiners to them. The pools.conf has one starting pool, which is not itself (It's slush's, to be exact). The Antminer only has one pool, which is IP:3333 of the proxy VM. They're on the same network, and can ping each other.

It sits there for a while, and as soon as I start CGMiner on the AntMiner, the proxy crashes.

Listening on 3333 for miners
Connecting to LeaseRig.net
Pool connection established: stratum.bitcoin.cz:3333
Connected to LeaseRig.net
Pool authorized: stratum.bitcoin.cz:3333
Authorized with LeaseRig.net
*Sits here for a while, and as soon as I connect a miner, the following lines all show up, and then it closes*
--10.0.4.101:53767->rig connected
--10.0.4.101:53767->connecting to pool stratum.bitcoin.cz:3333
--10.0.4.101:53767->pool connection established
--10.0.4.101:53767->rig disconnected
--10.0.4.101:53768->rig connected
--10.0.4.101:53768->connecting to pool stratum.bitcoin.cz:3333
--10.0.4.101:53768->pool connection established
--10.0.4.101:53768->rig disconnected
--10.0.4.101:53769->rig connected
--10.0.4.101:53769->connecting to pool stratum.bitcoin.cz:3333
--10.0.4.101:53769->pool connection established
--10.0.4.101:53769->pool diff: 3
--10.0.4.101:53769->rig disconnected
--10.0.4.101:53770->rig connected
--10.0.4.101:53770->connecting to pool stratum.bitcoin.cz:3333
--10.0.4.101:53770->pool connection established
--10.0.4.101:53770->pool diff: 3

If you are referring to the possibility of proxy crashing, then the easy solution is to make a script which auto-restarts it in case of crashing. Pools are saved in file after each modification, and everything is established back when proxy is started again (connection with LeaseRig, pools are loaded again, cgminers attempt new connection to proxy after few seconds). I personally haven't experienced any crash yet, nor I got any reports of crashing proxy. It should be pretty stable.

From the latest version I just downloaded, looks like it's already been fixed.

v0.03b
- fixed issue of some stratum pools not being supported
- linux executable is now 32-bit

Also many thanks to djeZo for working through some problems with my SHA256 rigs (hence the v0.02 and v0.03 !!)

Any chance of getting a 32bit compiled version of LeaseRigProxy for those of us running BAMT? Also do you have any ideas for setting this up redundantly (I don't want LeaseRigProxy to be a single point of failure)?

Thanks.

Updated proxy to version 0.03b. Update is recommended, because some stratum pools did not work with previous releases.

I get the error: can not execute this binary file?
when trying to run the stratum.

Also anyone know of a solution to add this so it starts up before cgminer within BAMT? and for it to check that its running / restart if not..?

UPDATE: BAMT = 32bit and the provided binary for the stratum is 64bit.

Yes, it is actually a stratum proxy. I have plans to expand it to support getwork&getblocktemplate HTTP requests, then even solo mining will be possible.

djeZo,

So, if i'm understanding this correctly, the applet essentially works as a stratum server that your miner is pointed to which is then uplinked to the leaserig website?

If so, this sounds great since I will be receiving a bunch of gridseed miners tomorrow and I was scratching my head how to get them to work with Leaserig.  Now i'll just run the applet from my HTPC and point all the miners to it's IP as my pool address.

Just read the Readme and it sounds like this might be the solution I was looking for!  Now I just gotta sit here refreshing delivery details and wait for DHL to arrive....

-Eric

By any chance did you put pool 127.0.0.1:3333 into pools.conf file? If yes, then you created a infinite connecting loop which will eventually use all sockets and crash. 127.0.0.1:3333 should be used in your cgminer!

I executed ...

and got this error message, using my actual generated ID on LeaseRig ...

Added:

A. Simple method

1. STEP: Contact me (djeZo) - send me PM

If you are newbie with no reputation on this forum, send me PM with request to get listed, but tell me total speed of the rigs you would like to put on.

I will return to you with deposit amount. After deposit is made, send me PM and include:
- mining rig names (choose on your own - alphanumeric characters)
- your trust/reputation thread (this is mandatory so customers can post feedback there)

I will reply to you with access to admin panel on LeaseRig.net.

2. STEP: Setup LeaseRig Proxy

Download LeaseRig Proxy Software (Windows&Linux). Detailed instructions are in README.txt file. But to sum it up with an example if you have one rig to offer.

1. Extract all files.
2. Open pools.conf and configure your starting pools.
3. Edit run.bat file - change PUT-YOUR-ID-HERE with ID you get on admin panel.
4. Double click run.bat to run it.
5. Configure your mining rig to use pool:

stratum+tcp://127.0.0.1:3333

THAT IS ALL. However, there are some more advanced options which you would like to check out (such as realtime speed stats). Just read README.txt file. You can connect as many as you like rigs to this proxy and total hash power will be increased.

A simple py script could be written to do this via admin panel.

I'm a newbie here trying to config my miner to work with leaserig.
Everything seems clear and almost the whole config is done but i have one question.
I'm actually mining rotating over 4 pools every 2 hours and i would like to keep this config even with leaserig.
Is it possible to configure the sgminer to rotate over 4 pools only when the miner is not for renting?
I mean:
1) sgminer starts with my actual rotate pools config
2) sgminer switches to mine for the customer's pool in case of renting
3) sgminer switches back in my rotate config at the end of the rental period.
What do you think, is it possible? If yes where to put the configuration?
Rotation option in command line and the pools in sgminer.config?
Thanks for your precious help!

FYI. Leave the default log interval of 5 seconds alone when configuring cgminer. LeaseRigs cannot parse other than 1 or 5 second values according to a prompt PM conversation with djeZo. The administration POOLS panel reported accepted share values OK but each rig was getting set disabled. We fixed everything by resetting the cgminer log interval.

Try to contact existing 2 providers with jupiters. I heard that it is actually pretty simple.

Anyone have any experience getting KNCminer's Jupiter working with this?