<p>kubeadm version 1.12.2</p>

<p><code>$ sudo kubeadm init --config kubeadm_new.config --ignore-preflight-errors=all</code></p>

<p>/var/log/syslog shows:</p>

<pre><code>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
</code></pre>

<p>I have tried <code>sudo systemctl stop kubelet</code> and manually kill kubelet process but to no avail. Any advice and insights are appreciated.</p>

<p>Have you tried using netstat to see what other process is running that has already bound to that port?</p>

<pre><code>sudo netstat -tulpn | grep 10250
</code></pre>
