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

Telemetry leaks sockets on error #2703

Closed
QxBytes opened this issue Apr 24, 2024 · 4 comments
Closed

Telemetry leaks sockets on error #2703

QxBytes opened this issue Apr 24, 2024 · 4 comments
Assignees

Comments

@QxBytes
Copy link
Contributor

QxBytes commented Apr 24, 2024

What happened:
Starting telemetry gives error

2024/04/20 00:17:26 [9756] StartServer: unmarshal error:invalid character 'm' looking for beginning of value
2024/04/24 16:39:41 [9756] StartServer: unmarshal error:invalid character ':' after top-level value
2024/04/24 16:39:42 [9756] StartServer: unmarshal error:invalid character ':' looking for beginning of value

and does not clean up/close connections on error.

What you expected to happen:
The unmarshal error should not occur and the connections should be closed properly on error.

How to reproduce it:
Start an AKS cluster and create a pod.

Orchestrator and Version (e.g. Kubernetes, Docker):

Operating System (Linux/Windows):

Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):

Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]

Copy link

github-actions bot commented May 9, 2024

This issue is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale due to inactivity. label May 9, 2024
Copy link

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
@rbtr rbtr reopened this May 17, 2024
@rbtr rbtr removed the stale Stale due to inactivity. label May 17, 2024
Copy link

github-actions bot commented Jun 1, 2024

This issue is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale due to inactivity. label Jun 1, 2024
@QxBytes QxBytes removed the stale Stale due to inactivity. label Jun 1, 2024
@QxBytes
Copy link
Contributor Author

QxBytes commented Jun 8, 2024

Fix has rolled out to aks (cni versions 1.4.54 and 1.5.28)

@QxBytes QxBytes closed this as completed Jun 8, 2024
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

No branches or pull requests

2 participants