MeshCentral 0.2.9-x Crashing on Start



  • Just updated to 0.2.9-x and now we get a continuous restart loop.

    { Error: Command failed: /root/.nvm/versions/node/v11.4.0/bin/node /opt/meshcentral/node_modules/meshcentral --launch
    /opt/meshcentral/node_modules/meshcentral/meshagent.js:362
                                obj2.send(common.ShortToStr(2) + common.ShortToStr(obj2.parent.agentCertificateAsn1.length) + obj2.parent.agentCertificateAsn1 + signature); // Command 2, certificate + signature
                                                                                               ^
    
    TypeError: Cannot read property 'agentCertificateAsn1' of undefined
        at /opt/meshcentral/node_modules/meshcentral/meshagent.js:362:92
        at Object.obj.acceleratorPerformSignature (/opt/meshcentral/node_modules/meshcentral/certoperations.js:528:13)
        at WebSocket.<anonymous> (/opt/meshcentral/node_modules/meshcentral/meshagent.js:360:61)
        at WebSocket.emit (events.js:189:13)
        at Receiver.receiverOnMessage (/opt/meshcentral/node_modules/express-ws/node_modules/ws/lib/websocket.js:720:20)
        at Receiver.emit (events.js:189:13)
        at Receiver.dataMessage (/opt/meshcentral/node_modules/express-ws/node_modules/ws/lib/receiver.js:405:14)
        at Receiver.getData (/opt/meshcentral/node_modules/express-ws/node_modules/ws/lib/receiver.js:346:17)
        at Receiver.startLoop (/opt/meshcentral/node_modules/express-ws/node_modules/ws/lib/receiver.js:133:22)
        at Receiver._write (/opt/meshcentral/node_modules/express-ws/node_modules/ws/lib/receiver.js:69:10)
        at doWrite (_stream_writable.js:415:12)
        at writeOrBuffer (_stream_writable.js:399:5)
        at Receiver.Writable.write (_stream_writable.js:299:11)
        at TLSSocket.socketOnData (/opt/meshcentral/node_modules/express-ws/node_modules/ws/lib/websocket.js:795:35)
        at TLSSocket.emit (events.js:189:13)
        at addChunk (_stream_readable.js:288:12)
    
        at ChildProcess.exithandler (child_process.js:294:12)
        at ChildProcess.emit (events.js:194:15)
        at maybeClose (internal/child_process.js:978:16)
        at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
      killed: false,
      code: 1,
      signal: null,
      cmd:
       '/root/.nvm/versions/node/v11.4.0/bin/node /opt/meshcentral/node_modules/meshcentral --launch' }
    ERROR: MeshCentral failed with critical error, check MeshErrors.txt. Restarting in 5 seconds...
    MeshCentral HTTP redirection server running on port 80.
    MeshCentral v0.2.9-x, WAN mode.
    MeshCentral Intel(R) AMT server running on mc.ntg.co:4433.
    MeshCentral HTTPS server running on mc.ntg.co:443.
    SMTP mail server mail.ntg.co working as expected.
    

    @Ylian



  • Might be related to this one...

    https://github.com/Ylianst/MeshCentral/issues/119



  • No such problem here



  • Published v0.2.9-y with a fix for this.



  • @FATeknollogee said in MeshCentral 0.2.9-x Crashing on Start:

    No such problem here

    Spoke too soon



  • I can't connect to any of my devices.



  • @Ylian said in MeshCentral 0.2.9-x Crashing on Start:

    Published v0.2.9-y with a fix for this.

    Thanks, now to update when the crashing going on 🙂



  • There is another problem, going to patch ASAP. The remote desktop/terminal/files does not work.



  • @Ylian said in MeshCentral 0.2.9-x Crashing on Start:

    There is another problem, going to patch ASAP. The remote desktop/terminal/files does not work.

    Thank you!



  • v0.2.9-z is out. That should solve the fires. Desktop/Terminal/Files working again.



  • 👍 👍
    Fixed up!!



  • Everything back to normal now. Sorry about that. Server heap memory optimizations gone wrong. There does seems to be a slow memory leak on the server and I am tracking that down.



  • 0.2.9-z is working for us here. Thanks!