Lex Pool (A rewritten pool based on uray source)
-
module.exports = { wallets : [ { walletIP : '127.0.0.1', walletPort : 8125, walletUrl : 'http://127.0.0.1:8125' } ], redirection : { enabled : false, target : 'http://lhc.ddns.net:8124' }, walletIndex: 0, blockMature : 1, txFeePercent : 0.0005, devFee : true, devFeePercent : 0.01, poolFee : 0.0015, poolDiff : 1000000, poolDiffCurve : 0.75, poolPort : 8124, poolPvtKey : 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', poolPublicRS : 'BURST-FK53-NKRM-42M2-32XJP', poolPublic : '1928561693545645153', poolFeePaymentAddr : '1928561693545645153', defaultPaymentDeadline : 1440, poolFeePaymentTxFeeNQT : 100000000, httpPort : 80, websocketPort : 4443, enablePayment : true, minimumPayout : 250.0, clearingMinPayout : 2.0, lastSessionFile : 'last-session.json', cumulativeFundReduction : 0.5, nextBlockFundSaving : 0.5, logWebsocketToConsole : false, maxRoundCount : 97, sharePenalty : 0.001, maxRecentPaymentHistory : 50 };and here is the port forward config from my router
D Service Port Internal Port IP Address Protocol Status Modify 1 80 8080 192.168.1.20 TCP Enabled Modify Delete
-
Do you have port 8080, 8125, 8124, 8123, 4443 Port forward for your pool and wallet? install latest jre and nodejs 4.4.7 and it should at least work locally. The rest you already know I assume.
-
I've got the latest jre and nodejs 4.4.7
Tried setting the http port to 8080 in the pool config but then the script fails with this errorgazda@ubuntu16:/var/www/burstpool$ sudo node burst-pool.js genesis base target = 18325193796 current timestamp 1492949663312 genesis-block blocktime 85227263 genesis-block timestamp 1407722400312 burst pool running on port 8124 websocket running on port 4443 Error: listen EADDRINUSE :::8080 at Object.exports._errnoException (util.js:907:11) at exports._exceptionWithHostPort (util.js:930:20) at Server._listen2 (net.js:1253:14) at listen (net.js:1289:10) at Server.listen (net.js:1385:5) at EventEmitter.app.listen (/var/www/burstpool/node_modules/express/lib/application.js:559:24) at initWebserver (/var/www/burstpool/burst-pool-protocol.js:202:9) at Object.module.exports.start (/var/www/burstpool/burst-pool-protocol.js:262:13) at /var/www/burstpool/burst-pool.js:236:30 at /var/www/burstpool/node_modules/async/lib/async.js:254:17 cleanIs that maybe the problem? Also, I honestly don't know where I should be setting up these port forwards for my localhost, somewhere in apache?
Would you share your web server config with me please?
-
ok 2 things I had to do to get my pool to work on my vpu (ubuntu) 1 I had to start the pool as root 2 I had to make sure all was in lower case in the client folder (think charts.js was Charts.js) If I think of anything else I will tell you.
Actually you only have to do that. When my vps is going for maintenance I go to webmin download pool and just have to start it and it works. My server at home is windows so the code works both ways. Those other ports have to be open too or it will only work local.
-
I try a test pool at home on a different port like 8081. edited works with other port. I would try what I said about root.
edit I talked to lexicon and he reminded me its Charts has to be in lower case in the client file!
-
"charts" is the solution. :-)
Thank you both for your time.
-
I too am have the no data on the site problem opened all the port mentioned above changed the C to c although I don't think it matters on windows I also made sure I ran burst-pool.js as admin and I am kinda out of ideas at this point any help would be greatly appreciated.

//module.exports = { wallets : [ { walletIP : '127.0.0.1', walletPort : 8125, walletUrl : 'http://127.0.0.1:8125' } ], redirection : { enabled : false, target : 'http://lhc.ddns.net:8124', }, walletIndex: 0, blockMature : 1, txFeePercent : 0.0005, devFee : true, devFeePercent : 0.01, poolFee : 0.01, poolDiff : 1000000, poolDiffCurve : 0.75, poolPort : 8124, poolPvtKey : 'Wallet Passphase here', poolPublicRS : 'BURST-BYHH-ETPK-49NE-BJUVV', poolPublic : '11380403184201955823', poolFeePaymentAddr : '8753115353486582411', defaultPaymentDeadline : 1440, poolFeePaymentTxFeeNQT : 100000000, httpPort : 80, websocketPort : 4443, enablePayment : true, minimumPayout : 250.0, clearingMinPayout : 2.0, lastSessionFile : 'last-session.json', cumulativeFundReduction : 0.5, logWebsocketToConsole : false, maxRoundCount : 800, sharePenalty : 0.001, maxRecentPaymentHistory : 50``
-
try node.js 4.4.7 otherwise looks correct. I would change the maxroundcount to 360 I ran 180 for the longest time but dropped it to cut down whats loading every block.
-
switched to node.js 4.4.7 tried x64 and 86 versions still didnt help miner is reporting DL's i can see them in the terminal window its just not making it to the site. just to make sure i have all the ports open it's 80, 8125, 8124, 8123, 4443 all tcp right? after this I am all out for ideas ;[
-
I never had that happen and I run test pools all the time. Maybe java version?
-
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
-
Have you opened the ports on your firewall? just because it is running in localhost still means you need to add the ports to your windows firewall :) to test if this is it, shut down the firewall for a sec, then try it
-
@Lexicon ,
Questions about setting up this pool?
-
node.js current version is v6.10.3. Should I use this or do I have to find 4.4.7?
-
the current version has a windows installer. If I have to use old source files, how do I install them in a win 10 OS?
-
Above instructions say to run "start pool.cmd". There is no file pool.cmd in the folder "burst-pool-master that I downloaded from your Github site.
-
The folder I loaded does not have all the folders as shown in the OP, like "nbproject" and "node_modules" am I missing something?
-
For the burst-pool-config.js lines:
wallets : [
{
walletIP : '127.0.0.1',
walletPort : 8125,
walletUrl : 'http://127.0.0.1:8125'
}
],
redirection : {
enabled : true,
target : 'http://127.0.0.1:8105'
},
walletIndex: 0,Does this mean the pool is connected to the port 8125 wallet but if it gets stuck it will go to my other wallet running on port 8105?
- Do I change wallet index if I set direction to true?
Thanks for your help.
-
-
@rds use node v5. v6 breaks a lot of stuff.
ill get back to your other questions shortly. still going through hell.
-
@Lexicon , thanks, no rush this is a slow work in progress for me, trying to learn something out of my comfort zone :)
-
Ok this is going to be my final attempt to get this sucka to work I switched from windows server to Ubuntu 16.4 and have the same problem as before with no info being sent to the pool site which leads me to believe I am missing a step can someone that uses linux please confrim I did this right
- downloaded the wallet and sync'ed the block chain
- installed node.js
- opened ports
- downloaded pool software from git
- changed the C to c in client chart
- ran npm install to get node modules
- start pool at root
Pool CLI is pulling data from the wallet and is on the right block as other pools
java ver.openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)Node ver. v5.12.0 but I also tried 4.4.7
npm ver.3.8.6
open ports in and out 80,8123,8124,8125,4443
any help or ideas would be greatly appreciated
-
@gersey only 4 4.7 works. If I get a chance I will follow your steps but on windows and see whats wrong.
It should be no issue to run this on windows then copy folder put it on linux dont change nothing (except C to c) and it should work. I do it all the time I download from ubuntu and run it on my windows java dont care.
-
@Lexicon said in Lex Pool (A rewritten pool based on uray source):
@rds use node v5. v6 breaks a lot of stuff.
ill get back to your other questions shortly. still going through hell.
Are you freed up yet to look at my questions?
-
@tross said in Lex Pool (A rewritten pool based on uray source):
@gersey only 4 4.7 works. If I get a chance I will follow your steps but on windows and see whats wrong.
It should be no issue to run this on windows then copy folder put it on linux dont change nothing (except C to c) and it should work. I do it all the time I download from ubuntu and run it on my windows java dont care.
if you get a chance to take a look that would be awesome! maybe someone who has set it up could write up a detailed how to or even a video curiosity has the best of me now I have to know what I am doing wrong
*edit I thought maybe it was my VPS services so I tried on my local Ubuntu Box with the same results clearly I am not as smart as I thought I was ;]
-
@gersey I have looked but need to confer something with lexicon I will post again!
