dvandal / cryptonote-nodejs-pool

Mining pool for all CryptoNote based coins using Cryptonight, Cryptonight Light and Cryptonight Heavy algorithms
GNU General Public License v2.0
364 stars 610 forks source link

Problem with Monero #664

Open DirtyHarryDev opened 3 years ago

DirtyHarryDev commented 3 years ago

Hello !

I setup the pool on a Ubuntu 18.04 Server. Started the Monero wallet and used for pool the standard example monero.json. When i start the pool i get this error

2021-03-13 16:30:03 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:04 [master] Pool spawned on 6 thread(s) 2021-03-13 16:30:04 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:04 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:04 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:04 [chartsDataCollector] Started 2021-03-13 16:30:05 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:05 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:05 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:05 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:05 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:05 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:06 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:06 [master] Starting Cryptonote Node.JS pool version v2.0.0 2021-03-13 16:30:06 [daemon] bad reponse from daemon 2021-03-13 16:30:07 [payments] Started (node:1407) ExperimentalWarning: queueMicrotask() is experimental. 2021-03-13 16:30:07 [payments] No workers' balances reached the minimum payment threshold 2021-03-13 16:30:07 [pool] (Thread 2) Clear values for connected workers in redis database. 2021-03-13 16:30:07 [pool] (Thread 2) Could not start server listening on port 9999 (SSL): SSL certificate file not found (configuration error) (node:1436) ExperimentalWarning: queueMicrotask() is experimental. 2021-03-13 16:30:07 [pool] (Thread 2) Clear values for port 3333 in redis database. 2021-03-13 16:30:07 [pool] (Thread 2) Started server listening on port 3333 2021-03-13 16:30:07 [pool] (Thread 2) Clear values for port 4444 in redis database. 2021-03-13 16:30:07 [pool] (Thread 2) Started server listening on port 4444 2021-03-13 16:30:07 [pool] (Thread 2) Clear values for port 5555 in redis database. 2021-03-13 16:30:07 [pool] (Thread 2) Started server listening on port 5555 2021-03-13 16:30:07 [pool] (Thread 2) Clear values for port 7777 in redis database. 2021-03-13 16:30:07 [pool] (Thread 2) Started server listening on port 7777 2021-03-13 16:30:07 [pool] (Thread 2) Clear values for port 8888 in redis database. 2021-03-13 16:30:07 [pool] (Thread 2) Started server listening on port 8888

Any body know what this error 2021-03-13 16:30:06 [daemon] bad reponse from daemon means ? It comes again and again.

stinkystizzy commented 3 years ago

i got this error while the monerod daemon was still syncing the blockchain.