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

dial tcp 10.X.X.X:3000: connect: connection refused (CrashLoopBackOff on rocketchat-rocketchat pod) #138

Open
abctaylor opened this issue Apr 3, 2024 · 2 comments

Comments

@abctaylor
Copy link

Deploying this Helm chart, the first thing I see is this:

[root@kube2-lon rocketchat]# k get pods -o wide
NAME                                     READY   STATUS             RESTARTS     AGE    IP             NODE                      NOMINATED NODE   READINESS GATES
rocketchat-mongodb-0                     1/1     Running            0            3m1s   10.3.130.59    k8s2-lon.core.xxx.net   <none>           <none>
rocketchat-postgresql-0                  1/1     Running            0            3m1s   10.3.130.27    k8s2-lon.core.xxx.net   <none>           <none>
rocketchat-rocketchat-79988457b5-p4qph   0/1     CrashLoopBackOff   3 (3s ago)   3m1s   10.3.132.130   k8s3-lon.core.xxx.net   <none>           <none>

Logs for that pod show this:

15s (x5 over 105s)     Warning   Unhealthy                Pod/rocketchat-rocketchat-79988457b5-p4qph           Readiness probe failed: Get "http://10.3.132.130:3000/health": dial tcp 10.3.132.130:3000: connect: connection refused
0s (x4 over 54s)       Warning   BackOff                  Pod/rocketchat-rocketchat-79988457b5-p4qph           Back-off restarting failed container rocketchat in pod rocketchat-rocketchat-79988457b5-p4qph_rocketchat(68dca7ae-900f-48fe-96a2-4ece6e724299)

Ideas?

values.yaml:

host: rocket.core.xxx.net
mongodb:
  auth:
    passwords:
      - rocketchat
    rootPassword: xxx
ingress:
  enabled: true
  tls:
    - secretName: cert-rocket.core.xxx.net
      hosts:
        - rocket.core.xxx.net
        - rocket

(I've also tried a simpler values.yaml with just the mongodb parts, uninstalled, deleted PVCs, and installed - same result).

@abctaylor
Copy link
Author

Interesting, in the mongodb container:

[root@kube2-lon rocketchat]# k exec -it  rocketchat-mongodb-0 -- bash
Defaulted container "mongodb" out of: mongodb, volume-permissions (init)
I have no name!@rocketchat-mongodb-0:/$ 

@abctaylor
Copy link
Author

At this point it pretty clearly seems like a bug.

MongoServerSelectionError: Server selection timed out after 30000 ms

From: /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:218

Can give a full stack trace if interest from the devs.

A lot turning up on Google (cursory search: https://www.google.com/search?client=firefox-b-d&q=rocket+chat+MongoServerSelectionError).

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

1 participant