RE: ssl mesos-executor not using /etc/default/mesos

2019-02-19 Thread Marc Roos 
 
Hi James, with your info on that the excutor runs inside the container, 
I need to provision the container environment with the certificate and 
key I guess before it starts the ssl connection. How can I do this?



-Original Message-
Sent: 18 February 2019 18:49
To: user
Subject: Re: ssl mesos-executor not using /etc/default/mesos


> On Feb 16, 2019, at 9:46 AM, Marc Roos  
wrote:
> 
> 
> 
> Looks like the mesos-executor is not using /etc/default/mesos 
> environment variables

Depending on your configuration, the executor runs inside the container, 
which means that /etc/default/mesos is probably not available. 

> 
> If I export the variables in /etc/default/mesos manually, I can run 
> the task.
> 
> mesos-execute --master=x.x.x.x:5050 --principal=xxx --secret=xxx 
> --name=ls --command="ls -lRrt /*; sleep 60" 
> --env=file:///test/env.json
> 
> How should this be resolved? I tried setting 
> --executor_environment_variables=/etc/mesos/executor-env.json

And what happened when you did this?

RE: ssl mesos-executor not using /etc/default/mesos

2019-02-18 Thread Marc Roos 
 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xe8 zxid:0x1d24 txntype:-1 reqpath:n/a Error 
Path:/marathon/state/deployment/a/aeeb05b3-f6d9-44e4-a012-4af35ebb5554 
Error:KeeperErrorCode = NoNode for 
/marathon/state/deployment/a/aeeb05b3-f6d9-44e4-a012-4af35ebb5554
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,412 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xe8 zxid:0x1d24 txntype:-1 reqpath:n/a Error 
Path:/marathon/state/deployment/a/aeeb05b3-f6d9-44e4-a012-4af35ebb5554 
Error:KeeperErrorCode = NoNode for 
/marathon/state/deployment/a/aeeb05b3-f6d9-44e4-a012-4af35ebb5554
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,501 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xec zxid:0x1d28 txntype:-1 reqpath:n/a Error 
Path:/marathon/state/instance/9/server.marathon-eb87000e-33b9-11e9-8454-
0050563001a1 Error:KeeperErrorCode = NoNode for 
/marathon/state/instance/9/server.marathon-eb87000e-33b9-11e9-8454-00505
63001a1
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,501 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xec zxid:0x1d28 txntype:-1 reqpath:n/a Error 
Path:/marathon/state/instance/9/server.marathon-eb87000e-33b9-11e9-8454-
0050563001a1 Error:KeeperErrorCode = NoNode for 
/marathon/state/instance/9/server.marathon-eb87000e-33b9-11e9-8454-00505
63001a1
Feb 18 21:15:22 m01 mesos-slave[27381]: W0218 21:15:22.741439 27416 
containerizer.cpp:2266] Ignoring update for unknown container 
3b5f3dfd-b47c-4ec8-a425-25c3e653029c
Feb 18 21:15:22 m01 mesos-slave[27381]: W0218 21:15:22.741439 27416 
containerizer.cpp:2266] Ignoring update for unknown container 
3b5f3dfd-b47c-4ec8-a425-25c3e653029c
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,761 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xf2 zxid:0x1d2d txntype:-1 reqpath:n/a Error 
Path:/marathon/state/taskFailures/d/server Error:KeeperErrorCode = 
NoNode for /marathon/state/taskFailures/d/server
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,761 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xf3 zxid:0x1d2e txntype:-1 reqpath:n/a Error 
Path:/marathon/state/taskFailures/d/server/2019-02-18T20:15:22.112Z 
Error:KeeperErrorCode = NoNode for 
/marathon/state/taskFailures/d/server/2019-02-18T20:15:22.112Z
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,761 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xf2 zxid:0x1d2d txntype:-1 reqpath:n/a Error 
Path:/marathon/state/taskFailures/d/server Error:KeeperErrorCode = 
NoNode for /marathon/state/taskFailures/d/server
Feb 18 21:15:22 m01 zookeeper: 2019-02-18 21:15:22,761 [myid:] - INFO  
[ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got 
user-level KeeperException when processing sessionid:0x169021324e4002a 
type:setData cxid:0xf3 zxid:0x1d2e txntype:-1 reqpath:n/a Error 
Path:/marathon/state/taskFailures/d/server/2019-02-18T20:15:22.112Z 
Error:KeeperErrorCode = NoNode for 
/marathon/state/taskFailures/d/server/2019-02-18T20:15:22.112Z
Feb 18 21:15:22 m01 marathon: [2019-02-18 21:15:22,760] WARN  New 
instance [instance 
[server.marathon-eb87000e-33b9-11e9-8454-0050563001a1]] failed during 
app /server scaling, queueing another instance 
(mesosphere.marathon.core.deployment.impl.TaskStartActor:marathon-akka.a
ctor.default-dispatcher-12)
Feb 18 21:15:22 m01 marathon: [2019-02-18 21:15:22,760] WARN  New 
instance [instance 
[server.marathon-eb87000e-33b9-11e9-8454-0050563001a1]] failed during 
app /server scaling, queueing another instance 
(mesosphere.marathon.core.deployment.impl.TaskStartActor:marathon-akka.a
ctor.default-dispatcher-12)




-Original Message-
Sent: 18 February 2019 18:49
To: user
Subject: Re: ssl mesos-executor not using /etc/default/mesos



> On Feb 16, 2019, at 9:46 AM, Marc Roos  
wrote:
> 
> 
> 
> Looks like the mesos-executor is not using /etc/default/mesos 
> environment variables

Depending on your configuration, the executor runs inside the container, 
which means that /etc/default/mesos is probably not available. 

> 
> If I export the variables in /etc/default/mesos manually, I can run 
> the task.
> 
> mesos-execute --master=x.x.x.x:5050 --principal=xxx --secret=xxx 
> --name=ls --command="ls -lRrt /*; sleep 60" 
> --env=file:///test/env.json
> 
> How should this be resolved? I tried setting 
> --executor_environment_variables=/etc/mesos/executor-env.json

And what happened when you did this?

Re: ssl mesos-executor not using /etc/default/mesos

2019-02-18 Thread James Peach 



> On Feb 16, 2019, at 9:46 AM, Marc Roos  wrote:
> 
> 
> 
> Looks like the mesos-executor is not using /etc/default/mesos 
> environment variables

Depending on your configuration, the executor runs inside the container, which 
means that /etc/default/mesos is probably not available. 

> 
> If I export the variables in /etc/default/mesos manually, I can run the 
> task. 
> 
> mesos-execute --master=x.x.x.x:5050 --principal=xxx --secret=xxx 
> --name=ls --command="ls -lRrt /*; sleep 60" --env=file:///test/env.json
> 
> How should this be resolved? I tried setting 
> --executor_environment_variables=/etc/mesos/executor-env.json 

And what happened when you did this?

ssl mesos-executor not using /etc/default/mesos

2019-02-16 Thread Marc Roos 



Looks like the mesos-executor is not using /etc/default/mesos 
environment variables

If I export the variables in /etc/default/mesos manually, I can run the 
task. 

mesos-execute --master=x.x.x.x:5050 --principal=xxx --secret=xxx 
--name=ls --command="ls -lRrt /*; sleep 60" --env=file:///test/env.json

How should this be resolved? I tried setting 
--executor_environment_variables=/etc/mesos/executor-env.json