Problem with golang library in Relay server #266
Labels
bug
Something isn't working
help wanted
Extra attention is needed
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Expected vs actual behavior
After some time the external cluster which been connected to the Paralus server ceases to be accessible from the web console.
Images here
Button "reconnect" doesn't fix this problem
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
andhelm version
. Any other information that you have, eg. logs and custom values, is highly appreciated!Red Hat Enterprise Linux release 8.8 (Ootpa)
clientVersion:
buildDate: "2023-07-19T12:20:54Z"
compiler: gc
gitCommit: fa3d7990104d7c1f16943a67f11b154b71f6a132
gitTreeState: clean
gitVersion: v1.27.4
goVersion: go1.20.6
major: "1"
minor: "27"
platform: linux/amd64
kustomizeVersion: v5.0.1
serverVersion:
buildDate: "2023-07-19T12:14:49Z"
compiler: gc
gitCommit: fa3d7990104d7c1f16943a67f11b154b71f6a132
gitTreeState: clean
gitVersion: v1.27.4
goVersion: go1.20.6
major: "1"
minor: "27"
platform: linux/amd64
Helm: version.BuildInfo{Version:"v3.12.3", GitCommit:"3a31588ad33fe3b89af5a2a54ee1d25bfe6eaa5e", GitTreeState:"clean", GoVersion:"go1.20.7"}
(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
I was able to solve this problem using values.yml with parameter images.reley.tag="v0.1.4". In this Reley Images using golang library golang.org/x/net v0.0.0-20210825183410-e898025ed96a thich resolve problem with number of open sokcet in virtual machine. For example, now i see:
[@~]# kubectl -n paralus exec relay-server-5b459f7-85vkd -c relay-server -it -- lsof | grep socket | wc -l
63
When I used the latest version (images.reley.tag="v0.1.6"), there were 2.5K+ open sockets.
A similar problem was described and solved earlier, but with the chart version ztka:0.2.{5,6} it happened again.
The text was updated successfully, but these errors were encountered: