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

Problem with golang library in Relay server #138

Open
2 tasks
Santhosh-Radhakrishna opened this issue Sep 25, 2024 · 0 comments
Open
2 tasks

Problem with golang library in Relay server #138

Santhosh-Radhakrishna opened this issue Sep 25, 2024 · 0 comments
Labels
bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Santhosh-Radhakrishna
Copy link

Santhosh-Radhakrishna commented Sep 25, 2024

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
image

Chart & environment details
image

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.
@Santhosh-Radhakrishna Santhosh-Radhakrishna added bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 25, 2024
@nirav-rafay nirav-rafay transferred this issue from paralus/paralus Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant