Comments (4)
After waiting for about 10 minutes, flanneld.service becomes active:
core@c1 ~ $ systemctl status flanneld.service
● flanneld.service - Network fabric for containers
Loaded: loaded (/usr/lib64/systemd/system/flanneld.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/flanneld.service.d
└─40-ExecStartPre-symlink.conf.conf
Active: active (running) since Fri 2016-06-03 23:48:35 UTC; 6min ago
But coreos-cloudinit-120749834.service
seems already marked failed:
core@c1 ~ $ systemctl status coreos-cloudinit-120749834.service
● coreos-cloudinit-120749834.service - Unit generated and executed by coreos-cloudinit on behalf of user
Loaded: loaded (/run/systemd/system/coreos-cloudinit-120749834.service; static; vendor preset: disabled)
Drop-In: /run/systemd/system/coreos-cloudinit-120749834.service.d
└─50-Description.conf, 50-ExecStart.conf
Active: failed (Result: exit-code) since Fri 2016-06-03 23:37:40 UTC; 20min ago
Main PID: 1172 (code=exited, status=1/FAILURE)
from vagrant-coreos.
Also, core@c1 ~ $ systemctl list-units | grep kube
shows nothing. And kubectl get nodes
from outside of the cluster doesn't work:
MacBook-Pro:/Users/yiwang/work/coreos-kubernetes/multi-node/vagrant (master)
$ ./kubectl get nodes
The connection to the server 172.17.4.101:443 was refused - did you specify the right host or port?
It seems that kubelet.service
is in status of disabled.
core@c1 ~ $ systemctl list-unit-files | grep kube
kubelet.service disabled
It seems that the failure of flanneld stopped coreos-cloudinit-120749834.service
from enabling and starting kubelet.service
. So I manually restarted it:
core@c1 ~ $ sudo systemctl restart coreos-cloudinit-120749834.service
It works and kubelet.service
is running now:
core@c1 ~ $ systemctl status kubelet.service
● kubelet.service
Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2016-06-04 00:48:56 UTC; 1min 35s ago
Process: 2156 ExecStartPre=/usr/bin/mkdir -p /etc/kubernetes/manifests (code=exited, status=0/SUCCESS)
The same works on VM w1 as well:
core@w1 ~ $ systemctl list-units | grep kube
kubelet.service loaded active running kubelet.service
core@w1 ~ $ systemctl status kubelet.service
● kubelet.service
Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2016-06-04 00:53:25 UTC; 2min 44s ago
from vagrant-coreos.
But kubectl still fails:
$ kubectl get nodes
The connection to the server 172.17.4.101:443 was refused - did you specify the right host or port?
from vagrant-coreos.
I tried rebooting all VMs, without an interference like above, kubectl works. However, I am still interested with details during the long time (~10 mins) Kubernetes startup time.
from vagrant-coreos.
Related Issues (4)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vagrant-coreos.