Topic: [ANN][POOLS] CryptoNote Universal Pool Solution (Read 39397 times)
We are about to revitalize all this with the Van Kush Family.
Hi all, I've got my pool up and running on Ubuntu no problem. I can connect and mine just fine using the direct ip, but I'm trying to figure out this part: "Simply host the contents of the website_example directory on file server capable of serving simple static files."
I'm not very familiar with how this works, and would love to have the front-end available for statistics and such. If anyone wants to PM me and let me know what I'm missing, that would be awesome, I'm sure it's something simple.
I'm not very familiar with how this works, and would love to have the front-end available for statistics and such. If anyone wants to PM me and let me know what I'm missing, that would be awesome, I'm sure it's something simple.
Please check your daemon version and your daemon port is opened. try with the bind port also.
My pool is not running.
The daemon is runing same server. The simplewallet run in rpc mode. The ip and port in the config are setting...
Error messages:
2018-10-02 11:01:27 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:28 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:28 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:40 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:40 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:41 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:41 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:42 [api] Error getting daemon data {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:42 [api] Stat collection finished: 3 ms redis, 5 ms daemon
2018-10-02 11:01:42 [api] Error collecting all stats
2018-10-02 11:01:42 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:42 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
The daemon is runing same server. The simplewallet run in rpc mode. The ip and port in the config are setting...
Error messages:
2018-10-02 11:01:27 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:28 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:28 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:40 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:40 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:41 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:41 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:42 [api] Error getting daemon data {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:42 [api] Stat collection finished: 3 ms redis, 5 ms daemon
2018-10-02 11:01:42 [api] Error collecting all stats
2018-10-02 11:01:42 [pool] (Thread 1) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
2018-10-02 11:01:42 [pool] (Thread 2) Error polling getblocktemplate {"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
I have successfully run fancoder, zone117x, but I can't seem to get sadbatman running.
The issue?
node init.js
Failed to read config file config.json
Error: ENOENT, no such file or directory 'config.json'
/home/poolname/pool/lib/logger.js:16
var logDir = config.logging.files.directory;
^
ReferenceError: config is not defined
at Object. (/home/bruceleeon/pool/lib/logger.js:16:14)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/bruceleeon/pool/init.js:10:1)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
config.json is present and configured, anyone wanna take a stab at it?
The issue?
node init.js
Failed to read config file config.json
Error: ENOENT, no such file or directory 'config.json'
/home/poolname/pool/lib/logger.js:16
var logDir = config.logging.files.directory;
^
ReferenceError: config is not defined
at Object.
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
config.json is present and configured, anyone wanna take a stab at it?
cd to your pool directory, and do an ls -al
where I can find api description?
I seem to have everything setup correctly, workers can connect, stats look ok, wallet/daemon both say "ok" in the monitoring section, but I have a unlocker_info.log full of:
It's going on three days now. The only other line in the log is "Started".
Is this normal? I couldn't find anything that tells me one way or another. The googled issues are related to a disconnected daemon or wallet - but mine appear to be connecting just fine. I haven't unlocked a block yet so I thought I would clear this up in case I was wasting hashes.
Thanks!
Code:
2018-03-15 20:46:42 No blocks candidates in redis
2018-03-15 20:47:12 No blocks candidates in redis
2018-03-15 20:47:42 No blocks candidates in redis
2018-03-15 20:48:12 No blocks candidates in redis
2018-03-15 20:48:42 No blocks candidates in redis
2018-03-15 20:49:12 No blocks candidates in redis
2018-03-15 20:49:42 No blocks candidates in redis
2018-03-15 20:50:12 No blocks candidates in redis
2018-03-15 20:50:42 No blocks candidates in redis
2018-03-15 20:51:12 No blocks candidates in redis
2018-03-15 20:51:42 No blocks candidates in redis
2018-03-15 20:52:12 No blocks candidates in redis
It's going on three days now. The only other line in the log is "Started".
Is this normal? I couldn't find anything that tells me one way or another. The googled issues are related to a disconnected daemon or wallet - but mine appear to be connecting just fine. I haven't unlocked a block yet so I thought I would clear this up in case I was wasting hashes.
Thanks!
That is normal logs if you haven't found a block. It is just the unlocker running on it's periodic interval, then informing that there are no blocks to unlock yet.
I seem to have everything setup correctly, workers can connect, stats look ok, wallet/daemon both say "ok" in the monitoring section, but I have a unlocker_info.log full of:
It's going on three days now. The only other line in the log is "Started".
Is this normal? I couldn't find anything that tells me one way or another. The googled issues are related to a disconnected daemon or wallet - but mine appear to be connecting just fine. I haven't unlocked a block yet so I thought I would clear this up in case I was wasting hashes.
Thanks!
Code:
2018-03-15 20:46:42 No blocks candidates in redis
2018-03-15 20:47:12 No blocks candidates in redis
2018-03-15 20:47:42 No blocks candidates in redis
2018-03-15 20:48:12 No blocks candidates in redis
2018-03-15 20:48:42 No blocks candidates in redis
2018-03-15 20:49:12 No blocks candidates in redis
2018-03-15 20:49:42 No blocks candidates in redis
2018-03-15 20:50:12 No blocks candidates in redis
2018-03-15 20:50:42 No blocks candidates in redis
2018-03-15 20:51:12 No blocks candidates in redis
2018-03-15 20:51:42 No blocks candidates in redis
2018-03-15 20:52:12 No blocks candidates in redis
It's going on three days now. The only other line in the log is "Started".
Is this normal? I couldn't find anything that tells me one way or another. The googled issues are related to a disconnected daemon or wallet - but mine appear to be connecting just fine. I haven't unlocked a block yet so I thought I would clear this up in case I was wasting hashes.
Thanks!
Are there any paid scripts?
The open source is awful to install without help.
I have tried everything and I can not make it work, is there no tutorial for this?
What is not working? I used both the original and now the SadBatman version (with more features) and it is pretty straightforward. Just follow the steps in the USAGE.md (https://github.com/SadBatman/cryptonote-sumokoin-pool/blob/master/USAGE.md). The open source is awful to install without help.
I have tried everything and I can not make it work, is there no tutorial for this?
Are there any paid scripts?
The open source is awful to install without help.
I have tried everything and I can not make it work, is there no tutorial for this?
The open source is awful to install without help.
I have tried everything and I can not make it work, is there no tutorial for this?
https://supportcryptonight.com Nodejs-pools AEON, ETN, GRAFT, IPBC
Open code for all coins on github.com/ArqTras
Open code for all coins on github.com/ArqTras
Just use older node version. Use nvm
Nothing works right.
Unable to install.
Errors and more mistakes.
Make a video showing how to install.
Very confusing
Unable to install.
Errors and more mistakes.
Make a video showing how to install.
Very confusing
Having recently set up a couple of pools using cryptonote-sumokoin-pool, one for ETN, another for SUMO and more planned for the future. I still have two outstanding items I would really appreciate some help with and I'm hoping this might be the place to ask. Regardless...
1. First is that it's not clear to me how you go about setting multiple sites in different GEOs and linking them together.
2. Second I've also not been able to get either site to run over HTTPS using Apache2 (my preference) or NGINX with the configuration sample. I can serve the content of /website over SSL easily enough but I just can't seem to get the APIs working, with the site displaying it's health status message.
Anyway, any help or direction on either topic would be gratefully received.
Thanks!
Hugh
1. First is that it's not clear to me how you go about setting multiple sites in different GEOs and linking them together.
2. Second I've also not been able to get either site to run over HTTPS using Apache2 (my preference) or NGINX with the configuration sample. I can serve the content of /website over SSL easily enough but I just can't seem to get the APIs working, with the site displaying it's health status message.
Anyway, any help or direction on either topic would be gratefully received.
Thanks!
Hugh
I have a question and I hope that someone can help me out.
I installed this pool and everything seems to be running right except for the wallet RPC perhaps?
In the admin panel I get fail and the error is { }. (Note, that there isn't an error descriptor between the brackets)
It is driving me nuts because I don't even have search terms to look for a solution.
I will try to give ya as much info as I can:
I have the blockchain synced, the wallet RPC going (at log level-2) and just showing green and blue info/blocks received ...etc, and I can connect miners to the pool. When I have the RPC going and go to my admin page I get this error:
https://i.stack.imgur.com/2CS9Z.jpg
The wallet RPC does not hang and continues to refresh INFO and DEBUG info.
I tried binding a different port in the command line and making sure it was also set in config.json wallet area and forwarding that port all to no avail. Can anyone point me to help? With the lack of information for the error it is making researching it near impossible. What would the error { } mean? I have looked at many related posts. I can duplicate their errors and resolve them (ERRCONNECT..etc) using 127.0.0.1 in the wallet area and bind that ip and port 8082 to the wallet but I get the { } error and the fail still. If someone could help me out I would really appreciate it. It is just so weird that it doesn't describe the error (I.E. "syscall" etc.)
I installed this pool and everything seems to be running right except for the wallet RPC perhaps?
In the admin panel I get fail and the error is { }. (Note, that there isn't an error descriptor between the brackets)
It is driving me nuts because I don't even have search terms to look for a solution.
I will try to give ya as much info as I can:
I have the blockchain synced, the wallet RPC going (at log level-2) and just showing green
Code:
DEBUG
Code:
INFO
https://i.stack.imgur.com/2CS9Z.jpg
The wallet RPC does not hang and continues to refresh INFO and DEBUG info.
Code:
config.json
Code:
{
"coin": "Monero",
"symbol": "XMR",
"coinUnits": 100000000,
"coinDifficultyTarget": 120,
"logging": {
"files": {
"level": "info",
"directory": "logs",
"flushInterval": 5
},
"console": {
"level": "info",
"colors": true
}
},
"poolServer": {
"enabled": true,
"clusterForks": "auto",
"poolAddress": "44XjW8cg418JmtooiVgKzUCnQFbMEzkFtD1mW2fqDCQSgv5hok4QfZzQuRCKWydkrYik8Vj3VaLc22zLDFRW7EtDJyGS6jR",
"addressBase58Prefix": 18,
"blockRefreshInterval": 1000,
"minerTimeout": 900,
"ports": [
{
"port": 3333,
"difficulty": 100,
"desc": "Low end hardware"
},
{
"port": 5555,
"difficulty": 2000,
"desc": "Mid range hardware"
},
{
"port": 7777,
"difficulty": 10000,
"desc": "High end hardware"
},
{
"port": 8888,
"difficulty": 10000,
"desc": "Hidden port",
"hidden": true
}
],
"varDiff": {
"minDiff": 2,
"maxDiff": 100000,
"targetTime": 100,
"retargetTime": 30,
"variancePercent": 30,
"maxJump": 100
},
"fixedDiff": {
"enabled": true,
"addressSeparator": "."
},
"shareTrust": {
"enabled": true,
"min": 10,
"stepDown": 3,
"threshold": 10,
"penalty": 30
},
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 25,
"checkThreshold": 30
}
},
"payments": {
"enabled": true,
"interval": 600,
"maxAddresses": 50,
"mixin": 3,
"transferFee": 5000,
"minPayment": 3000000,
"denomination": 1000
},
"blockUnlocker": {
"enabled": true,
"interval": 30,
"depth": 60,
"poolFee": 0.45,
"devDonation": 0.001,
"coreDevDonation": 0.001,
"extraFeaturesDevDonation": 0
},
"api": {
"enabled": true,
"hashrateWindow": 600,
"updateInterval": 5,
"port": 8117,
"blocks": 30,
"payments": 30,
"password": "xxxxxxxxx"
},
"daemon": {
"host": "127.0.0.1",
"port": 18081
},
"wallet": {
"host": "127.0.0.1",
"port": 8082
},
"redis": {
"host": "127.0.0.1",
"port": 6379
},
"monitoring": {
"daemon": {
"checkInterval": 60,
"rpcMethod": "getblockcount"
},
"wallet": {
"checkInterval": 60,
"rpcMethod": "getbalance"
}
},
"charts": {
"pool": {
"hashrate": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"workers": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"difficulty": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"price": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"profit": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
}
},
"user": {
"hashrate": {
"enabled": true,
"updateInterval": 180,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"payments": {
"enabled": true
}
}
}
}I tried binding a different port in the command line and making sure it was also set in config.json wallet area and forwarding that port all to no avail. Can anyone point me to help? With the lack of information for the error it is making researching it near impossible. What would the error { } mean? I have looked at many related posts. I can duplicate their errors and resolve them (ERRCONNECT..etc) using 127.0.0.1 in the wallet area and bind that ip and port 8082 to the wallet but I get the { } error and the fail still. If someone could help me out I would really appreciate it. It is just so weird that it doesn't describe the error (I.E. "syscall" etc.)
The sumokoin project has a well maintained cryptonote pool fork here:
https://github.com/SadBatman/cryptonote-sumokoin-pool/
Changes we added to this fork are, amongst others:
We also have a Telegram group where we discuss new development projects and can assist if you have problems running our fork.
https://t.me/joinchat/Hkpz6hIFOy4qGqMHTDzn1A
If you are a pool admin; come and have a look at our fork!
Hello,https://github.com/SadBatman/cryptonote-sumokoin-pool/
Changes we added to this fork are, amongst others:
- Email notifications
- Miner controlled minimum payout rates
- Health monitoring in the web UI (e.g. see when the pool's wallet is down)
- Improved proxy support
We also have a Telegram group where we discuss new development projects and can assist if you have problems running our fork.
https://t.me/joinchat/Hkpz6hIFOy4qGqMHTDzn1A
If you are a pool admin; come and have a look at our fork!
I try but fail at: [api] Error getting deamon data {"code":"ECONNRESET"}. daemon is running already and correct p2p port.
And now i am back to the binding.js error and multi-hashing.
Can anyone shed any light on this?
Can anyone shed any light on this?
HELP! 
When I run node init.js
I have take this http://prntscr.com/i424y1
What's wrong.....?
All modules work except a pool
When I run node init.js
I have take this http://prntscr.com/i424y1
What's wrong.....?
All modules work except a pool
I ran into this issue last night, and now I have another issue but i solved by
- using NVM change to nodejs to version 6
- removing node_modules folder
- then NPM install
- and then doing the following found here, https://github.com/zone117x/node-multi-hashing/issues/31
Code:
apt-get install -y build-essential git
cd node_modules
git clone https://github.com/UNOMP/node-multi-hashing
cd node-multi-hashing
git fetch origin pull/5/head:BRANCHNAME
git checkout BRANCHNAME
npm install
Appears to have sorted it for me, but now I have an issue with bignum and it expect version 48 and getting 46
HELP!
When I run node init.js
I have take this http://prntscr.com/i424y1
What's wrong.....?
All modules work except a pool
When I run node init.js
I have take this http://prntscr.com/i424y1
What's wrong.....?
All modules work except a pool
Jump to: