Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

Thanks for the update Nan. k8s enabling firewall rules that would block traffic to the master seems a bit odd. Looks like a bug to me, in the head of the branch. If you are able to reproduce it consistently, could you file an issue against kubernetes mesos. regards, Avinash On Tue, Dec 29, 2015

Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

Hi Avinash, Sorry for my unclear expression! The root cause is not related to k8s, but the CentOS which k8s is running on. It is related to iptables. After executing "iptables -F", it works! Best Regards Nan Xiao On Wed, Dec 30, 2015 at 11:41 PM, Avinash Sridharan

Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

lsof command will show only actively opened file descriptors. So if you ran the command after seeing the error logs in the master, most probably the master had already closed this fd. Just throwing a few other things to look at, that might give some more insights. * Run the "netstat -na" and

Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

Hi Avinash, Thanks very much for your reply! The root cause has been found: the k8s server has enabled the iptables which blocks connection from Mesos master; after disable it, it works! Best Regards Nan Xiao On Wed, Dec 30, 2015 at 3:22 AM, Avinash Sridharan wrote: >

Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

BTW, using "lsof" command finds there are only 16 file descriptors. I don't know why Mesos master try to close "fd 17". Best Regards Nan Xiao On Tue, Dec 29, 2015 at 11:32 AM, Nan Xiao wrote: > Hi Klaus, > > Firstly, thanks very much for your answer! > > The km

Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

It seems Kubernetes is down; would you help to check kubernetes's status (km)? Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform Symphony/DCOS Development & Support, STG, IBM GCG +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me On Mon, Dec 28, 2015 at 6:35 PM, Nan

The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

Hi all, Greetings from me! I am trying to follow this tutorial (https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/mesos.md) to deploy "k8s on Mesos" on local machines: The k8s is the newest master branch, and Mesos is the 0.26 edition. After running Mesos

Re: The issue of "Failed to shutdown socket with fd xx: Transport endpoint is not connected" on Mesos master

Hi Klaus, Firstly, thanks very much for your answer! The km processes are all live: root 129474 128024 2 22:26 pts/000:00:00 km apiserver --address=15.242.100.60 --etcd-servers=http://15.242.100.60:4001 --service-cluster-ip-range=10.10.10.0/24 --port= --cloud-provider=mesos