Pool crashes periodically..



  • I'm in the process of testing a Burst pool using Urays code.. but every 30 minutes or so, it crashes with the following error:

    
    new best deadline 1486559
    Error: write after end
        at ServerResponse.OutgoingMessage.write (_http_outgoing.js:413:15)
        at ServerResponse.res.write (/root/burstpool/node_modules/compression/index.js:95:17)
        at ServerResponse.res.end (/root/burstpool/node_modules/compression/index.js:112:14)
        at ServerResponse.send (/root/burstpool/node_modules/express/lib/response.js:191:8)
        at /root/burstpool/burst-pool-protocol.js:216:13
        at Layer.handle [as handle_request] (/root/burstpool/node_modules/express/lib/router/layer.js:82:5)
        at trim_prefix (/root/burstpool/node_modules/express/lib/router/index.js:271:13)
        at /root/burstpool/node_modules/express/lib/router/index.js:238:9
        at Function.proto.process_params (/root/burstpool/node_modules/express/lib/router/index.js:313:12)
        at /root/burstpool/node_modules/express/lib/router/index.js:229:12
    clean
    
    

    I'm no Javascript expert, so if someone could explain what is going wrong it would be greatly appreciated!

    Thanks



  • @technoeuan , that code is old. You need a newer version.



  • @rds I tried @Lexicon 's version, but the pool wouldn't get the latest block.. or update the amount of miners etc (see https://burst.cryptosphere.world ) .. am i doing something wrong with that?
    Using Node version 5.12.0 by the way..



  • @technoeuan , I just downloaded CRK's version of the Lex code. He cleaned it all up. Looks good, runs good. I am mining on his pool that uses the code. I also have the new code constantly running on my server, if I decide to go solo, I point my miners to the server and it is good to go.

    https://github.com/burstpay/burst-pool



  • @technoeuan said in Pool crashes periodically..:

    @rds I tried @Lexicon 's version, but the pool wouldn't get the latest block.. or update the amount of miners etc (see https://burst.cryptosphere.world ) .. am i doing something wrong with that?
    Using Node version 5.12.0 by the way..

    Is that your pool? It would not connect, is it port 80 or did you setup a custom port? Regardless, try the new code.

    Also, Lex code thread said node 4.4.7 was the stable version for his code. That's what I have on my machines. It supports CRK's code and CRK said his code will work on V6 so your 5.12.0 should work, it's in the middle :)

    Just so you think you're not losing it, additionally, the web socket would not work until you replaced the socket.io file with a different one. Why it's still in the package I don't know. But that was a lot of growing pains for me. You can see about half way down the Lex code thread, I was pulling my hair out trying to understand why the code would not work. I had a lot of question and got periodic half answers. Pretty sure Lex is gone now, so that version will die a slow death.

    Someone else forked that code but I don't know who is behind it. Here is their pool.

    http://pool.burstcoin.asia/



  • @rds Sorry.. i was uploading CRK's code.. hence the down pool! I tried running it, although it just returns a blank terminal line and nothing else.. is this part of the socket.io thing.. as i haven't touched that yet.

    Thanks for your help so far



  • @technoeuan , no I didn't change the socket.io on the crk version. Did you do a "npm install" in your pool directory? Sorry, if that is a dumb question, but I didn't know about it for quite awhile as I was trying to start up the pool.

    This is my pool running now, no miners just idling:

    0_1504564150377_912b14d1-b49b-4118-8884-45ae45725ed9-image.png