The logs indicate an issue with running docker… I would start by login into the node that you are having issues with and debug the docker issue. I would suspect you can’t run a docker container manually.
ken > On May 11, 2016, at 4:43 AM, <suruchi.kum...@accenture.com> > <suruchi.kum...@accenture.com> wrote: > > Hi, > > 1. I did not launch the marathon job with json file. > 2. version of mesos is 0.27.2 and marathon is 0.15.3 > 3. what OS is on the nodes :Ubuntu 14.04 LTS > 4. Here are the slave logs :- > > E0511 00:41:43.982487 1460 slave.cpp:3800] Termination of executor > 'nginx.226620ca-1711-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed: Unknown container: > a0d72cc7-f02b-44d7-b93a-3b1df6e74414 > E0511 01:41:44.518671 1457 slave.cpp:3729] Container > '20095298-d0c5-4c23-ae0b-a0b9393ecfb4' for executor > 'nginx.847bdd1b-1719-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed to start: None of the > enabled containerizers (mesos) could create a container for the provided > TaskInfo/ExecutorInfo message > E0511 01:41:44.518831 1457 slave.cpp:3800] Termination of executor > 'nginx.847bdd1b-1719-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed: Unknown container: > 20095298-d0c5-4c23-ae0b-a0b9393ecfb4 > E0511 02:41:44.632048 1462 slave.cpp:3729] Container > '944a6719-b942-4a06-8d4a-08e1f624f62e' for executor > 'nginx.e6557acc-1721-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed to start: None of the > enabled containerizers (mesos) could create a container for the provided > TaskInfo/ExecutorInfo message > E0511 02:41:44.632735 1457 slave.cpp:3800] Termination of executor > 'nginx.e6557acc-1721-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed: Unknown container: > 944a6719-b942-4a06-8d4a-08e1f624f62e > E0511 03:41:44.781136 1464 slave.cpp:3729] Container > '2677810f-0f42-45fd-87aa-329a9fbe5af0' for executor > 'nginx.482be42d-172a-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed to start: None of the > enabled containerizers (mesos) could create a container for the provided > TaskInfo/ExecutorInfo message > E0511 03:41:44.782914 1460 slave.cpp:3800] Termination of executor > 'nginx.482be42d-172a-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed: Unknown container: > 2677810f-0f42-45fd-87aa-329a9fbe5af0 > E0511 04:41:44.891082 1463 slave.cpp:3729] Container > 'acefe126-7d69-4525-987c-bafbf1dd1d6f' for executor > 'nginx.aa066c3e-1732-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed to start: None of the > enabled containerizers (mesos) could create a container for the provided > TaskInfo/ExecutorInfo message > E0511 04:41:44.891180 1463 slave.cpp:3800] Termination of executor > 'nginx.aa066c3e-1732-11e6-9f8a-fa163ecc33f1' of framework > a039103f-aab7-4f15-8578-0d52ac8f60e0-0000 failed: Unknown container: > acefe126-7d69-4525-987c-bafbf1dd1d6f > > E0510 10:27:25.997802 1352 process.cpp:1958] Failed to shutdown socket with > fd 10: Transport endpoint is not connected > E0511 05:39:43.651479 1351 slave.cpp:3252] Failed to update resources for > container 53bb3453-31b2-4cf7-a9e1-5f700510eeb4 of executor > 'nginx.38f28ab0-169b-11e6-9f8a-fa163ecc33f1' running task > nginx.38f28ab0-169b-11e6-9f8a-fa163ecc33f1 on status update for terminal > task, destroying container: Failed to 'docker -H unix:///var/run/docker.sock > <unix:///var/run/docker.sock> inspect > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.53bb3453-31b2-4cf7-a9e1-5f700510eeb4': > exit status = exited with status 1 stderr = Cannot connect to the Docker > daemon. Is the docker daemon running on this host? > E0511 05:39:43.651845 1351 slave.cpp:3252] Failed to update resources for > container ec4e97ad-2365-4c29-9ed7-64cd9261c666 of executor > 'nginx.38f48682-169b-11e6-9f8a-fa163ecc33f1' running task > nginx.38f48682-169b-11e6-9f8a-fa163ecc33f1 on status update for terminal > task, destroying container: Failed to 'docker -H unix:///var/run/docker.sock > <unix:///var/run/docker.sock> inspect > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.ec4e97ad-2365-4c29-9ed7-64cd9261c666': > exit status = exited with status 1 stderr = Cannot connect to the Docker > daemon. Is the docker daemon running on this host? > E0511 05:39:43.651983 1351 slave.cpp:3252] Failed to update resources for > container 116be528-b81f-4e4c-b2a4-11bb10707031 of executor > 'nginx.413b3558-169b-11e6-9f8a-fa163ecc33f1' running task > nginx.413b3558-169b-11e6-9f8a-fa163ecc33f1 on status update for terminal > task, destroying container: Failed to 'docker -H unix:///var/run/docker.sock > <unix:///var/run/docker.sock> inspect > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.116be528-b81f-4e4c-b2a4-11bb10707031': > exit status = exited with status 1 stderr = Cannot connect to the Docker > daemon. Is the docker daemon running on this host? > E0511 05:39:43.652032 1351 slave.cpp:3252] Failed to update resources for > container f77a5a14-4eb0-4801-a520-6fd2b298a3e3 of executor > 'nginx.47bcdb9a-169b-11e6-9f8a-fa163ecc33f1' running task > nginx.47bcdb9a-169b-11e6-9f8a-fa163ecc33f1 on status update for terminal > task, destroying container: Failed to 'docker -H unix:///var/run/docker.sock > <unix:///var/run/docker.sock> inspect > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.f77a5a14-4eb0-4801-a520-6fd2b298a3e3': > exit status = exited with status 1 stderr = Cannot connect to the Docker > daemon. Is the docker daemon running on this host? > E0511 05:39:43.652118 1351 slave.cpp:3252] Failed to update resources for > container 537100e5-99de-4b59-903a-127dae29839e of executor > 'nginx.47bf4c9b-169b-11e6-9f8a-fa163ecc33f1' running task > nginx.47bf4c9b-169b-11e6-9f8a-fa163ecc33f1 on status update for terminal > task, destroying container: Failed to 'docker -H unix:///var/run/docker.sock > <unix:///var/run/docker.sock> inspect > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.537100e5-99de-4b59-903a-127dae29839e': > exit status = exited with status 1 stderr = Cannot connect to the Docker > daemon. Is the docker daemon running on this host? > E0511 05:39:43.679261 1352 process.cpp:1958] Failed to shutdown socket with > fd 18: Transport endpoint is not connected > E0511 05:39:43.780983 1352 process.cpp:1958] Failed to shutdown socket with > fd 14: Transport endpoint is not connected > > > > > From: Ken Sipe [mailto:kens...@gmail.com <mailto:kens...@gmail.com>] > Sent: 11 May 2016 13:50 > To: user@mesos.apache.org <mailto:user@mesos.apache.org> > Subject: Re: Marathon scaling application > > It is hard to say with the information provided. I would check the slave > log the failure node. I suspect the failure is recorded there. > > otherwise more information is necessary: > 1. the marathon job (did you launch with a json file? that would be helpful) > 2. the slave logs > > it could also be useful to understand: > 1. the version of mesos and marathon > 2. what OS is on the nodes > > ken > > On May 11, 2016, at 3:10 AM, suruchi.kum...@accenture.com > <mailto:suruchi.kum...@accenture.com> wrote: > > I have problem scaling the applications through Marathon. > > I have a setup of two slave nodes.The first slave node having CPU=1 and > RAM=2GB and the Second node having CPU=4 and RAM=8GB. > > It is able to scale maximum 5 instances on the first node but when I tried > scaling it further the host gets changed to the second slave node.And the > task fails to start and error in the debug section of the Marathon UI shows > "Abnormal executor termination". > > I would like to know why is it not getting scheduled on the other slave > node??? > > Can you please help me with this issue. > > Thanks > > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise confidential information. If you have received it > in error, please notify the sender immediately and delete the original. Any > other use of the e-mail by you is prohibited. Where allowed by local law, > electronic communications with Accenture and its affiliates, including e-mail > and instant messaging (including content), may be scanned by our systems for > the purposes of information security and assessment of internal compliance > with Accenture policy. > ______________________________________________________________________________________ > > www.accenture.com <http://www.accenture.com/>
