Community
All Features
Overview of all exisiting features.
Arcade
Play various games in the arcade.
Awards
Earn awards for different tasks.
Bug Tracker
Report site related bugs the right way.
Credits
Everything related to credits.
Groups
A list of user run groups you can join.
Help Center
Official regulations and help documents.
Member List
A list of all registered members.
Latest Announcements
Staff Recruitment | September 2022
Changelog #34 - 03/04/2022
April Update - Index Redesign and Unlock Content Experiment
Support
Shop
Upgrade
Log In
Create Account
NulledBB
Marketplace
Money Talk
NOMP HUGE BUG SINCE 2014.....
Create an account
Login
PrivateAlps.net - Offshore Cloud Services | VPS/RDP/VPN - Dedicated Servers - Webhosting - TOR Services - Auto Deploy
ADULTSLAYER.STORE 💎 #1 PORN SHOP | 700+ Hot Products: Brazzers, Teamskeet, Pornhub, NaughtyAmerica, Many More! | 💸 Secure PayPal & Card Payments | Satisfaction Guaranteed! 🔥
Money Talk
NOMP HUGE BUG SINCE 2014.....
Submitted by isimsiz1,
09-03-2019, 11:50 PM
, Thread ID: 123938
Thread Closed
Reply
09-03-2019, 11:50 PM
#1
In
node_modules/stratum-pool/lib/pool.js
:
.on('broadcastTimeout', function(){
emitLog('No new blocks for ' + options.jobRebroadcastTimeout + ' seconds - updating transactions & rebroadcasting work');
GetBlockTemplate(function(error, rpcData, processedBlock){
if (error || processedBlock) return;
_this.jobManager.updateCurrentJob(rpcData);
});
the call to GetBlockTemplate function DOES NOT update workers with a new getblocktemplate RPC call...........
And the worst part is it actually print to console that is does..........
But getblocktemplate is actually sent to the coin's wallet ( RPC call ) ONLY if there is a new block or when starting the pool..........
( option " jobRebrodcastTimeout " in nomp/config.json ) :
"defaultPoolConfigs": {
"blockRefreshInterval": 378,
"jobRebroadcastTimeout": 55,
"connectionTimeout": 600,
"emitInvalidBlockHashes": false,
"validateWorkerUsername": true,
"tcpProxyProtocol": false,
"banning": {
"enabled": true,
"time": 7200,
"invalidPercent": 30,
"checkThreshold": 15,
"purgeInterval": 300
},
"redis": {
"host": "127.0.0.1",
"port": 6379
}
},
I am currently trying to correct this flaw so that " jobRebroadcastTimeout " option in NOMP actualy DOES SOMETHING apart from printing that it does something.....
I really think this is a bug and is not intended.
I welcome help and comments !!!
More
RE: NOMP HUGE BUG SINCE 2014.....
03-04-2019, 03:17 PM
#2
thank you very much, I really needed this template
More
Users browsing this thread: 4 Guest(s)