Kubernetes master can not find minion

The log is reported as follows:
shell
Nov 25 09:05:34 fedora201 kube-scheduler[496]: E1125 09:05:34.514772 00496 factory.go:179] Error scheduling apache: failed to find a fit for pod: {{ } {apache default /api/v1beta1/pods/apache 7 2014-11-24 18:27:56 +0800 CST map[name:apache] map[]} {{v1beta1 apache 8e6f8482-73c4-11e4-9c8f-000c2951bd4d [] [{master fedora/apache [] [{ 80 80 TCP }] [] 0 0 [] <nil> <nil> false }] {0x9e97d0 <nil> <nil>}} Running map[]} {{ [] [] {<nil> <nil> <nil>}} Waiting map[]} map[]}; retrying
Nov 25 09:05:36 fedora201 kube-scheduler[496]: E1125 09:05:36.319853 00496 event.go:51] Sleeping: Unable to write event: events "" already exists

Service start status
shell
[root@fedora201 ~]# netstat -tulnp | grep -E "(kube)|(docker)|(cadvisor)"
tcp 0 0 127.0.0.1:10251 0.0.0.0:* LISTEN 496/kube-scheduler
tcp 0 0 127.0.0.1:10252 0.0.0.0:* LISTEN 499/kube-controller
tcp6 0 0 :::7080 :::* LISTEN 500/kube-apiserver
tcp6 0 0 :::8080 :::* LISTEN 500/kube-apiserver

But can not find minion
shell
[root@fedora201 ~]# kubectl get minions
NAME
2014-11-25 add comment share it

  • Weibo
  • QZONE
  • Micro letter

Did not find the relevant results

    Invited:

    Yang zhangxian – Cisco Systems Operation and Maintenance Engineer

    We agreed from:

    1. First check your minion server on the kubelet port 10250 is listening.
    2. If listening, check from master to minion whether telent 10250 port.
    3. If not, check the minion's firewall if the block 10250port.

    Heads up! This alert needs your attention, but it's not super important.