RE: Mesos Slave not registering or getting activated

[suruchi.kumari]

Hi,
 I have set zookeeper quorum size=2 as there are 3 master nodes and even 
checked the slave zk configuration.as per this 
https://www.digitalocean.com/community/tutorials/how-to-configure-a-production-ready-mesosphere-cluster-on-ubuntu-14-04
We need to configure only vi /etc/mesos/zk file in slave configuration for 
zookeeper.


From: Pradeep Chhetri [mailto:pradeep.chhetr...@gmail.com]
Sent: 20 May 2016 11:40
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

Slave logs clearly says that its unable to connect to zookeeper. Definitely 
something is wrong in zk quorum or slave zk configuration.

On Fri, May 20, 2016 at 11:42 AM, 
> wrote:
Hi,
Here are the logs:
Master logs :

0520 05:20:48.026689  1905 master.cpp:1457] Recovery failed: Failed to recover 
registrar: Failed to perform fetch within 1mins
F0520 05:23:05.026454  2097 log.cpp:396] Failed to participate in ZooKeeper 
group: Failed to create ephemeral node at '/mesos/log_replicas' in ZooKeeper: 
no node
W0520 05:23:05.256734  2115 authenticator.cpp:511] No credentials provided, 
authentication requests will be refused

I0520 05:25:22.299355  2192 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0520 05:25:22.299422  2192 master.cpp:1710] The newly elected leader is 
master@:5050 with id ddf2064c-9887-4f64-875d-2ed3e318310b
I0520 05:25:22.300588  2193 network.hpp:413] ZooKeeper group memberships changed
I0520 05:25:22.300668  2193 group.cpp:700] Trying to get 
'/mesos/log_replicas/38' in ZooKeeper
I0520 05:25:22.307706  2193 group.cpp:700] Trying to get 
'/mesos/log_replicas/39' in ZooKeeper
I0520 05:25:22.308213  2193 group.cpp:700] Trying to get 
'/mesos/log_replicas/40' in ZooKeeper
I0520 05:25:22.309149  2193 network.hpp:461] ZooKeeper group PIDs: { 
log-replica(1)@:5050, log-replica(1)@:5050 }
I0520 05:25:30.009531  2193 detector.cpp:154] Detected a new leader: (id='40')
I0520 05:25:30.009729  2193 group.cpp:700] Trying to get 
'/mesos/json.info_40' in ZooKeeper
I0520 05:25:30.010063  2190 network.hpp:413] ZooKeeper group memberships changed
I0520 05:25:30.012197  2190 group.cpp:700] Trying to get 
'/mesos/log_replicas/39' in ZooKeeper
I0520 05:25:30.012583  2193 detector.cpp:479] A new leading master 
(UPID=master@:5050) is detected
I0520 05:25:30.012662  2193 master.cpp:1710] The newly elected leader is 
master@with id 1ef713ee-313d-440c-b76e-2772cb6056c7
I0520 05:25:30.012990  2190 group.cpp:700] Trying to get 
'/mesos/log_replicas/40' in ZooKeeper
I0520 05:25:30.013538  2190 network.hpp:461] ZooKeeper group PIDs: { 
log-replica(1)@:5050, log-replica(1)@:5050 }


Slave logs:
E0519 06:33:03.076380  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
W0519 10:33:20.348443  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:33:30.354156  1413 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:33:40.358856  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
E0520 05:28:46.157860  1622 process.cpp:1966] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0520 05:33:18.412081  1622 process.cpp:1966] Failed to shutdown socket with fd 
10: Transport end W0520 05:33:18.108160  1616 slave.cpp:3484] Master 
disconnected! Waiting for a new master to be elected
E0520 05:33:18.412081  1622 process.cpp:1966] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
W0520 05:34:26.118638  1620 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be electedpoint is not connected


From: Pradeep Chhetri 
[mailto:pradeep.chhetr...@gmail.com]
Sent: 20 May 2016 08:58
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

I am assuming that now you have pointed mesos slaves to this new zk quorum. Can 
you please post the logs of mesos slave when you are restarting it.

On Fri, May 20, 2016 at 8:41 AM, 
> wrote:
M running zk quorum .

