Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
hopefully someone can help, or at least point me to the correct direction. The team that manage our servers updated the version of node.js to the current latest LTS version as of today (18.13) as what was installed was very out of date (in fact the versions supported on the pre-reqs for alerting are all out of support according to the team). Upon restart alerting is just giving an 'internal server error' red box on trying to log in (either via localhost or remotely). checking the gateway log (which i'm presuming is the web login) gives the below errors :
7 20230123T164104.402+0000 <server> 1.1.31 Global ERROR {"stack":"Error: read ECONNRESET\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)","message":"read ECONNRESET","errno":-4077,"code":"ECONNRESET","syscall":"read"}
8 20230123T164137.828+0000 <server> 1.1.31 Global ERROR {"stack":"Error: read ECONNRESET\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)","message":"read ECONNRESET","errno":-4077,"code":"ECONNRESET","syscall":"read"}
9 20230123T164249.917+0000 <server> 1.1.31 Global ERROR {"stack":"Error: read ECONNRESET\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)","message":"read ECONNRESET","errno":-4077,"code":"ECONNRESET","syscall":"read"}
10 20230123T164851.382+0000 <server> 1.1.31 Global ERROR {"stack":"Error: connect ECONNREFUSED ::1:4560\n at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1487:16)","message":"connect ECONNREFUSED ::1:4560","errno":-4078,"code":"ECONNREFUSED","syscall":"connect","address":"::1","port":4560}
11 20230123T164922.971+0000 <server> 1.1.31 Global ERROR {"stack":"Error: read ECONNRESET\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)","message":"read ECONNRESET","errno":-4077,"code":"ECONNRESET","syscall":"read"}
and the windows event viewer are full of warnings about workers not starting and trying to restart.
any help massively appreciated, server team are going to try reverting to previous version and hoping that will work in the meantime but not ideal to be running out of date software.
even tried updating to SR1 in case that would fix it but no dice.
thanks
It seems the server team were a bit over enthusiastic and 16.18.1 is actually supported for another few months, they have reverted back to that version and all is well again.
It seems the server team were a bit over enthusiastic and 16.18.1 is actually supported for another few months, they have reverted back to that version and all is well again.