vide any hints as to what happened. It looks
like Thermos was SIGKILLed.
Has any of you run into this problem before? Do you have an idea what
could cause this behaviour? Do you have any suggestion what information
we could look for to better understand what happens?
Kind Regards,
Matthias
--
vide any hints as to what happened. It looks
like Thermos was SIGKILLed.
Has any of you run into this problem before? Do you have an idea what
could cause this behaviour? Do you have any suggestion what information
we could look for to better understand what happens?
Kind Regards,
Matthias
--
e from the executor after the 2
> second reconnect timeout so it was killed. Have you checked the kernel
> logs during this time frame? Were you changing mesos versions around
> this event? Have you checked thermos' logs?
>
> On Thu, Jan 14, 2016 at 8:10 AM, Matthias Bach
&g
3 matches
Mail list logo