kubeadm init kubelet complains default bind address already in use
kubeadm version 1.12.2
$ sudo kubeadm init --config kubeadm_new.config --ignore-preflight-errors=all
/var/log/syslog shows:
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438374 5101 server.go:1013] Started kubelet
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438406 5101 server.go:133] Starting to listen on 0.0.0.0:10250
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438446 5101 kubelet.go:1287] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory cache
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438492 5101 server.go:753] Starting health server failed: listen tcp 127.0.0.1:10248: bind: address already in use
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438968 5101 server.go:318] Adding debug handlers to kubelet server.
Nov 15 08:44:13 khteh-T580 kubelet[5101]: F1115 08:44:13.439455 5101 server.go:145] listen tcp 0.0.0.0:10250: bind: address already in use
I have tried sudo systemctl stop kubelet and manually kill kubelet process but to no avail. Any advice and insights are appreciated.
kubernetes bind ip-address kubelet
edited Nov 15 '18 at 1:48
Rico
28.4k95066
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
add a comment |
kubeadm version 1.12.2
$ sudo kubeadm init --config kubeadm_new.config --ignore-preflight-errors=all
/var/log/syslog shows:
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438374 5101 server.go:1013] Started kubelet
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438406 5101 server.go:133] Starting to listen on 0.0.0.0:10250
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438446 5101 kubelet.go:1287] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory cache
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438492 5101 server.go:753] Starting health server failed: listen tcp 127.0.0.1:10248: bind: address already in use
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438968 5101 server.go:318] Adding debug handlers to kubelet server.
Nov 15 08:44:13 khteh-T580 kubelet[5101]: F1115 08:44:13.439455 5101 server.go:145] listen tcp 0.0.0.0:10250: bind: address already in use
I have tried sudo systemctl stop kubelet and manually kill kubelet process but to no avail. Any advice and insights are appreciated.
kubernetes bind ip-address kubelet
edited Nov 15 '18 at 1:48
Rico
28.4k95066
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
you reset and try to run the init againsudo kubeadm reset
– sfgroups
Nov 15 '18 at 1:10
Tried but doesn't help
– Kok How Teh
Nov 15 '18 at 2:04
add a comment |
kubeadm version 1.12.2
$ sudo kubeadm init --config kubeadm_new.config --ignore-preflight-errors=all
/var/log/syslog shows:
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438374 5101 server.go:1013] Started kubelet
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438406 5101 server.go:133] Starting to listen on 0.0.0.0:10250
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438446 5101 kubelet.go:1287] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory cache
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438492 5101 server.go:753] Starting health server failed: listen tcp 127.0.0.1:10248: bind: address already in use
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438968 5101 server.go:318] Adding debug handlers to kubelet server.
Nov 15 08:44:13 khteh-T580 kubelet[5101]: F1115 08:44:13.439455 5101 server.go:145] listen tcp 0.0.0.0:10250: bind: address already in use
I have tried sudo systemctl stop kubelet and manually kill kubelet process but to no avail. Any advice and insights are appreciated.
kubernetes bind ip-address kubelet
edited Nov 15 '18 at 1:48
Rico
28.4k95066
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
kubeadm version 1.12.2
$ sudo kubeadm init --config kubeadm_new.config --ignore-preflight-errors=all
/var/log/syslog shows:
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438374 5101 server.go:1013] Started kubelet
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438406 5101 server.go:133] Starting to listen on 0.0.0.0:10250
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438446 5101 kubelet.go:1287] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory cache
Nov 15 08:44:13 khteh-T580 kubelet[5101]: E1115 08:44:13.438492 5101 server.go:753] Starting health server failed: listen tcp 127.0.0.1:10248: bind: address already in use
Nov 15 08:44:13 khteh-T580 kubelet[5101]: I1115 08:44:13.438968 5101 server.go:318] Adding debug handlers to kubelet server.
Nov 15 08:44:13 khteh-T580 kubelet[5101]: F1115 08:44:13.439455 5101 server.go:145] listen tcp 0.0.0.0:10250: bind: address already in use
I have tried sudo systemctl stop kubelet and manually kill kubelet process but to no avail. Any advice and insights are appreciated.
kubernetes bind ip-address kubelet
kubernetes bind ip-address kubelet
edited Nov 15 '18 at 1:48
Rico
28.4k95066
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
edited Nov 15 '18 at 1:48
Rico
28.4k95066
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
edited Nov 15 '18 at 1:48
Rico
28.4k95066
edited Nov 15 '18 at 1:48
Rico
28.4k95066
edited Nov 15 '18 at 1:48
Rico
28.4k95066
28.4k95066
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
asked Nov 15 '18 at 0:50
Kok How TehKok How Teh
129314
129314
you reset and try to run the init againsudo kubeadm reset
– sfgroups
Nov 15 '18 at 1:10
Tried but doesn't help
– Kok How Teh
Nov 15 '18 at 2:04
add a comment |
you reset and try to run the init againsudo kubeadm reset
– sfgroups
Nov 15 '18 at 1:10
Tried but doesn't help
– Kok How Teh
Nov 15 '18 at 2:04
you reset and try to run the init again
sudo kubeadm reset– sfgroups
Nov 15 '18 at 1:10
you reset and try to run the init again
sudo kubeadm reset– sfgroups
Nov 15 '18 at 1:10
Tried but doesn't help
– Kok How Teh
Nov 15 '18 at 2:04
Tried but doesn't help
– Kok How Teh
Nov 15 '18 at 2:04
add a comment |
3 Answers
3
active
oldest
votes
Here is what you can do:
Try the following command to find out which process is holding the port 10250
root@master admin]# ss -lntp | grep 10250
LISTEN 0 128 :::10250 :::* users:(("kubelet",pid=23373,fd=20))
It will give you PID of that process and name of that process. If it is unwanted process which is holding the port, you can always kill the process and that port becomes available to use by kubelet.
After killing the process again run the above command, it should return no value.
Just to be on safe side run kubeadm reset and then run kubeadm init and it should go through.
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
add a comment |
Have you tried using netstat to see what other process is running that has already bound to that port?
sudo netstat -tulpn | grep 10250
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
Then usessas @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.
– Zach Swanson
Nov 16 '18 at 14:18
add a comment |
I ditch kubeadm and use microk8s.
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310930%2fkubeadm-init-kubelet-complains-default-bind-address-already-in-use%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Here is what you can do:
Try the following command to find out which process is holding the port 10250
root@master admin]# ss -lntp | grep 10250
LISTEN 0 128 :::10250 :::* users:(("kubelet",pid=23373,fd=20))
It will give you PID of that process and name of that process. If it is unwanted process which is holding the port, you can always kill the process and that port becomes available to use by kubelet.
After killing the process again run the above command, it should return no value.
Just to be on safe side run kubeadm reset and then run kubeadm init and it should go through.
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
add a comment |
Here is what you can do:
Try the following command to find out which process is holding the port 10250
root@master admin]# ss -lntp | grep 10250
LISTEN 0 128 :::10250 :::* users:(("kubelet",pid=23373,fd=20))
It will give you PID of that process and name of that process. If it is unwanted process which is holding the port, you can always kill the process and that port becomes available to use by kubelet.
After killing the process again run the above command, it should return no value.
Just to be on safe side run kubeadm reset and then run kubeadm init and it should go through.
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
add a comment |
Here is what you can do:
Try the following command to find out which process is holding the port 10250
root@master admin]# ss -lntp | grep 10250
LISTEN 0 128 :::10250 :::* users:(("kubelet",pid=23373,fd=20))
It will give you PID of that process and name of that process. If it is unwanted process which is holding the port, you can always kill the process and that port becomes available to use by kubelet.
After killing the process again run the above command, it should return no value.
Just to be on safe side run kubeadm reset and then run kubeadm init and it should go through.
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
Here is what you can do:
Try the following command to find out which process is holding the port 10250
root@master admin]# ss -lntp | grep 10250
LISTEN 0 128 :::10250 :::* users:(("kubelet",pid=23373,fd=20))
It will give you PID of that process and name of that process. If it is unwanted process which is holding the port, you can always kill the process and that port becomes available to use by kubelet.
After killing the process again run the above command, it should return no value.
Just to be on safe side run kubeadm reset and then run kubeadm init and it should go through.
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
answered Nov 15 '18 at 3:24
Prafull LadhaPrafull Ladha
3,6281422
3,6281422
add a comment |
add a comment |
Have you tried using netstat to see what other process is running that has already bound to that port?
sudo netstat -tulpn | grep 10250
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
Then usessas @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.
– Zach Swanson
Nov 16 '18 at 14:18
add a comment |
Have you tried using netstat to see what other process is running that has already bound to that port?
sudo netstat -tulpn | grep 10250
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
Then usessas @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.
– Zach Swanson
Nov 16 '18 at 14:18
add a comment |
Have you tried using netstat to see what other process is running that has already bound to that port?
sudo netstat -tulpn | grep 10250
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
Have you tried using netstat to see what other process is running that has already bound to that port?
sudo netstat -tulpn | grep 10250
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
answered Nov 15 '18 at 0:57
Zach SwansonZach Swanson
714
714
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
Then usessas @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.
– Zach Swanson
Nov 16 '18 at 14:18
add a comment |
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
Then usessas @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.
– Zach Swanson
Nov 16 '18 at 14:18
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
netstat command not found in Ubuntu 18.10
– Kok How Teh
Nov 15 '18 at 1:54
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
@KokHowTeh you need to install the net-tools package to use it.
– Zach Swanson
Nov 15 '18 at 13:07
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
net-tools is obsolete
– Kok How Teh
Nov 16 '18 at 5:03
Then use
ss as @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.– Zach Swanson
Nov 16 '18 at 14:18
Then use
ss as @prafull-ladha suggested in the other answer. It has the same command structure. Regardless of what tool you want to use, the error message from k8 indicates that some other process is already bound to that ip:port, so just figure that out and kill it.– Zach Swanson
Nov 16 '18 at 14:18
add a comment |
I ditch kubeadm and use microk8s.
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
add a comment |
I ditch kubeadm and use microk8s.
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
add a comment |
I ditch kubeadm and use microk8s.
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
I ditch kubeadm and use microk8s.
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
answered Nov 27 '18 at 0:49
Kok How TehKok How Teh
129314
129314
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310930%2fkubeadm-init-kubelet-complains-default-bind-address-already-in-use%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
you reset and try to run the init again
sudo kubeadm reset– sfgroups
Nov 15 '18 at 1:10
Tried but doesn't help
– Kok How Teh
Nov 15 '18 at 2:04