RE: Marathon MySQL and Wordpress Deployment
Hi, Would like to know can we deploy MySQL and Wordpress together through Marathon UI (using command option in Marathon UI). Can we put the commands of both together in the white space with the environment varibles of command option.Is it possible to run that way. -Original Message- From: Stephen Gran [mailto:stephen.g...@piksel.com] Sent: 11 May 2016 15:26 To: user@mesos.apache.org Subject: Re: Marathon scaling application Hi, The logs say that the only enabled containerizer is mesos. Perhaps you need to set that to mesos,docker. Cheers, On 11/05/16 10:48, 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- 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- 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- 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- 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- 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- 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- 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- 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- 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 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 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 > termin
Re: Marathon MySQL and Wordpress Deployment
You may want to elaborate on what exactly you want to do. But yes. Command tasks just run commands. As long the syntax is correct (i.e. can you run it locally?), it will run. On Wed, May 11, 2016 at 10:13 PM, wrote: > Hi, > > Would like to know can we deploy MySQL and Wordpress together through > Marathon UI (using command option in Marathon UI). > > Can we put the commands of both together in the white space with the > environment varibles of command option.Is it possible to run that way. > > > > > -Original Message- > From: Stephen Gran [mailto:stephen.g...@piksel.com] > Sent: 11 May 2016 15:26 > To: user@mesos.apache.org > Subject: Re: Marathon scaling application > > Hi, > > The logs say that the only enabled containerizer is mesos. Perhaps you > need to set that to mesos,docker. > > Cheers, > > On 11/05/16 10:48, 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- 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- 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- 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- 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- 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- 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- 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- 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- 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 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 inspect > > > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.ec4e97ad-236
