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

[BUG] polardbx cluster create ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-gms:3306' (110) #8846

Closed
JashBook opened this issue Jan 22, 2025 · 0 comments · Fixed by apecloud/kubeblocks-addons#1433
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@JashBook
Copy link
Collaborator

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. create cluster
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: polardbx-joqvbv
  namespace: default
spec:
  componentSpecs:
  - componentDef: polardbx-gms-1.0.0-alpha.0
    name: gms
    replicas: 3
    resources:
      limits:
        cpu: 500m
        memory: 1Gi
      requests:
        cpu: 500m
        memory: 1Gi
    serviceVersion: 2.3.0
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
  - componentDef: polardbx-dn-1.0.0-alpha.0
    name: dn
    replicas: 3
    resources:
      limits:
        cpu: 500m
        memory: 1Gi
      requests:
        cpu: 500m
        memory: 1Gi
    serviceVersion: 2.3.0
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
  - componentDef: polardbx-cn-1.0.0-alpha.0
    name: cn
    replicas: 1
    resources:
      limits:
        cpu: 500m
        memory: 1Gi
      requests:
        cpu: 500m
        memory: 1Gi
    serviceVersion: 2.3.0
  - componentDef: polardbx-cdc-1.0.0-alpha.0
    name: cdc
    replicas: 1
    resources:
      limits:
        cpu: 500m
        memory: 1Gi
      requests:
        cpu: 500m
        memory: 1Gi
    serviceVersion: 2.3.0
  terminationPolicy: WipeOut
  1. See error
➜  ~ kubectl get cluster polardbx-joqvbv 
NAME              CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
polardbx-joqvbv                        WipeOut              Creating   25m
➜  ~ 
➜  ~ kubectl get pod -l app.kubernetes.io/instance=polardbx-joqvbv 
NAME                    READY   STATUS     RESTARTS   AGE
polardbx-joqvbv-cdc-0   0/2     Init:0/1   0          25m
polardbx-joqvbv-cn-0    0/2     Init:0/2   0          25m
polardbx-joqvbv-dn-0    3/3     Running    0          25m
polardbx-joqvbv-dn-1    3/3     Running    0          23m
polardbx-joqvbv-dn-2    3/3     Running    0          22m
polardbx-joqvbv-gms-0   3/3     Running    0          25m
polardbx-joqvbv-gms-1   3/3     Running    0          23m
polardbx-joqvbv-gms-2   3/3     Running    0          22m

logs pod

➜  ~ kubectl logs polardbx-joqvbv-cdc-0 wait-cn-ready 
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-cn:3306' (110)
cn is not ready
mysql: [Warning] Using a password on the command line interface can be insecure.
➜  ~ 
➜  ~ kubectl logs polardbx-joqvbv-cn-0 metadb-init 
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-gms:3306' (110)
wait gms ready
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'polardbx-joqvbv-gms:3306' (110)
wait gms ready
mysql: [Warning] Using a password on the command line interface can be insecure.
➜  ~ 

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants