Open
Description
Expected vs actual behavior
To be able to use kubectl and UI without errors
with version paralusio/relay:v0.1.8
we often get this error after a day's use with just 2 users.
{"level":"error","ts":"2024-09-24T22:03:40.892Z","caller":"utils/utils.go:422","msg":"Relay Server.Server.Listener::io.Copy error direction: tunnel to unix error: write unix /tmp/relay-unix-*.core-connector.kauth.stage.c8y.io->@: write: broken pipe ","stacktrace":"github.com/paralus/relay/pkg/utils.Transfer\n\t/build/pkg/utils/utils.go:422\ngithub.com/paralus/relay/pkg/tunnel.(*Server).proxyUnixConnection\n\t/build/pkg/tunnel/server.go:1141"}in UI we get
Chart & environment details
open sockets
❯ kubectl -n paralus exec relay-server-588bf9bcb6-n9ct6 -c relay-server -it -- lsof | grep socket | wc -l
2569
this sounds very similar behaviour to what is mentioned here - paralus/paralus#266
images.reley.tag="v0.1.6"
Steps to reproduce the bug
Are you using the latest version of the project?
You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.
What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!
(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
same old version looks to be working fine
relay:
name: relay
repository: paralusio/relay
tag: "v0.1.4"kubectl -n paralus exec relay-server-6547fb998-92z4g -c relay-server -it -- lsof | grep socket | wc -l SAG-VWDHQ744DR: Wed Sep 25 10:31:30 2024
14- I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
- I'm using the latest version of the project.