Bitcoin Forum
April 25, 2024, 04:13:27 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Installing NOMP.  (Read 322 times)
educob (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 4


View Profile
October 23, 2018, 06:16:27 PM
Last edit: October 23, 2018, 09:34:42 PM by educob
 #1

Hello,

I have a private bitcoin network (2 nodes connected among themselves)

I am installing NOMP according to this guide: https://github.com/zone117x/node-open-mining-portal

When running "node init.js" I get these errors:

Code:
2018-10-23 20:02:54 [POSIX]	[Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2018-10-23 20:02:54 [Master] [CLI] CLI listening on port 17117
2018-10-23 20:02:55 [Master] [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
2018-10-23 20:02:55 [Payments] [bitcoin] Payment processing setup to run every 20 second(s) with daemon (xxx@127.0.0.1:8332) and redis (127.0.0.1:6379)
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: bind EACCES 0.0.0.0:80
    at listenOnMasterHandle (net.js:1420:16)
    at rr (internal/cluster/child.js:121:12)
    at Worker.send (internal/cluster/child.js:88:7)
    at process.onInternalMessage (internal/cluster/utils.js:42:8)
    at emitTwo (events.js:131:20)
    at process.emit (events.js:214:7)
    at emit (internal/child_process.js:762:12)
    at _combinedTickCallback (internal/process/next_tick.js:142:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
2018-10-23 20:02:55 [Master] [Website] Website process died, spawning replacement...
2018-10-23 20:02:55 [Payments] [bitcoin] Finished interval - time spent: 4ms total, 2ms redis, 2ms daemon RPC
2018-10-23 20:02:55 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) No rewardRecipients have been setup which means no fees will be taken
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Daemon is still syncing with network (download blockchain) - server will be started once synced
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
events.js:183

Any idea what is wrong?

Thanks.
1714061607
Hero Member
*
Offline Offline

Posts: 1714061607

View Profile Personal Message (Offline)

Ignore
1714061607
Reply with quote  #2

1714061607
Report to moderator
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714061607
Hero Member
*
Offline Offline

Posts: 1714061607

View Profile Personal Message (Offline)

Ignore
1714061607
Reply with quote  #2

1714061607
Report to moderator
d57heinz
Legendary
*
Offline Offline

Activity: 1453
Merit: 1011


Bitcoin Talks Bullshit Walks


View Profile
October 23, 2018, 06:22:14 PM
 #2

Hello,

I am installing NOMP according to this guide: https://github.com/zone117x/node-open-mining-portal

When running "node init.js" I get these errors:

Code:
2018-10-23 20:02:54 [POSIX]	[Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2018-10-23 20:02:54 [Master] [CLI] CLI listening on port 17117
2018-10-23 20:02:55 [Master] [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
2018-10-23 20:02:55 [Payments] [bitcoin] Payment processing setup to run every 20 second(s) with daemon (xxx@127.0.0.1:8332) and redis (127.0.0.1:6379)
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: bind EACCES 0.0.0.0:80
    at listenOnMasterHandle (net.js:1420:16)
    at rr (internal/cluster/child.js:121:12)
    at Worker.send (internal/cluster/child.js:88:7)
    at process.onInternalMessage (internal/cluster/utils.js:42:8)
    at emitTwo (events.js:131:20)
    at process.emit (events.js:214:7)
    at emit (internal/child_process.js:762:12)
    at _combinedTickCallback (internal/process/next_tick.js:142:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
2018-10-23 20:02:55 [Master] [Website] Website process died, spawning replacement...
2018-10-23 20:02:55 [Payments] [bitcoin] Finished interval - time spent: 4ms total, 2ms redis, 2ms daemon RPC
2018-10-23 20:02:55 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) No rewardRecipients have been setup which means no fees will be taken
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Daemon is still syncing with network (download blockchain) - server will be started once synced
2018-10-23 20:02:55 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
events.js:183

Any idea what is wrong?

Thanks.


Would you post your config. Omit credentials pw/usr as necessary. Thanks

Edit. Try setting your website to port 81 in the config.  Also. It’s been quite a while. I’m not certain if the blockchain needed to be synced for it to load correctly. I’m not where I can look at the code

As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
educob (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 4


View Profile
October 23, 2018, 07:24:26 PM
 #3

Thanks.

this is config.json

Code:
{
    "logLevel": "debug",
    "logColors": true,

    "cliPort": 17117,

    "clustering": {
        "enabled": true,
        "forks": "auto"
    },

    "defaultPoolConfigs": {
        "blockRefreshInterval": 1000,
        "jobRebroadcastTimeout": 55,
        "connectionTimeout": 600,
        "emitInvalidBlockHashes": false,
        "validateWorkerUsername": true,
        "tcpProxyProtocol": false,
        "banning": {
            "enabled": true,
            "time": 600,
            "invalidPercent": 50,
            "checkThreshold": 500,
            "purgeInterval": 300
        },
        "redis": {
            "host": "127.0.0.1",
            "port": 6379
        }
    },

    "website": {
        "enabled": true,
        "host": "0.0.0.0",
        "port": 80,
        "stratumHost": "cryppit.com",
        "stats": {
            "updateInterval": 60,
            "historicalRetention": 43200,
            "hashrateWindow": 300
        },
        "adminCenter": {
            "enabled": true,
            "password": "password"
        }
    },

    "redis": {
        "host": "127.0.0.1",
        "port": 6379
    },

    "switching": {
        "switch1": {
            "enabled": false,
            "algorithm": "sha256",
            "ports": {
                "3333": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "switch2": {
            "enabled": false,
            "algorithm": "scrypt",
            "ports": {
                "4444": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "switch3": {
            "enabled": false,
            "algorithm": "x11",
            "ports": {
                "5555": {
                    "diff": 0.001,
                    "varDiff": {
                        "minDiff": 0.001,
                        "maxDiff": 1,
                        "targetTime": 15,
                        "retargetTime": 60,
                        "variancePercent": 30
                    }
                }
            }
        }
    },

    "profitSwitch": {
        "enabled": false,
        "updateInterval": 600,
        "depth": 0.90,
        "usePoloniex": true,
        "useCryptsy": true,
        "useMintpal": true,
        "useBittrex": true
    }
}

This is pool_settings/bitcoin.json

Code:
{
    "enabled": true,
    "coin": "bitcoin.json",

    "address": "3KFHKvFjjfcNYsWRJz8Bt8TtWSrLsC7Neh",

    "paymentProcessing": {
        "enabled": true,
        "paymentInterval": 20,
        "minimumPayment": 5,
        "daemon": {
            "host": "127.0.0.1",
            "port": 8332,
            "user": "xxx",
            "password": "yyy"
        }
    },

    "ports": {
        "3008": {
            "diff": 8
        },
        "3032": {
            "diff": 32,
            "varDiff": {
                "minDiff": 8,
                "maxDiff": 4096,
                "targetTime": 15,
                "retargetTime": 90,
                "variancePercent": 30
            }
        },
        "3256": {
            "diff": 256
        }
    },

    "daemons": [
        {
            "host": "127.0.0.1",
            "port": 8332,
            "user": "xxx",
            "password": "yyy"
        }
    ],

    "p2p": {
        "enabled": true,
        "host": "127.0.0.1",
        "port": 8333,
        "disableTransactions": true
    },

    "mposMode": {
        "enabled": false,
        "host": "127.0.0.1",
        "port": 3306,
        "user": "me",
        "password": "mypass",
        "database": "ltc",
        "checkPassword": true,
        "autoCreateWorker": false
    }

}

Thanks.
educob (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 4


View Profile
October 23, 2018, 07:31:13 PM
 #4

Update.

I found this thread: https://stackoverflow.com/questions/9164915/node-js-eacces-error-when-listening-on-most-ports

The solution is to allow, somehow, port 80 for non-root users:

Code:
sudo apt-get install libcap2-bin
sudo setcap cap_net_bind_service=+ep `readlink -f \`which node\``

But now I get this:

Code:
2018-10-23 21:29:43 [Pool]	[bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:29:48 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:29:53 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:29:58 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:30:03 [Payments] [bitcoin] Finished interval - time spent: 3ms total, 1ms redis, 2ms daemon RPC
2018-10-23 21:30:03 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers
2018-10-23 21:30:08 [Pool] [bitcoin] (Thread 1) Downloaded NaN% of blockchain from 2 peers

I have two bitcoins nodes connected among themselves (a private mainnet) and I want to start mining.

How do I know the pool is mining?

Thanks.
d57heinz
Legendary
*
Offline Offline

Activity: 1453
Merit: 1011


Bitcoin Talks Bullshit Walks


View Profile
October 23, 2018, 09:23:46 PM
 #5

Best thing to do would be to get it setup on a testnet so that you can see if you find blocks.  Wait till your daemon is synced.  Problem with bitcoin is your going to need so much hash power it’s not worth it to hope you have it right.  If your looking to mine solo btc checkout ck solo pool.   If your looking to learn then I’d suggest keeping it internal within your network. Thieves will clean your pool so quick it’ll make your head swim.

BR

As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
educob (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 4


View Profile
October 23, 2018, 09:33:54 PM
 #6

Hi.

Thanks for answering.
The bitcoin network is private. Mining souldn't be a problem at all.

The thing is that I installed a mining server but I haven't seen an explanation of how to use it.
It seems that most documentation assumes some kind of magic learning by readers.

How do i mine?
educob (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 4


View Profile
October 23, 2018, 10:36:22 PM
 #7

I am running cpuminer (please see above the configuration files):

Code:
./minerd --url=stratum+tcp://127.0.0.1:17117  --userpass=3KFHKvFjjfcNYsWRJz8Bt8TtWSrLsC7Neh:yyy  -a sha256d -D -P

And I get this error:

Code:
[2018-10-24 00:34:35] > {"id": 1, "method": "mining.subscribe", "params": ["cpuminer/2.5.0"]}
* Failed to get recent socket
[2018-10-24 00:34:35] stratum_recv_line failed
[2018-10-24 00:34:35] ...retry after 30 seconds

No idea if the port is 17117, or 3333 or 3008.

Sometimes I get this error in the terminal running "node init.js":

Code:
/home/vader/.bitcoin/nomp/libs/poolWorker.js:278
                            pools[currentPool].getStratumServer().handleNewClient(socket);
                                                                 ^

TypeError: Cannot read property 'handleNewClient' of undefined

Please help me.

d57heinz
Legendary
*
Offline Offline

Activity: 1453
Merit: 1011


Bitcoin Talks Bullshit Walks


View Profile
October 23, 2018, 11:45:24 PM
Last edit: October 24, 2018, 12:32:02 PM by d57heinz
 #8

Your mining port would be the 3008 port. If you are mining the same machine you are running NOMP use 127.0.01:3008 for mining address. Otherwise if it’s same network use whatever you config your network with. 10.10.10.5:3008 or 192.168.1.5:3008 for example. See if that gets you connected and talking to stratum. FYI Cpu mining bitcoin isn’t going to work for you at this point. Difficulty to mine a block is 7 trillion. Not impossible but improbable. Your going to be submitting shares to the pool that exceed a difficulty of 8.  Chances to mine a block bitcoin with cpu is prolly about 1 in 10000 years. Maybe worse. Odds aren’t in your favor.

BR

As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!