aion_solo_pool throws error when starting kernel + miner after starting the solo_pool

[JimVanEeden]

Not really a big issue, but you might want to fix this. When I start the solo_pool first, then start the kernel, then start the miner, I get the following error:

~/aion/aion_miner/aion_solo_pool$ ./run.sh 
function verify() { [native code] }
2018-02-21 10:03:26 [POSIX]	[Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2018-02-21 10:03:26 [Master]	[CLI] CLI listening on port 17117
2018-02-21 10:03:26 [Master]	[PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
function verify() { [native code] }
2018-02-21 10:03:26 [Switching]	[Setup] (Thread 1) Loading last proxy state from redis
2018-02-21 10:03:26 [Pool]	[aion] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2018-02-21 10:03:26 [Pool]	[aion] (Thread 1) Could not start pool, error with init batch RPC call: {"type":"offline","message":"connect ECONNREFUSED 127.0.0.1:8545"}
2018-02-21 10:03:26 [Switching]	[Setup] (Thread 1) Switching "switch0" listening for equihash on port 3333 into aion
2018-02-21 10:03:35 [Switching]	[Connect] (Thread 1) Connection to switch0 from ::ffff:127.0.0.1 on 3333 routing to aion
/home/jim/aion/aion_miner/aion_solo_pool/libs/poolWorker.js:279
                            pools[currentPool].getStratumServer().handleNewClient(socket);
                                                                 ^

TypeError: Cannot read property 'handleNewClient' of undefined
    at Server.<anonymous> (/home/jim/aion/aion_miner/aion_solo_pool/libs/poolWorker.js:279:66)
    at emitOne (events.js:116:13)
    at Server.emit (events.js:211:7)
    at Object.onconnection (net.js:1561:8)
    at onconnection (internal/cluster/child.js:168:12)
    at Worker.onmessage (internal/cluster/child.js:43: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:772:12)
2018-02-21 10:03:35 [Master]	[PoolSpawner] Fork 0 died, spawning replacement worker...
function verify() { [native code] }
2018-02-21 10:03:37 [Switching]	[Setup] (Thread 1) Loading last proxy state from redis

Everything starts correctly after that, but you might want to catch the error in the code instead.