There's not enough information to understand the situation. How did you kill the task? Did the task get correctly marked as killed? Did the killed notification get correctly acknowledged?
On Sun, Feb 2, 2020 at 9:04 AM Marc Roos <m.r...@f1-outsourcing.eu> wrote: > > > > Because the instance was not showing in the marathon gui. I have killed > a task with kill -KILL, assuming it would restart, yet it did not. > > I think it has to do with these messages. Why do I have these even, when > I can just ping them? > > W0202 14:46:51.215673 359364 process.cpp:1480] Failed to link to > '192.168.122.253:35071', connect: Failed connect: connection closed > W0202 14:46:51.217136 359364 process.cpp:1480] Failed to link to > '192.168.122.95:41400', connect: Failed connect: connection closed > W0202 14:46:51.217594 359364 process.cpp:1480] Failed to link to > '192.168.122.94:41974', connect: Failed connect: connection closed > W0202 14:46:51.218037 359364 process.cpp:1480] Failed to link to > '192.168.122.13:33447', connect: Failed connect: connection closed > > > > [@mesos]# ping -c 2 192.168.122.95 > PING 192.168.122.95 (192.168.122.95) 56(84) bytes of data. > 64 bytes from 192.168.122.95: icmp_seq=1 ttl=64 time=0.062 ms > 64 bytes from 192.168.122.95: icmp_seq=2 ttl=64 time=0.051 ms > > [@mesos]# ping -c 2 192.168.122.94 > PING 192.168.122.94 (192.168.122.94) 56(84) bytes of data. > 64 bytes from 192.168.122.94: icmp_seq=1 ttl=64 time=0.053 ms > 64 bytes from 192.168.122.94: icmp_seq=2 ttl=64 time=0.045 ms > > [@mesos]# ping -c 2 192.168.122.13 > PING 192.168.122.13 (192.168.122.13) 56(84) bytes of data. > 64 bytes from 192.168.122.13: icmp_seq=1 ttl=64 time=0.069 ms > 64 bytes from 192.168.122.13: icmp_seq=2 ttl=64 time=0.051 ms > >
