At almost the same time, I had another node entered the same situation, the 
log of kubelet:

$ systemctl status kubelet
* kubelet.service - Kubernetes Kubelet
   Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2017-11-29 16:04:21 CST; 1 months 4 
days ago
     Docs: https://github.com/kubernetes/kubernetes
 Main PID: 22966 (kubelet)
    Tasks: 75
   Memory: 364.2M
      CPU: 1w 3h 13min 2.144s
   CGroup: /system.slice/kubelet.service
           |-22966 /kubelet --address=0.0.0.0 --allow-privileged=true 
--cluster-dns=192.168.192.10 --cluster-domain=cluster.local --
cloud-provider= --port=10250 --lock-file=/var/run/lock/kubelet.lock 
--exit-on-lock-contention --node-labels=worker=true --pod-manife
st-path=/etc/kubernetes/manifests 
--kubeconfig=/etc/kubernetes/kubeconfig.yaml --require-kubeconfig=true 
--network-plugin=cni --cni-
conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin --logtostderr=true
           `-23109 journalctl -k -f

Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count
Jan 02 10:31:41 ae02.pek.prod.com kubelet-wrapper[22966]: fatal error: 
runtime·unlock: lock count

10255 port wasn't response, and strace hung here:

# strace -p 22966
Process 22966 attached
read(25, ^CProcess 22966 detached
 <detached ...>


-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to