UNOMP / unified-node-open-mining-portal

Development stopped and is now unsupported. The node.js version is being deprecated in October 2016.
GNU General Public License v2.0
347 stars 395 forks source link

undefined symbol: GetNfactorJane #274

Open nabouthy opened 6 years ago

nabouthy commented 6 years ago

[2018-03-07 21:00:43.023] [INFO] [default] - New Relic [2018-03-07 21:00:43.025] [DEBUG] [default] - NewRelic Monitor New Relic initiated [2018-03-07 21:00:43.029] [INFO] [default] - POSIX Not Installed [2018-03-07 21:00:43.029] [DEBUG] [default] - POSIX Connection Limit (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised [2018-03-07 21:00:43.029] [INFO] [default] - Run Workers [2018-03-07 21:00:43.794] [INFO] [default] - New Relic [2018-03-07 21:00:43.797] [INFO] [default] - POSIX Not Installed [2018-03-07 21:00:43.798] [INFO] [default] - Run Workers [2018-03-07 21:00:43.807] [INFO] [default] - Switching Setup Thread 1 Loading last proxy state from redis [2018-03-07 21:00:43.817] [DEBUG] [default] - Pool ultracoin Thread 1 Share processing setup with redis (127.0.0.1:6379) [2018-03-07 21:00:43.832] [DEBUG] [default] - Pool ultracoin Thread 1 started for ultracoin [UTC] {scrypt-jane} Network Connected: Mainnet Detected Reward Type: POW Current Block Height: 2369114 Current Connect Peers: 15 Current Block Diff: 1085.795139584 Network Difficulty: 1140.08457216 Network Hash Rate: 704.53 KH Stratum Port(s): 3008, 3032, 3256 Pool Fee Percent: 1.5% Block polling every: 1000 ms [2018-03-07 21:00:43.832] [DEBUG] [default] - Switching Setup scrypt-jane Setting proxy difficulties after pool start [2018-03-07 21:00:43.994] [INFO] [default] - New Relic [2018-03-07 21:00:43.997] [INFO] [default] - POSIX Not Installed [2018-03-07 21:00:43.997] [INFO] [default] - Run Workers [2018-03-07 21:00:44.005] [INFO] [default] - Switching Setup Thread 2 Loading last proxy state from redis [2018-03-07 21:00:44.014] [DEBUG] [default] - Pool ultracoin Thread 2 Share processing setup with redis (127.0.0.1:6379) [2018-03-07 21:00:44.027] [DEBUG] [default] - Pool ultracoin Thread 2 started for ultracoin [UTC] {scrypt-jane} [2018-03-07 21:00:44.027] [DEBUG] [default] - Switching Setup scrypt-jane Setting proxy difficulties after pool start [2018-03-07 21:00:44.046] [DEBUG] [default] - Master PoolSpawner Spawned 1 pool(s) on 4 thread(s) [2018-03-07 21:00:44.249] [INFO] [default] - New Relic [2018-03-07 21:00:44.252] [INFO] [default] - POSIX Not Installed [2018-03-07 21:00:44.252] [INFO] [default] - Run Workers [2018-03-07 21:00:44.260] [INFO] [default] - Switching Setup Thread 3 Loading last proxy state from redis [2018-03-07 21:00:44.269] [DEBUG] [default] - Pool ultracoin Thread 3 Share processing setup with redis (127.0.0.1:6379) [2018-03-07 21:00:44.281] [DEBUG] [default] - Pool ultracoin Thread 3 started for ultracoin [UTC] {scrypt-jane} [2018-03-07 21:00:44.281] [DEBUG] [default] - Switching Setup scrypt-jane Setting proxy difficulties after pool start [2018-03-07 21:00:44.495] [INFO] [default] - New Relic [2018-03-07 21:00:44.498] [INFO] [default] - POSIX Not Installed [2018-03-07 21:00:44.498] [INFO] [default] - Run Workers [2018-03-07 21:00:44.506] [INFO] [default] - Switching Setup Thread 4 Loading last proxy state from redis [2018-03-07 21:00:44.516] [DEBUG] [default] - Pool ultracoin Thread 4 Share processing setup with redis (127.0.0.1:6379) [2018-03-07 21:00:44.530] [DEBUG] [default] - Pool ultracoin Thread 4 started for ultracoin [UTC] {scrypt-jane} [2018-03-07 21:00:44.530] [DEBUG] [default] - Switching Setup scrypt-jane Setting proxy difficulties after pool start [2018-03-07 21:00:53.038] [DEBUG] [default] - Master CLI CLI listening on port 17117 [2018-03-07 21:00:53.529] [INFO] [default] - New Relic [2018-03-07 21:00:53.532] [INFO] [default] - POSIX Not Installed [2018-03-07 21:00:53.533] [INFO] [default] - Run Workers [2018-03-07 21:00:53.613] [DEBUG] [default] - Website Server Website started on 144.202.34.14:80 [2018-03-07 21:00:55.021] [DEBUG] [default] - Pool ultracoin Thread 1 getting block notification via RPC polling [2018-03-07 21:00:55.022] [DEBUG] [default] - Pool ultracoin Thread 2 getting block notification via RPC polling [2018-03-07 21:00:55.023] [DEBUG] [default] - Pool ultracoin Thread 4 getting block notification via RPC polling [2018-03-07 21:00:55.023] [DEBUG] [default] - Pool ultracoin Thread 3 getting block notification via RPC polling [2018-03-07 21:01:10.719] [DEBUG] [default] - Pool ultracoin Thread 3 getting block notification via RPC polling [2018-03-07 21:01:10.719] [DEBUG] [default] - Pool ultracoin Thread 1 getting block notification via RPC polling [2018-03-07 21:01:10.719] [DEBUG] [default] - Pool ultracoin Thread 4 getting block notification via RPC polling [2018-03-07 21:01:10.720] [DEBUG] [default] - Pool ultracoin Thread 2 getting block notification via RPC polling [2018-03-07 21:01:44.516] [DEBUG] [default] - Pool ultracoin Thread 3 Authorized UUxj4Modewa6eWjryu74G8z5JYXGGocnn9:x [201.185.223.251]

/usr/bin/nodejs: symbol lookup error: /root/unomp/node_modules/merged-pooler/node_modules/unomp-multi-hashing/build/Release/multihashing.node: undefined symbol: GetNfactorJane [2018-03-07 21:01:45.265] [ERROR] [default] - Master PoolSpawner Fork 2 died, spawning replacement worker... [2018-03-07 21:01:45.593] [DEBUG] [default] - Pool ultracoin Thread 4 Authorized UUxj4Modewa6eWjryu74G8z5JYXGGocnn9:x [201.185.223.251]

/usr/bin/nodejs: symbol lookup error: /root/unomp/node_modules/merged-pooler/node_modules/unomp-multi-hashing/build/Release/multihashing.node: undefined symbol: GetNfactorJane [2018-03-07 21:01:46.281] [ERROR] [default] - Master PoolSpawner Fork 3 died, spawning replacement worker...

nabouthy commented 6 years ago

i have this error, a want configure coin ultracoin.

  1. /usr/bin/nodejs: symbol lookup error: /root/unomp/node_modules/merged-pooler/node_modules/unomp-multi-hashing/build/Release/multihashing.node: undefined symbol: GetNfactorJane

  2. [2018-03-07 20:58:10.613] [ERROR] [default] - Master PoolSpawner Fork 3 died, spawning replacement worker...

devnull-ed commented 6 years ago

https://github.com/foxer666/node-multi-hashing/issues/5

jdamhost commented 6 years ago

i resolved this multi-hashing issue and more by using nvm use 0.10.25