Any failed tasks in the list? Does the Marathon log contain lines about non matching offers?
> On 10 Feb 2015, at 10:29, Emre Tekelioğlu <[email protected]> wrote: > > Slaves > > Activated 1 > Deactivated 0 > > > Resources > > CPUs Mem > Total 4 10.7 GB > Used 0.1 128 MB > Offered 0 0 B > Idle 3.9 10.6 GB > > > Active Frameworks > > ID Host User Name Active Tasks CPUs Mem Max Share > Registered Re-Registered > …5050-1278-0001 maas01... root > chronos-2.3.1_mesos-0.20.1-SNAPSHOT 0 0 0 B 0% 16 > hours ago 16 hours ago > …5050-1278-0000 maas01... root marathon 1 0.1 > 128 MB 2.5% 16 hours ago 16 hours ago > > 2015-02-10 10:35 GMT+02:00 Dario Rexin <[email protected] > <mailto:[email protected]>>: > Please check how many slaves are connected to the master, how many resources > it shows and if Marathon is properly connected. > > > > On 10.02.2015, at 09:31, Emre Tekelioğlu <[email protected] > <mailto:[email protected]>> wrote: > >> Yes you are right, I've already updated it before i wrote here but i think >> without a service restart. >> Now marathon shows version 0.8.0 but nothing changed :| >> >> 2015-02-09 18:05 GMT+02:00 Dario Rexin <[email protected] >> <mailto:[email protected]>>: >> It should be in the Mesosphere repos since Thursday last week. >> >>> On 09 Feb 2015, at 17:02, Emre Tekelioğlu <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> I installed mesos from repo, did you know when ubuntu repo will update? >>> >>> 2015-02-09 17:46 GMT+02:00 Dario Rexin <[email protected] >>> <mailto:[email protected]>>: >>> This looks normal. But could you try updating to Marathon 0.8.0? We fixed a >>> couple of deployment related bugs in there. >>> >>> >>>> On 09 Feb 2015, at 16:38, Emre Tekelioğlu <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi Dario, >>>> >>>> I found these logs in syslog. >>>> Is it normal? >>>> >>>> Feb 9 15:26:38 maas01 marathon[8808]: [2015-02-09 15:26:38,537] INFO >>>> Computed new deployment plan: DeploymentPlan(2015-02-09T15:26:38.437Z, >>>> (Step(Vector(Start(App(/testtest1, None)), 0))), >>>> Step(List(Scale(App(/testtest1, None)), 5))))) >>>> (mesosphere.marathon.upgrade.DeploymentPlan$:246) >>>> Feb 9 15:26:38 maas01 marathon[8808]: [INFO] [02/09/2015 15:26:38.539] >>>> [marathon-akka.actor.default-dispatcher-14] >>>> [akka://marathon/user/MarathonScheduler/$a/UpgradeManager/5cf28be2-af8e-427d-90a2-5b0388b7009a/$a >>>> <>] Successfully started 0 instances of /testtest1 >>>> Feb 9 15:26:38 maas01 marathon[8808]: [2015-02-09 15:26:38,557] INFO >>>> Starting app /testtest1 (mesosphere.marathon.SchedulerActions:363) >>>> Feb 9 15:26:38 maas01 marathon[8808]: [2015-02-09 15:26:38,557] INFO >>>> Already running 0 instances of /testtest1. Not scaling. >>>> (mesosphere.marathon.SchedulerActions:512) >>>> >>>> >>>> 2015-02-09 16:10 GMT+02:00 Dario Rexin <[email protected] >>>> <mailto:[email protected]>>: >>>> Could you please post the relevant log output of Mesos and Marathon? >>>> >>>>> On 09 Feb 2015, at 15:06, Emre Tekelioğlu <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> I added the app with REST API, but nothing changed. >>>>> Status stuck in "Deploying" >>>>> I also run these commands; >>>>> >>>>> echo 'docker,mesos' > /etc/mesos-slave/containerizers >>>>> echo '5mins' > /etc/mesos-slave/executor_registration_timeout >>>>> >>>>> App config is like that >>>>> >>>>> { >>>>> "id":"/test2", >>>>> "cmd":null, >>>>> "args":[ >>>>> >>>>> ], >>>>> "user":null, >>>>> "env":{ >>>>> >>>>> }, >>>>> "instances":5, >>>>> "cpus":0.1, >>>>> "mem":128.0, >>>>> "disk":512.0, >>>>> "executor":"", >>>>> "constraints":[ >>>>> >>>>> ], >>>>> "uris":[ >>>>> >>>>> ], >>>>> "storeUrls":[ >>>>> >>>>> ], >>>>> "ports":[ >>>>> 10001 >>>>> ], >>>>> "requirePorts":false, >>>>> "backoffSeconds":1, >>>>> "backoffFactor":1.15, >>>>> "maxLaunchDelaySeconds":3600, >>>>> "container":{ >>>>> "type":"DOCKER", >>>>> "volumes":[ >>>>> >>>>> ], >>>>> "docker":{ >>>>> "image":"fehmicansaglam/progressed.io <http://progressed.io/>", >>>>> "network":null, >>>>> "portMappings":null, >>>>> "privileged":false, >>>>> "parameters":[ >>>>> >>>>> ] >>>>> } >>>>> }, >>>>> "healthChecks":[ >>>>> >>>>> ], >>>>> "dependencies":[ >>>>> >>>>> ], >>>>> "upgradeStrategy":{ >>>>> "minimumHealthCapacity":1.0, >>>>> "maximumOverCapacity":1.0 >>>>> }, >>>>> "labels":{ >>>>> >>>>> }, >>>>> "version":"2015-02-09T13:55:52.577Z" >>>>> } >>>>> >>>>> >>>>> Thanks >>>>> >>>>> >>>>> 2015-02-09 15:43 GMT+02:00 Dario Rexin <[email protected] >>>>> <mailto:[email protected]>>: >>>>> Yes, it’s currently not possible to deploy containers with the web UI. >>>>> >>>>>> On 09 Feb 2015, at 14:42, Emre Tekelioğlu <[email protected] >>>>>> <mailto:[email protected]>> wrote: >>>>>> >>>>>> Hi Dario, >>>>>> >>>>>> I couldn't find the container section in my Marathon UI when i click New >>>>>> App, should i use only REST API to do that? >>>>>> >>>>>> Regards, >>>>>> Emre >>>>>> >>>>>> 2015-02-09 15:09 GMT+02:00 Dario Rexin <[email protected] >>>>>> <mailto:[email protected]>>: >>>>>> Hi Emre, >>>>>> >>>>>> Mesos and Marathon have full support for running Docker containers, you >>>>>> can just specify them in the app definition, no need to run `docker run >>>>>> …` as a command. Try this app definition instead: >>>>>> >>>>>> { >>>>>> "id":"/progressed-io", >>>>>> "instances":5, >>>>>> "cpus":0.1, >>>>>> "mem":128.0, >>>>>> "disk":512.0, >>>>>> “container”: { >>>>>> “docker”: { >>>>>> “image”: “fehmicansaglam/progressed.io <http://progressed.io/>" >>>>>> } >>>>>> } >>>>>> } >>>>>> >>>>>> Please make sure to start your mesos-slave process with >>>>>> “—containerizers=docker,mesos” >>>>>> >>>>>> Hope this helps. >>>>>> >>>>>> Cheers, >>>>>> Dario >>>>>> >>>>>>> On 09 Feb 2015, at 14:02, Emre Tekelioğlu <[email protected] >>>>>>> <mailto:[email protected]>> wrote: >>>>>>> >>>>>>> Hi Dario >>>>>>> >>>>>>> Mesos version 0.21.1, Marathon version 0.7.6. >>>>>>> App config; >>>>>>> { >>>>>>> "id":"/progressed-io", >>>>>>> "cmd":"sudo docker run fehmicansaglam/progressed.io >>>>>>> <http://progressed.io/>", >>>>>>> "args":null, >>>>>>> "user":null, >>>>>>> "env":{ >>>>>>> >>>>>>> }, >>>>>>> "instances":5, >>>>>>> "cpus":0.1, >>>>>>> "mem":128.0, >>>>>>> "disk":512.0, >>>>>>> "executor":"", >>>>>>> "constraints":[ >>>>>>> >>>>>>> ], >>>>>>> "uris":[ >>>>>>> >>>>>>> ], >>>>>>> "storeUrls":[ >>>>>>> >>>>>>> ], >>>>>>> "ports":[ >>>>>>> >>>>>>> ], >>>>>>> "requirePorts":false, >>>>>>> "backoffSeconds":1, >>>>>>> "backoffFactor":1.15, >>>>>>> "container":null, >>>>>>> "healthChecks":[ >>>>>>> >>>>>>> ], >>>>>>> "dependencies":[ >>>>>>> >>>>>>> ], >>>>>>> "upgradeStrategy":{ >>>>>>> "minimumHealthCapacity":1.0 >>>>>>> } >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Emre >>>>>>> >>>>>>> 2015-02-09 14:52 GMT+02:00 Dario Rexin <[email protected] >>>>>>> <mailto:[email protected]>>: >>>>>>> Hi Emre, >>>>>>> >>>>>>> what are the versions of Mesos and Marathon and what does your app >>>>>>> definition look like? >>>>>>> >>>>>>> Cheers, >>>>>>> Dario >>>>>>> >>>>>>> > On 09 Feb 2015, at 13:50, Emre Tekelioğlu <[email protected] >>>>>>> > <mailto:[email protected]>> wrote: >>>>>>> > >>>>>>> > Hi, >>>>>>> > I have a single node mesos cluster on Ubuntu 14.04 host machine, with >>>>>>> > one node mesos-master and one node mesos-slave. >>>>>>> > I try to deploy and run my dockerized services with marathon but i >>>>>>> > have a weird problem. >>>>>>> > >>>>>>> > For example If i start a new app with 5 instance, only one task start >>>>>>> > and the status stuck in "deploying". If i restart the mesos-master, >>>>>>> > then the second task start to run. >>>>>>> > >>>>>>> > Each restart for mesos-master cause an increment of a task. >>>>>>> > >>>>>>> > Any idea? >>>>>>> > >>>>>>> > Regards, >>>>>>> > Emre >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >
