search

d2iq-archive / marathon

Deploy and manage containers (including Docker) on top of Apache Mesos at scale.
https://mesosphere.github.io/marathon/
Apache License 2.0
4.07k stars 843 forks source link

docker image also "Loading applications" #7200

Open f1-outsourcing opened 4 years ago

f1-outsourcing commented 4 years ago

I thought I maybe had some dependency problem so I tried your docker hub image. When I start the latest dockerhub container with:

docker run -v /dev/log:/dev/log -u root -it --network host --entrypoint /bin/bash mesosphere/marathon

and then:

/marathon/bin/marathon --master m01.local:5050 --zk zk://m01.local:2181/v11025 --framework_name v11025 --http_port 7070 --hostname test2.local

I still have 'Loading Applications' and endpoints like v2/info do not respond.

http://test2.local:7070/v2 (gives still uri not found) http://test2.local:7070/v2/info (keeps loading)

[2020-07-18 16:45:00,289] INFO initiate task reconciliation (mesosphere.marathon.MarathonSchedulerActor:marathon-akka.actor.default-dispatcher-5) [2020-07-18 16:45:00,304] INFO Requesting task reconciliation with the Mesos master (mesosphere.marathon.SchedulerActions:scheduler-actions-thread-0) [2020-07-18 16:45:00,311] INFO task reconciliation has finished (mesosphere.marathon.MarathonSchedulerActor:marathon-akka.actor.default-dispatcher-4) [2020-07-18 16:45:00,320] INFO Message [mesosphere.marathon.MarathonSchedulerActor$TasksReconciled$] from Actor[akka://marathon/user/MarathonScheduler/$a#1961271917] to Actor[akka://marathon/deadLetters] was not delivered. [1] dead letters encountered. If this is not an expected behavior, then [Actor[akka://marathon/deadLetters]] may have terminated unexpectedly, This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'. (akka.actor.DeadLetterActorRef:marathon-akka.actor.default-dispatcher-8)