And now I have recreated all master nodes and then trying  but isn’t getting 
registered.

From: Pradeep Chhetri 
[mailto:pradeep.chhetr...@gmail.com]
Sent: 19 May 2016 23:40

To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

Are you running zk quorum or just a standalone instance ?

My guess is that you were running single zk node & your slaves are still 
pointing to the zookeeper instance on the mesos master which you have replaced.

On Thu, May 19, 2016 at 4:53 PM, 

RE: Mesos Slave not registering or getting activated

[suruchi.kumari]

Hi,
Here are the logs:
Master logs :

0520 05:20:48.026689  1905 master.cpp:1457] Recovery failed: Failed to recover 
registrar: Failed to perform fetch within 1mins
F0520 05:23:05.026454  2097 log.cpp:396] Failed to participate in ZooKeeper 
group: Failed to create ephemeral node at '/mesos/log_replicas' in ZooKeeper: 
no node
W0520 05:23:05.256734  2115 authenticator.cpp:511] No credentials provided, 
authentication requests will be refused

I0520 05:25:22.299355  2192 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0520 05:25:22.299422  2192 master.cpp:1710] The newly elected leader is 
master@:5050 with id ddf2064c-9887-4f64-875d-2ed3e318310b
I0520 05:25:22.300588  2193 network.hpp:413] ZooKeeper group memberships changed
I0520 05:25:22.300668  2193 group.cpp:700] Trying to get 
'/mesos/log_replicas/38' in ZooKeeper
I0520 05:25:22.307706  2193 group.cpp:700] Trying to get 
'/mesos/log_replicas/39' in ZooKeeper
I0520 05:25:22.308213  2193 group.cpp:700] Trying to get 
'/mesos/log_replicas/40' in ZooKeeper
I0520 05:25:22.309149  2193 network.hpp:461] ZooKeeper group PIDs: { 
log-replica(1)@:5050, log-replica(1)@:5050 }
I0520 05:25:30.009531  2193 detector.cpp:154] Detected a new leader: (id='40')
I0520 05:25:30.009729  2193 group.cpp:700] Trying to get 
'/mesos/json.info_40' in ZooKeeper
I0520 05:25:30.010063  2190 network.hpp:413] ZooKeeper group memberships changed
I0520 05:25:30.012197  2190 group.cpp:700] Trying to get 
'/mesos/log_replicas/39' in ZooKeeper
I0520 05:25:30.012583  2193 detector.cpp:479] A new leading master 
(UPID=master@:5050) is detected
I0520 05:25:30.012662  2193 master.cpp:1710] The newly elected leader is 
master@with id 1ef713ee-313d-440c-b76e-2772cb6056c7
I0520 05:25:30.012990  2190 group.cpp:700] Trying to get 
'/mesos/log_replicas/40' in ZooKeeper
I0520 05:25:30.013538  2190 network.hpp:461] ZooKeeper group PIDs: { 
log-replica(1)@:5050, log-replica(1)@:5050 }


Slave logs:
E0519 06:33:03.076380  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
W0519 10:33:20.348443  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:33:30.354156  1413 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:33:40.358856  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
E0520 05:28:46.157860  1622 process.cpp:1966] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0520 05:33:18.412081  1622 process.cpp:1966] Failed to shutdown socket with fd 
10: Transport end W0520 05:33:18.108160  1616 slave.cpp:3484] Master 
disconnected! Waiting for a new master to be elected
E0520 05:33:18.412081  1622 process.cpp:1966] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
W0520 05:34:26.118638  1620 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be electedpoint is not connected


From: Pradeep Chhetri [mailto:pradeep.chhetr...@gmail.com]
Sent: 20 May 2016 08:58
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

I am assuming that now you have pointed mesos slaves to this new zk quorum. Can 
you please post the logs of mesos slave when you are restarting it.

On Fri, May 20, 2016 at 8:41 AM, 
> wrote:
M running zk quorum .

And now I have recreated all master nodes and then trying  but isn’t getting 
registered.

From: Pradeep Chhetri 
[mailto:pradeep.chhetr...@gmail.com]
Sent: 19 May 2016 23:40

To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

Are you running zk quorum or just a standalone instance ?

My guess is that you were running single zk node & your slaves are still 
pointing to the zookeeper instance on the mesos master which you have replaced.

On Thu, May 19, 2016 at 4:53 PM, 
> wrote:
Master logs:-

F0519 10:47:39.203780 28689 master.cpp:1457] Recovery failed: Failed to recover 
registrar: Failed to perform fetch within 1mins

W0519 10:47:39.370132 28719 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected
W0519 10:48:47.387729 28722 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected

I0519 10:48:55.191784 28723 detector.cpp:154] Detected a new leader: (id='183')
I0519 10:48:55.191987 28723 group.cpp:700] Trying to get 
'/mesos/json.info_000183' in ZooKeeper
I0519 10:48:55.193650 28723 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0519 10:48:55.193745 28723 slave.cpp:795] New master detected at master@
I0519 10:48:55.193918 28723 slave.cpp:820] No credentials provided. 

RE: Mesos Slave not registering or getting activated

[suruchi.kumari]

M running zk quorum .

And now I have recreated all master nodes and then trying  but isn’t getting 
registered.

From: Pradeep Chhetri [mailto:pradeep.chhetr...@gmail.com]
Sent: 19 May 2016 23:40
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

Are you running zk quorum or just a standalone instance ?

My guess is that you were running single zk node & your slaves are still 
pointing to the zookeeper instance on the mesos master which you have replaced.

On Thu, May 19, 2016 at 4:53 PM, 
> wrote:
Master logs:-

F0519 10:47:39.203780 28689 master.cpp:1457] Recovery failed: Failed to recover 
registrar: Failed to perform fetch within 1mins

W0519 10:47:39.370132 28719 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected
W0519 10:48:47.387729 28722 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected

I0519 10:48:55.191784 28723 detector.cpp:154] Detected a new leader: (id='183')
I0519 10:48:55.191987 28723 group.cpp:700] Trying to get 
'/mesos/json.info_000183' in ZooKeeper
I0519 10:48:55.193650 28723 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0519 10:48:55.193745 28723 slave.cpp:795] New master detected at master@
I0519 10:48:55.193918 28723 slave.cpp:820] No credentials provided. Attempting 
to register without authentication
I0519 10:48:55.193949 28723 slave.cpp:831] Detecting new master
I0519 10:48:55.194022 28723 status_update_manager.cpp:174] Pausing sending 
status updates
I0519 10:49:29.887965 28725 slave.cpp:4304] Current disk usage 9.13%. Max 
allowed age: 5.661099880651967days
I0519 10:49:55.378037 28725 slave.cpp:3481] master@exited
W0519 10:49:55.378182 28725 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected
I0519 10:50:03.213912 28723 detector.cpp:154] Detected a new leader: (id='184')
I0519 10:50:03.214061 28723 group.cpp:700] Trying to get 
'/mesos/json.info_000184' in ZooKeeper
I0519 10:50:03.215296 28723 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0519 10:50:03.215395 28723 slave.cpp:795] New master detected at master@
I0519 10:50:03.215601 28723 slave.cpp:820] No credentials provided. Attempting 
to register without authentication
I0519 10:50:03.215631 28723 slave.cpp:831] Detecting new master
I0519 10:50:03.215670 28723 status_update_manager.cpp:174] Pausing sending 
status updates
I0519 10:50:29.893625 28720 slave.cpp:4304] Current disk usage 9.13%. Max 
allowed






From: Abhishek Amralkar 
[mailto:abhishek.amral...@talentica.com]
Sent: 19 May 2016 16:23

To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

How about masters logs?
On 19-May-2016, at 4:20 PM, 
suruchi.kum...@accenture.com wrote:



From: Kumari, Suruchi
Sent: 19 May 2016 16:14
To: 'abhishek.amral...@talentica.com' 
>
Subject: RE: Mesos Slave not registering or getting activated

Hi ,

Theses are the slave logs:

E0519 05:31:52.802345  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:53.122215  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:54.422402  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:54.546566  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:43:34.321432  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 06:00:44.652227  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 06:33:03.076380  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected

W0519 10:27:40.170183  1413 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:27:50.175251  1415 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:00.191156  1411 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:10.207135  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:20.214915  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:30.222079  1415 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:40.227010  1414 group.cpp:503] Timed out waiting to connect to 

Marathon error

[suruchi.kumari]

Hi,

Marathon service is running.
But I don't know why it's not showing up in Mesos GUI 's frameworks.


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

RE: Mesos Slave not registering or getting activated

[suruchi.kumari]

Master logs:-

F0519 10:47:39.203780 28689 master.cpp:1457] Recovery failed: Failed to recover 
registrar: Failed to perform fetch within 1mins

W0519 10:47:39.370132 28719 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected
W0519 10:48:47.387729 28722 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected

I0519 10:48:55.191784 28723 detector.cpp:154] Detected a new leader: (id='183')
I0519 10:48:55.191987 28723 group.cpp:700] Trying to get 
'/mesos/json.info_000183' in ZooKeeper
I0519 10:48:55.193650 28723 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0519 10:48:55.193745 28723 slave.cpp:795] New master detected at master@
I0519 10:48:55.193918 28723 slave.cpp:820] No credentials provided. Attempting 
to register without authentication
I0519 10:48:55.193949 28723 slave.cpp:831] Detecting new master
I0519 10:48:55.194022 28723 status_update_manager.cpp:174] Pausing sending 
status updates
I0519 10:49:29.887965 28725 slave.cpp:4304] Current disk usage 9.13%. Max 
allowed age: 5.661099880651967days
I0519 10:49:55.378037 28725 slave.cpp:3481] master@exited
W0519 10:49:55.378182 28725 slave.cpp:3484] Master disconnected! Waiting for a 
new master to be elected
I0519 10:50:03.213912 28723 detector.cpp:154] Detected a new leader: (id='184')
I0519 10:50:03.214061 28723 group.cpp:700] Trying to get 
'/mesos/json.info_000184' in ZooKeeper
I0519 10:50:03.215296 28723 detector.cpp:479] A new leading master 
(UPID=master@) is detected
I0519 10:50:03.215395 28723 slave.cpp:795] New master detected at master@
I0519 10:50:03.215601 28723 slave.cpp:820] No credentials provided. Attempting 
to register without authentication
I0519 10:50:03.215631 28723 slave.cpp:831] Detecting new master
I0519 10:50:03.215670 28723 status_update_manager.cpp:174] Pausing sending 
status updates
I0519 10:50:29.893625 28720 slave.cpp:4304] Current disk usage 9.13%. Max 
allowed






From: Abhishek Amralkar [mailto:abhishek.amral...@talentica.com]
Sent: 19 May 2016 16:23
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

How about masters logs?
On 19-May-2016, at 4:20 PM, 
suruchi.kum...@accenture.com wrote:



From: Kumari, Suruchi
Sent: 19 May 2016 16:14
To: 'abhishek.amral...@talentica.com' 
>
Subject: RE: Mesos Slave not registering or getting activated

Hi ,

Theses are the slave logs:

E0519 05:31:52.802345  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:53.122215  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:54.422402  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:54.546566  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:43:34.321432  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 06:00:44.652227  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 06:33:03.076380  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected

W0519 10:27:40.170183  1413 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:27:50.175251  1415 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:00.191156  1411 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:10.207135  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:20.214915  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:30.222079  1415 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:40.227010  1414 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:50.230976  1418 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:29:00.234498  1417 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:29:10.238258  1416 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration



From: Abhishek Amralkar [mailto:abhishek.amral...@talentica.com]
Sent: 19 May 2016 15:40
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

FW: Mesos Slave not registering or getting activated

[suruchi.kumari]

From: Kumari, Suruchi
Sent: 19 May 2016 16:14
To: 'abhishek.amral...@talentica.com' 
Subject: RE: Mesos Slave not registering or getting activated

Hi ,

Theses are the slave logs:

E0519 05:31:52.802345  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:53.122215  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:54.422402  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:31:54.546566  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 05:43:34.321432  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 06:00:44.652227  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected
E0519 06:33:03.076380  1416 process.cpp:1958] Failed to shutdown socket with fd 
10: Transport endpoint is not connected

W0519 10:27:40.170183  1413 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:27:50.175251  1415 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:00.191156  1411 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:10.207135  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:20.214915  1412 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:30.222079  1415 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:40.227010  1414 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:28:50.230976  1418 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:29:00.234498  1417 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration
W0519 10:29:10.238258  1416 group.cpp:503] Timed out waiting to connect to 
ZooKeeper. Forcing ZooKeeper session (sessionId=0) expiration



From: Abhishek Amralkar [mailto:abhishek.amral...@talentica.com]
Sent: 19 May 2016 15:40
To: user@mesos.apache.org
Subject: Re: Mesos Slave not registering or getting activated

What logs are saying? Any error?

-Abhishek
On 19-May-2016, at 3:35 PM, 
suruchi.kum...@accenture.com wrote:


Hi,

Previously I had a setup of 3 mesos-masters and 2 slave node but one of the 
master node stopped working. So I replaced that with new mesos-master. And now 
the slaves are not registering themselves. Slaves are not getting registered.


Can I know why is this happening. And is there any solution to this.


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

FW: Mesos Slave not registering or getting activated

[suruchi.kumari]

Hi,

Previously I had a setup of 3 mesos-masters and 2 slave node but one of the 
master node stopped working. So I replaced that with new mesos-master. And now 
the slaves are not registering themselves. Slaves are not getting registered.


Can I know why is this happening. And is there any solution to this.


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

Deploying MySQL and WordPress Docker Containers through Marathon

[suruchi.kumari]

Hi ,

In case we are killing one of the instances running through Marathon UI. It is 
able to bring up another replacing it.

So, would like to know is it a replication of the previous instance which was 
killed or it's a new one.

For example, if we are running a MySQL application through Marathon UI  and try 
on of its instance to kill. Will the information saved in the database will be 
remain in the new one replacing it.


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

Deploying MySQL and WordPress Docker Containers through Marathon

[suruchi.kumari]

Hi ,

In case we are killing one the instances running through Marathon UI. It is 
able to bring up another replacing it.

So, would like to know is it a replication of the previous instance which was 
killed or it's a new one.

For example, if we are running a MySQL application through Marathon UI  and try 
on of its instance to kill. Will the information saved in the database will be 
remain in the new one replacing it.


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

Mesos UI sandbox error

[suruchi.kumari]

Hi,
I get this error when I click the sandbox in the Mesos UI.

Failed to connect to slave '997ada1d-87fd-4d20-8035-cb90e191ee9f-S1' on 
'host:5051'.
Potential reasons:
* The slave's hostname, 'host, is not accessible from your network
* The slave's port, '5051', is not accessible from your network
* The slave timed out or went offline

Can I know why the sandbox is throwing this error.




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

RE: Marathon scaling application

[suruchi.kumari]

Hi,

I get this error when I click the sandbox in the Mesos UI.

Failed to connect to slave '997ada1d-87fd-4d20-8035-cb90e191ee9f-S1' on 
'host:5051'.
Potential reasons:
*The slave's hostname, 'host, is not accessible from your network
*The slave's port, '5051', is not accessible from your network
*The slave timed out or went offline

Can I know why the sandbox is throwing this error.


-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
> 

RE: Marathon deploying MySQL and Wordpress application

[suruchi.kumari]

Hi,

I would like to know that can we deploy MySQL and WordPress together through 
Marathon UI (using the command option of Marathon UI).

Can I place both commands and environment variables of MySQL and WordPress 
together in the white space of the command option provided  in the Marathon UI.

-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 

RE: Marathon MySQL and Wordpress Deployment

[suruchi.kumari]

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
> 

RE: Marathon scaling application

[suruchi.kumari]

Hi,

Thank you ..it worked :)

-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
> terminal task, destroying container: Failed to 'docker -H
> 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 

RE: Marathon scaling application

[suruchi.kumari]

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 terminal task, 
destroying container: Failed to 'docker -H 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 inspect