FAILING TO CREATE HA CLUSTER #5258
rkitindi-kr
started this conversation in
General
Replies: 7 comments
-
|
Errors from another node: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The logs suggest that you're only waiting a minute or so for RKE2 to start. Depending on how long it takes your nodes to pull the etcd and kubernetes images from the registry, it may take a bit longer to finish starting. Assuming the issue does not resolve itself after application of a little bit of patience, I would check the kubelet.log and containerd.log files on the first server, as well as the files under /var/log/pods if any are present. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you, Brad.
Is there any parameter that I can add into confi.yaml file to delay RKE2-server start time?
Raj
From: Brad Davidson ***@***.***>
Sent: Thursday, January 11, 2024 2:22 PM
To: rancher/rke2 ***@***.***>
Cc: Kitindi, Rajabu (NonEmp) ***@***.***>; Author ***@***.***>
Subject: Re: [rancher/rke2] FAILING TO CREATE HA CLUSTER (Issue #5249)
** [EXTERNAL EMAIL]: Do not click links or open attachments unless you recognize the sender and know the content is safe. **
The logs show that you're only waiting a minute or so for RKE2 to start. Depending on how long it takes your nodes to pull the etcd and kubernetes images from the registry, it may take a bit longer to finish starting.
Assuming the issue does not resolve itself after application of a little bit of patience, I would check the kubelet.log and containerd.log files on the first server, as well as the files under /var/log/pods if any are present.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/rancher/rke2/issues/5249*issuecomment-1887813559__;Iw!!J-PWDud9Isc!i0lhGm8X24Kvba3V6OxrQ4cJTQEFtp_euNNpIK1x0nagN9lBwPGu3j2tACYxdnlDb-0Z9TyA4EuLBl2VZdKO0tLxBfGh$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BAYPIUR4EKUNF5GEB3LFUPLYOA3XBAVCNFSM6AAAAABBW675NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBXHAYTGNJVHE__;!!J-PWDud9Isc!i0lhGm8X24Kvba3V6OxrQ4cJTQEFtp_euNNpIK1x0nagN9lBwPGu3j2tACYxdnlDb-0Z9TyA4EuLBl2VZdKO0qRsIEsx$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
…________________________________
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
________________________________
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
It takes very long time and in the end RKE-server never starts
From: Brad Davidson ***@***.***>
Sent: Thursday, January 11, 2024 2:22 PM
To: rancher/rke2 ***@***.***>
Cc: Kitindi, Rajabu (NonEmp) ***@***.***>; Author ***@***.***>
Subject: Re: [rancher/rke2] FAILING TO CREATE HA CLUSTER (Issue #5249)
** [EXTERNAL EMAIL]: Do not click links or open attachments unless you recognize the sender and know the content is safe. **
The logs show that you're only waiting a minute or so for RKE2 to start. Depending on how long it takes your nodes to pull the etcd and kubernetes images from the registry, it may take a bit longer to finish starting.
Assuming the issue does not resolve itself after application of a little bit of patience, I would check the kubelet.log and containerd.log files on the first server, as well as the files under /var/log/pods if any are present.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/rancher/rke2/issues/5249*issuecomment-1887813559__;Iw!!J-PWDud9Isc!i0lhGm8X24Kvba3V6OxrQ4cJTQEFtp_euNNpIK1x0nagN9lBwPGu3j2tACYxdnlDb-0Z9TyA4EuLBl2VZdKO0tLxBfGh$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BAYPIUR4EKUNF5GEB3LFUPLYOA3XBAVCNFSM6AAAAABBW675NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBXHAYTGNJVHE__;!!J-PWDud9Isc!i0lhGm8X24Kvba3V6OxrQ4cJTQEFtp_euNNpIK1x0nagN9lBwPGu3j2tACYxdnlDb-0Z9TyA4EuLBl2VZdKO0qRsIEsx$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
…________________________________
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
________________________________
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Please take a look at the logs I suggested examining earlier. Also, please avoid replying via e-mail, your client apparently formats the replies in a way that prevents the GitHub mail relay from properly filtering out the noise from your responses. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I checked logs you suggested I didn't find anything interesting Can you help me to understand why do we see connection refused on port 2379 while port server is listening on that port and IP? Jan 12 02:45:45 ecs2u rke2[520627]: time="2024-01-12T02:45:45Z" level=info msg="Cluster-Http-Server 2024/01/12 02:45:45 http: TLS handshake error from 127.0.0.1:58658: remote error: tls: bad certificate"
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm going to convert this to a discussion, so we can continue to help you, but declassify this as an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Guys
I am pretty new to RKE2 and I need your help.
I am trying to create a HA RKE2 cluster but for some reason I am getting a bunch of errors and I am not sure what is the problem. Cluster join fails and these are error logs I see:
Can someone point me to the correct direction?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions