Sudden Error [ERR_SERVER_NOT_RUNNING]: Server is not running on angular builds

[fabianfrz]

Version

v22.21.1

Platform

* oraclelinux:9 container on kubernetes
* ubuntu 24.4 LTS

Subsystem

net

What steps will reproduce the bug?

I actually do not know. It is an angular 17 build

How often does it reproduce? Is there a required condition?

every time the build runs

What is the expected behavior? Why is that the expected behavior?

the socket probably should just close or it should not close an not open socket

What do you see instead?

Chrome Headless 143.0.0.0 (Linux 0.0.0): Executed 27 of 27 SUCCESS (0.088 secs / 0.07 secs)
TOTAL: 27 SUCCESS
✔ Browser application bundle generation complete.
✔ Browser application bundle generation complete.
node:net:2359
        cb(new ERR_SERVER_NOT_RUNNING());
           ^
Error [ERR_SERVER_NOT_RUNNING]: Server is not running.
    at Server.close (node:net:2359:12)
    at Object.onceWrapper (node:events:633:28)
    at Server.emit (node:events:531:35)
    at emitCloseNT (node:net:2419:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:89:21) {
  code: 'ERR_SERVER_NOT_RUNNING'
}

Additional information

The tests are run using karma and for some reason, this stack trace does not contain any library code, only node internal classes so I suspect that it is not related to any of the libraries and the build did work before (I cannot guarantee that there is no new library version but the stack trace does not show usage of any libs anyway).

the same happens on v24.0, which I also tried

[MikeMcC399]

@fabianfrz

You might want to check the version of Node.js that you are using. Angular 17 states that it is compatible with:

Node.js ^18.13.0 || ^20.9.0

see https://v17.angular.io/guide/versions and you write that you are using Node.js v22.21.1 and v24.0, which are not listed for compatibility.

[fabianfrz]

@MikeMcC399 the thing is if you look at the stack trace, you do not see any library / utility at all. It looks like something inside node might be cleaning up resources and then runs in the problem. If there would be an angular specific callback, I would expect something like node_modules/@angular/… in the stack trace.

[MikeMcC399]

@fabianfrz

I guess you would need to share a repro to investigate further on the Node.js side. I don't know if your error message implies that there is a bug in Node.js. It sounds more like Node.js is telling you that a server that is supposed to have been started by Angular is not running:

Error [ERR_SERVER_NOT_RUNNING]: Server is not running.

The other issue is that Angular 17 is no longer under regular support. According to Angular Support policy and schedule

Angular versions v2 to v18 are no longer supported.