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

No servers available for connection #56

Open
andragabr opened this issue Oct 21, 2019 · 4 comments
Open

No servers available for connection #56

andragabr opened this issue Oct 21, 2019 · 4 comments

Comments

@andragabr
Copy link

kubectl logs bmrg-dev-nats-streamer-2
[1] 2019/10/21 09:53:54.901940 [INF] STREAM: Starting nats-streaming-server[bmrg-dev-nats-streamer] version 0.16.2
[1] 2019/10/21 09:53:54.901996 [INF] STREAM: ServerID: h6KMqx3nUR7PZU62q3jKVZ
[1] 2019/10/21 09:53:54.902000 [INF] STREAM: Go version: go1.11.13
[1] 2019/10/21 09:53:54.902005 [INF] STREAM: Git commit: [910d6e1]
[1] 2019/10/21 09:53:56.910836 [INF] STREAM: Shutting down.
[1] 2019/10/21 09:53:56.911025 [FTL] STREAM: Failed to start: nats: no servers available for connection

"nats-operator:latest"
10-deployments.yaml connecteverything/nats-operator:0.6.0
deployment.yaml synadia/nats-streaming-operator:v0.2.2-v1alpha1

@mlipovsky
Copy link

same problem

@mlipovsky
Copy link

Logs with debug:

[1] 2020/01/06 09:19:30.888847 [INF] STREAM: Starting nats-streaming-server[stan-service] version 0.16.2
[1] 2020/01/06 09:19:30.888932 [INF] STREAM: ServerID: Azp1VGKzj4L2Ioe8BKJzeU
[1] 2020/01/06 09:19:30.888935 [INF] STREAM: Go version: go1.11.13
[1] 2020/01/06 09:19:30.888937 [INF] STREAM: Git commit: [910d6e1]
[1] 2020/01/06 09:19:32.943148 [INF] STREAM: Shutting down.
[1] 2020/01/06 09:19:32.943310 [DBG] STREAM: connection "_NSS-stan-service-send" has been closed
[1] 2020/01/06 09:19:32.943438 [DBG] STREAM: connection "_NSS-stan-service-general" has been closed
[1] 2020/01/06 09:19:32.943481 [FTL] STREAM: Failed to start: nats: no servers available for connection

@halink0803
Copy link

I am currently got this problem? Anyone know how to resolve it?

@halink0803
Copy link

Hi, I just figured it out. In my case, the problem is not about nats-server or client, but my gcp firewall config. The server have not open the port 4222 to the client. Fixed that, and it works normally.

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

3 participants