But well, I'm not fast enough due to real life work load.
Topic: [ANNOUNCE] ecoinpool - A brand new pool mining software written in Erlang - page 5. (Read 28503 times)
March 02, 2012, 03:13:27 AM
It's kind of funny that there are now bounties for setting ecoinpool up while I'm working on the bugs and features which will make setting up so easy that everyone should be able to do it
But well, I'm not fast enough due to real life work load.
But well, I'm not fast enough due to real life work load.
March 01, 2012, 11:12:41 AM
Is anyone interested in setting this up for a bounty. Please pm me if you are. I'm interested in mining on it with a few friends. Thanks.
February 21, 2012, 06:35:56 AM
Sweet, two ltc blocks in a row for us last night!
February 20, 2012, 11:21:05 PM
I would like to post a BTC bounty for anyone who can assist me in the final stages of getting this all working. I think I have about 95% of the pool set up but I just can't seem to get the last little bit figured out. I have installed all the files onto a dedicated linux server. I have followed all directions and just can't seem to get the results of the pool running. Somewhere the setup of the pool has failed and therefore will not start. Please PM me if interested.
February 16, 2012, 04:31:21 PM
Sigh, unlucky lately. No blocks since that first one found, and currently at 119800 shares.
@EnergyVampire I got no idea about your error...
@EnergyVampire I got no idea about your error...
February 16, 2012, 04:14:44 PM
Hello,
I received this error a few times today on the namecoind debug.log:
Have I setup the auxchain wrong somehow? I installed namecoin version 32464 to try and do some merged mining. I haven't found any blocks but I am getting valid shares from couchdb.
Thanks in advance for your replies,
Cheers!
I received this error a few times today on the namecoind debug.log:
Code:
ERROR: ConnectInputsHook() : name_firstupdate Cannot be mined if name_new is not already in chain and unexpired
Have I setup the auxchain wrong somehow? I installed namecoin version 32464 to try and do some merged mining. I haven't found any blocks but I am getting valid shares from couchdb.
Thanks in advance for your replies,
Cheers!
February 16, 2012, 03:22:00 AM
Hi,
sorry I've been busy the last days and will be away the following days too.
Cache size and work age aren't that important for ecoinpool because it can create work so fast that the cache never really gets empty.
Max work age is the time that workunits stay in the cache until they are discarded it mainly has to do how "good" you want to support new transactions coming in. On larger pools, this is never really hit, because work is requested faster than cached workunits are discarded; this could even be true for your small pool.
As for the cache size: It is not printed as an info message how the cache is refilled, you'd have to set the server logger to "debug" to see that. The fact that the number never gets below 19 is because the cache is being refilled to 20 only milliseconds after it was accessed. The value of 20 has been determined by watching the cache on a relatively big pool where the cache got below ~15 in only 2% of all cases (that's mostly on block changes, where the cache has to be drained anyway). Maintaining a cache of 20 workunits should be ok for any server as they just take a couple of cycles to make and only use a few bytes of ram.
The essence of all that I said: It's not really worth changing the default settings for those two values as what you gain from tweaking the numbers is pretty much marginal and will probably never impact work delivery at all. If you're really a perfectionist and want to save ~4kb of RAM and 100ms CPU time, then set the cache size to 10.
p2k
sorry I've been busy the last days and will be away the following days too.
Cache size and work age aren't that important for ecoinpool because it can create work so fast that the cache never really gets empty.
Max work age is the time that workunits stay in the cache until they are discarded it mainly has to do how "good" you want to support new transactions coming in. On larger pools, this is never really hit, because work is requested faster than cached workunits are discarded; this could even be true for your small pool.
As for the cache size: It is not printed as an info message how the cache is refilled, you'd have to set the server logger to "debug" to see that. The fact that the number never gets below 19 is because the cache is being refilled to 20 only milliseconds after it was accessed. The value of 20 has been determined by watching the cache on a relatively big pool where the cache got below ~15 in only 2% of all cases (that's mostly on block changes, where the cache has to be drained anyway). Maintaining a cache of 20 workunits should be ok for any server as they just take a couple of cycles to make and only use a few bytes of ram.
The essence of all that I said: It's not really worth changing the default settings for those two values as what you gain from tweaking the numbers is pretty much marginal and will probably never impact work delivery at all. If you're really a perfectionist and want to save ~4kb of RAM and 100ms CPU time, then set the cache size to 10.
p2k
February 13, 2012, 05:08:23 PM
Oh p2k because I am only going to have 2-5 people mining every night, is it best to lower Max. Cache & Size Max. Work Age a bit lower? If so what do you recommend?
Edit:
So it would be optimal to leave it at 20? Or change it to 19?
Edit:
Code:
[2012-02-13 12:11:20.860][info] ltc_pool: Cache hit by richard/X.X.X.X - Queue size: 19/20
[2012-02-13 12:11:22.700][info] ltc_pool: Cache hit by kitteh/X.X.X.X - Queue size: 19/20
[2012-02-13 12:12:06.745][info] ltc_pool: Cache hit by richard/X.X.X.X - Queue size: 19/20
[2012-02-13 12:12:08.004][info] ltc_pool: Cache hit by kitteh/X.X.X.X - Queue size: 19/20
So it would be optimal to leave it at 20? Or change it to 19?
February 13, 2012, 03:36:37 PM
Nice to know it's up and running. I have been having troubles installing it but I am sure it is a problem on my end. I am in a similar boat to tittiez. I want to create a small pool for me and my friends just a private pool for now. I was wondering about the payout setup but never had to worry cause I couldn't get that far. When I tried to look at ozco.in their site tells me it is down. I wanted to get a look at kind of what things will look like and how the will operate. Tittiez if you have a link I may check out to see running that would be great if not I will plug away until I get it going.
Few Tips:
1. Make sure bitcoind/litecoind are finished downloading blocks (You will know when the blk files stop gaining size that its done)
2. Make sure to be running with server=1, here's my config for ltc:
Code:
server=1
daemon=1
rpcuser=user
rpcpassword=pass
rpcport=9334
port=9335
& the IP to the pool looks like this: http://XXX.XXX.XXX.XXX:9339/ (yes, I set the port to 9339 rather then 8888)
& RPC port under CoinDaemon is 9334
3. I used the exact same user/pass that was already in the example config file for ecoinpool for a user. Only thing I had to change was that two "Replace Me!" passwords.
4. If you have a similar problem to me just PM me, since I had to figure it out myself. No need to bother p2k more.
5.I might be able to help you set up yours
Pics of it working:
http://i.imgur.com/Qd0jZ.png
http://i.imgur.com/2Uc6R.png
http://i.imgur.com/Ga15b.png
February 13, 2012, 12:40:30 PM
Nice to know it's up and running. I have been having troubles installing it but I am sure it is a problem on my end. I am in a similar boat to tittiez. I want to create a small pool for me and my friends just a private pool for now. I was wondering about the payout setup but never had to worry cause I couldn't get that far. When I tried to look at ozco.in their site tells me it is down. I wanted to get a look at kind of what things will look like and how the will operate. Tittiez if you have a link I may check out to see running that would be great if not I will plug away until I get it going.
February 13, 2012, 06:08:23 AM
We solved our first block, yay!
February 13, 2012, 06:05:44 AM
To quote from the README:
I'm not lying in that README, it's true!
Congratz on setting it up, so it was possible to bypass the frontend error messages involved in first worker creation. Good to know.
p2k
Quote
... Daemons which support local work creation through the getmemorypool call will have two extra fields "Pay To" and "Tag". The former will override the default payout address on block solves; if you leave it empty, ecoinpool will create an account called "ecoinpool" via RPC call and use this one for payout ...
I'm not lying in that README, it's true!
Congratz on setting it up, so it was possible to bypass the frontend error messages involved in first worker creation. Good to know.
p2k
Yes I did get those frontend errors, all I had to do was disable the pool and suddenly the databases for the workers were created.
February 13, 2012, 02:22:15 AM
To quote from the README:
I'm not lying in that README, it's true!
Congratz on setting it up, so it was possible to bypass the frontend error messages involved in first worker creation. Good to know.
p2k
Quote
... Daemons which support local work creation through the getmemorypool call will have two extra fields "Pay To" and "Tag". The former will override the default payout address on block solves; if you leave it empty, ecoinpool will create an account called "ecoinpool" via RPC call and use this one for payout ...
I'm not lying in that README, it's true!
Congratz on setting it up, so it was possible to bypass the frontend error messages involved in first worker creation. Good to know.
p2k
February 12, 2012, 11:36:23 PM
So if we find a block it pays out to the "Pay To:" address I put into CoinDaemon, right?
February 12, 2012, 10:21:09 PM
Also @Tittiez: I've heard that you want to start your own private pool with some friends. Keep in mind that ecoinpool currently doesn't have any payout mechanisms (neither do PoolserverJ nor pushpool), so you would have to manage that yourself. There is another ticket on my tracker that promises payout support for a future release, making ecoinpool the true all-in-one backend solution for mining. But - as you can imagine - it's a lot of work to get there.
p2k
p2k
Not a problem, we decided we would all split the blocks evenly anyway, its a lot easier that way. Oh and I got it working!
Code:
[07:18:54.068][ebitcoin/warn] ltc_block: Connecting to localhost:9335...
[07:18:54.071][ebitcoin/warn] ltc_block: Connection established.
[07:18:54.084][server/warn] Subpool b2fcfae2039213c8ae671ecc77006547 starting...
[07:18:54.170][ebitcoin/warn] ltc_block: Entering resync mode, getting 49745 block(s)...
[07:18:54.197][default/warn] ecoinpool_rpc: Started RPC on port 9339
[07:18:54.199][daemon/warn] SCrypt-ltc CoinDaemon starting...
[07:18:54.388][server/warn] ltc_pool: --- New main block! Assigned: 0; Shares: 0; Cached: 0; Longpolling: 0 ---
Got a few of my friends pointing their miners to my pool, its working fine now. Thanks!
February 12, 2012, 05:07:32 PM
Thanks Graet!
And I will take this opportunity to say that ecoinpool is running on ozco.in with very special settings which are not yet covered by the built-in frontend, all of them are listed on the ticket (<- click me!). I had to help ozco.in at great lengths and most of the features on that list were actually developed to get eco to work ozco.in.
However, I will fix this up in some days (I'm currently blocked by RL jobs, shadders, your chance to catch up) making ecoinpool as easy to setup as it is meant to be and removing the pressure on me that I always have to be around if something has to be changed in the configuration etc. Yes, with ozco.in being currently the only pool which uses eco on a large basis, it's still ok for me; but I don't want to be responsible for the inner workings of all the pools in the world in the end... I'm only one guy... (yeah, ok, I claim that I'm a one-man-army, but even an army can run out of troops)
Also @Tittiez: I've heard that you want to start your own private pool with some friends. Keep in mind that ecoinpool currently doesn't have any payout mechanisms (neither do PoolserverJ nor pushpool), so you would have to manage that yourself. There is another ticket on my tracker that promises payout support for a future release, making ecoinpool the true all-in-one backend solution for mining. But - as you can imagine - it's a lot of work to get there.
p2k
And I will take this opportunity to say that ecoinpool is running on ozco.in with very special settings which are not yet covered by the built-in frontend, all of them are listed on the ticket (<- click me!). I had to help ozco.in at great lengths and most of the features on that list were actually developed to get eco to work ozco.in.
However, I will fix this up in some days (I'm currently blocked by RL jobs, shadders, your chance to catch up) making ecoinpool as easy to setup as it is meant to be and removing the pressure on me that I always have to be around if something has to be changed in the configuration etc. Yes, with ozco.in being currently the only pool which uses eco on a large basis, it's still ok for me; but I don't want to be responsible for the inner workings of all the pools in the world in the end... I'm only one guy... (yeah, ok, I claim that I'm a one-man-army, but even an army can run out of troops
)Also @Tittiez: I've heard that you want to start your own private pool with some friends. Keep in mind that ecoinpool currently doesn't have any payout mechanisms (neither do PoolserverJ nor pushpool), so you would have to manage that yourself. There is another ticket on my tracker that promises payout support for a future release, making ecoinpool the true all-in-one backend solution for mining. But - as you can imagine - it's a lot of work to get there.
p2k
February 12, 2012, 02:29:21 PM
God I am making such simple errors over and over again, I really need to start sleeping. I swear I had it running though! I'm using 0.6.0rc1 64bit bitcoind.
Bitcoind and the couchdb are both running, I get this at pool startup:
http://pastebin.com/KcwAE47N
Some other simple dumbass mistake I presume?
"{\"result\":null,\"error\":{\"code\":-10,\"message\":\"Bitcoin is downloading blocks...\"},\"id\":null}\n"}},Bitcoind and the couchdb are both running, I get this at pool startup:
http://pastebin.com/KcwAE47N
Some other simple dumbass mistake I presume?
until it is synced it will crash, see p2k's post above
Very impressed with ecoinpool. We have been running ~4-500Ghash most of the day and the servers barely get out of idle
February 12, 2012, 10:22:01 AM
God I am making such simple errors over and over again, I really need to start sleeping. I swear I had it running though! I'm using 0.6.0rc1 64bit bitcoind.
Bitcoind and the couchdb are both running, I get this at pool startup:
http://pastebin.com/KcwAE47N
Some other simple dumbass mistake I presume?
Bitcoind and the couchdb are both running, I get this at pool startup:
http://pastebin.com/KcwAE47N
Some other simple dumbass mistake I presume?
February 12, 2012, 04:38:52 AM
This error tells us that ecoinpool could not connect to the local bitcoind. Either it is not running, or you've set it to another port than the default 8332 in your bitcoin.conf. In the later case, you can configure ecoinpool to use a different port in the CoinDaemon configuration dialog of your Subpool.
In general, ecoinpool is currently not very tolerant towards any errors you might have in your CoinDaemon configuration and if bitcoind is still loading blocks or crashes, ecoinpool will terminate as well. It is on my todo list to even this out and present you a more informative error message and let ecoinpool reconnect on errors etc.
Also, while helping EnergyVampire to set it up, I've discovered some more problems with the built-in frontend that have to be fixed. We used a not-so-easy workaround to get it running. For you and others, it would be better if you could wait until I've fixed those problems properly; you can subscribe to the tracking ticket via RSS. The first ticket entry is a blocker, as it is not possible to create your first worker properly. Please be patient, you won't regret it.
p2k
In general, ecoinpool is currently not very tolerant towards any errors you might have in your CoinDaemon configuration and if bitcoind is still loading blocks or crashes, ecoinpool will terminate as well. It is on my todo list to even this out and present you a more informative error message and let ecoinpool reconnect on errors etc.
Also, while helping EnergyVampire to set it up, I've discovered some more problems with the built-in frontend that have to be fixed. We used a not-so-easy workaround to get it running. For you and others, it would be better if you could wait until I've fixed those problems properly; you can subscribe to the tracking ticket via RSS. The first ticket entry is a blocker, as it is not possible to create your first worker properly. Please be patient, you won't regret it.
p2k
February 11, 2012, 08:14:34 PM
Realized my VPS was too cluttered, so I decided to reinstall it altogether.
So this is on a fresh Ubuntu Server 11.04 Installation:
I go to startup a testpool, and I get this error message:
http://pastebin.com/kfP55yKd
Exact same one I had earlier today.
Since it works fine others I assume its my own fault and has something to do with the config correct?
So this is on a fresh Ubuntu Server 11.04 Installation:
I go to startup a testpool, and I get this error message:
http://pastebin.com/kfP55yKd
Exact same one I had earlier today.
Since it works fine others I assume its my own fault and has something to do with the config correct?
Jump to: