I am getting these on a test setup, where marathon and mesos-master running on the same node and iptables is not even configured.
W0222 23:03:48.829741 1112 process.cpp:1917] Failed to send 'mesos.internal.FrameworkErrorMessage' to '192.168.10.151:35530', connect: Failed connect, connection error: Connection refused W0222 23:03:48.831212 1112 process.cpp:1917] Failed to send 'mesos.internal.FrameworkErrorMessage' to '192.168.10.151:35530', connect: Failed to connect to 192.168.10.151:35530: Connection refused W0222 23:05:41.584399 1112 process.cpp:1917] Failed to send 'mesos.internal.FrameworkErrorMessage' to '192.168.10.151:42877', connect: Failed connect, connection error: Connection refused W0222 23:05:41.584664 1112 process.cpp:1917] Failed to send 'mesos.internal.FrameworkErrorMessage' to '192.168.10.151:42877', connect: Failed to connect to 192.168.10.151:42877: Connection refused Marathon logs these: Feb 22 23:30:54 m01 marathon: [2020-02-22 23:30:54,471] INFO Found no roles suitable for revive repetition. (mesosphere.marathon.core.launchqueue.impl.ReviveOffersStreamLogic$Reviv eRepeaterLogic:marathon-akka.actor.default-dispatcher-5) Feb 22 23:30:59 m01 marathon: [2020-02-22 23:30:59,482] INFO Found no roles suitable for revive repetition. (mesosphere.marathon.core.launchqueue.impl.ReviveOffersStreamLogic$Reviv eRepeaterLogic:marathon-akka.actor.default-dispatcher-12) Feb 22 23:31:04 m01 marathon: [2020-02-22 23:31:04,342] INFO Prompting Mesos for a heartbeat via explicit task reconciliation (mesosphere.marathon.core.heartbeat.MesosHeartbeatMonitor$$anon$1:marath on-akka.actor.default-dispatcher-2) Feb 22 23:31:04 m01 marathon: [2020-02-22 23:31:04,347] INFO Received fake heartbeat task-status update (mesosphere.marathon.core.heartbeat.MesosHeartbeatMonitor:Thread-130) Feb 22 23:31:04 m01 marathon: [2020-02-22 23:31:04,471] INFO Found no roles suitable for revive repetition. (mesosphere.marathon.core.launchqueue.impl.ReviveOffersStreamLogic$Reviv eRepeaterLogic:marathon-akka.actor.default-dispatcher-9)
