Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service crash on ws failure #46

Open
avoylenko opened this issue Feb 12, 2025 · 2 comments · May be fixed by #47
Open

Service crash on ws failure #46

avoylenko opened this issue Feb 12, 2025 · 2 comments · May be fixed by #47

Comments

@avoylenko
Copy link
Contributor

If the RTPENGINE_URL env points to the wrong endpoint or there is an issue with WS establishment, the service crashed with the below error:

7|sbc-rtpengine-sidecar  | Error: connect ECONNREFUSED 127.0.0.1:8082
7|sbc-rtpengine-sidecar  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
7|sbc-rtpengine-sidecar  |   errno: -111,
7|sbc-rtpengine-sidecar  |   code: 'ECONNREFUSED',
7|sbc-rtpengine-sidecar  |   syscall: 'connect',
7|sbc-rtpengine-sidecar  |   address: '127.0.0.1',
7|sbc-rtpengine-sidecar  |   port: 8082
7|sbc-rtpengine-sidecar  | }
@avoylenko avoylenko linked a pull request Feb 12, 2025 that will close this issue
@davehorton
Copy link
Contributor

probably good that it crashes though if misconfgured, silently continuing with configuration error doesnt seem like a good idea to me

@avoylenko
Copy link
Contributor Author

The ws connection is needed just to dump the rtpenigne stats. Is this so important for the service?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants