Re: Tasks that run docker images consistently fail while downloading

Ahem. Yes. I had meant 300,000 ;) Cheers, Jim On 28 October 2015 at 12:10, Rad Gruchalski wrote: > However, it should be 30, not 3. It’s milliseconds - 5 mins in > milliseconds is 30. > > Optional. Default: 30 (5 minutes) > > Kind regards, > Radek

Re: Tasks that run docker images consistently fail while downloading

Indeed, I have images which take more than a minute to download and I do not see such behaviour. No immediate idea why this would happen. Can you share your application request? Kind regards,
 Radek Gruchalski 
ra...@gruchalski.com (mailto:ra...@gruchalski.com)


Re: Tasks that run docker images consistently fail while downloading

I shall fix my own problem it's embarrassing. Top marks to those of you that notice I supplied 3000 instead of 3 (which I understand is actually the default anyway) to task_launch_timeout! Jim On 28 October 2015 at 10:21, James Vanns wrote: > Hi all. > > Mesos

Re: Tasks that run docker images consistently fail while downloading

However, it should be 30, not 3. It’s milliseconds - 5 mins in milliseconds is 30. Optional. Default: 30 (5 minutes) Kind regards,
 Radek Gruchalski 
ra...@gruchalski.com (mailto:ra...@gruchalski.com)
 (mailto:ra...@gruchalski.com)

Re: Marathon 0.11.1 - Mesos 0.25 - Mesos-DNS 0.4.0

I've had no issue with the following combination: MesosDNS 0.4.0 Marathon 0.11.0 Mesos 0.24.1 I've been waiting to upgrade to Mesos 0.25.0 because of issues mentioned in the mesos mailing list regarding Marathon 0.11.x and Mesos 0.25.0 On Wed, Oct 28, 2015 at 10:38 AM, John Omernik

Marathon 0.11.1 - Mesos 0.25 - Mesos-DNS 0.4.0

Hey all - I am cross posting this because it's a number of moving parts that could be at issue here (Mesos, Mesos-dns, and/or Marathon). Basically: At the version combination in Subject, the IP that is registered in mesos-dns for Docker containers running in Marathon is the internal (container)

Re: Marathon 0.11.1 - Mesos 0.25 - Mesos-DNS 0.4.0

If I rolled back mesos-dns to v0.2.0 (on the releases page) then it pulls the right IP address.. (Mesos-dns version is the easiest of the three to change) John On Wed, Oct 28, 2015 at 9:52 AM, John Omernik wrote: > So, the issues that are listed appear to be resolved with

Re: Marathon 0.11.1 - Mesos 0.25 - Mesos-DNS 0.4.0

I will check out those issues and report back. On Wed, Oct 28, 2015 at 9:42 AM, craig w wrote: > I've had no issue with the following combination: > > MesosDNS 0.4.0 > Marathon 0.11.0 > Mesos 0.24.1 > > I've been waiting to upgrade to Mesos 0.25.0 because of issues

Re: How to tell master which ip to connect.

On Tue, Oct 27, 2015 at 7:43 PM, Xiaodong Zhang wrote: > It works! Thanks a lot. > Ok. So we should expose advertise_ip and advertise_port as command line options for mesos-slave as well (instead of using the environment variables)? Opened

unable to start mesos-slave as non-root user after 0.25 upgrade

After I upgraded the first thing I notice is that permissions on wrapper script # ls -al /usr/bin/mesos-init-wrapper -rwxr-x---. 1 root root 5202 Oct 12 21:08 /usr/bin/mesos-init-wrapper So systemd was unable to EXEC this script So I changed the perms on this wrapper # chmod a+x

Re: Marathon 0.11.1 - Mesos 0.25 - Mesos-DNS 0.4.0

It's not a bug, it's a feature - http://mesosphere.github.io/mesos-dns/docs/configuration-parameters.html look at IPSources config śr., 28.10.2015 o 15:59 użytkownik John Omernik napisał: > If I rolled back mesos-dns to v0.2.0 (on the releases page) then it pulls > the right

Re: Can't start docker container when SSL_ENABLED is on.

Do you compile mesos with ssl support? The default compile don't contains ssl. And does docker container have stdour and stderr? On Thu, Oct 29, 2015 at 11:41 AM, Xiaodong Zhang wrote: > My scenarios is like previous email says, masters and slaves are in > different IaaS. Now

Re: Can't start docker container when SSL_ENABLED is on.

[cid:9D46724C-457C-4BE1-B0E4-F57B147F6DC8] The webui have a LOG link, when click it shows like this: I1029 04:44:32.293445 5697 http.cpp:321] HTTP GET for /master/state.json from 114.113.20.135:55682 with User-Agent='Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML,

Re: Can't start docker container when SSL_ENABLED is on.

Thanks for your reply. Yes I build mesos with `--enable-libevent --enable-ssl`. If I don’t provide key and pem when start slave, it will register fail(That means the ssl work well right?) As I said the odd thing is the container nerver run(`docker ps –a show nothing`). So it can’t have any

Re: Can't start docker container when SSL_ENABLED is on.

Oh, I mean you task logs. They could be get from Mesos webui. On Thu, Oct 29, 2015 at 11:52 AM, Xiaodong Zhang wrote: > Thanks for your reply. > > Yes I build mesos with `--enable-libevent --enable-ssl`. If I don’t > provide key and pem when start slave, it will register

Re: unable to start mesos-slave as non-root user after 0.25 upgrade

The issue was indeed permission problems. I’m using Fedora 22 and mesos-0.25.0-0.2.70.centos701406.x86_64 The following file is set with odd perms -rwxr-x---. 1 root root 5202 Oct 12 21:08 /bin/mesos-init-wrapper I was able to use ansible to fix the perms across my cluster by changing

Re: Can't start docker container when SSL_ENABLED is on.

I didn’t see some useful info. In mesos slave log, there is a line : I1029 03:29:53.160143 9292 slave.cpp:3399] Executor '279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713' of framework 20151029-031549-1294671788-5050-4937- terminated with signal Killed I check

Re: Can't start docker container when SSL_ENABLED is on.

Hi Xiaodong, That's the master log, but if you click on "sandbox" next to the TASK_FAILED task and find the stdout/stderr files, click on them and paste the results here. Tim On Wed, Oct 28, 2015 at 9:59 PM, Xiaodong Zhang wrote: > > The webui have a LOG link, when click it

Re: unable to start mesos-slave as non-root user after 0.25 upgrade

This may be related to the systemd support we added in 0.25. If the agent detects it is running on systemd it will try to launch a systemd slice under which to run the executors. If your non-root user does not have sufficient permissions to perform these operations that will be a problem. Can you

Re: Tasks that run docker images consistently fail while downloading

Yes I have - I mention that in my Email ;) I set it to the same as the ' executor_registration_timeout'. Both effectively set to 5 minutes - but my tasks are killed off after 1 minute without being allowed to fully download the image. Jim On 28 October 2015 at 10:26, Rad Gruchalski