[jira] [Commented] (MESOS-2025) Process reparent assumes new parent is init pid 1
[ https://issues.apache.org/jira/browse/MESOS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192934#comment-14192934 ] Joris Van Remoortere commented on MESOS-2025: - https://reviews.apache.org/r/27461/ > Process reparent assumes new parent is init pid 1 > - > > Key: MESOS-2025 > URL: https://issues.apache.org/jira/browse/MESOS-2025 > Project: Mesos > Issue Type: Bug > Components: stout > Environment: Ubuntu 14.04 with graphical interface >Reporter: Joris Van Remoortere >Assignee: Joris Van Remoortere >Priority: Minor > > Reparenting does not always assign pid 1 (/sbin/init). If there is a user > init such as init --user with some other pid, this will be the new parent. > Modify os_tests to check up the parent tree, and succeed if there is a path > to pid 1 without zombies along the way. > This is not the cleanest fix, but I'm having trouble finding a way to find > the appropriate init to check for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2025) Process reparent assumes new parent is init pid 1
Joris Van Remoortere created MESOS-2025: --- Summary: Process reparent assumes new parent is init pid 1 Key: MESOS-2025 URL: https://issues.apache.org/jira/browse/MESOS-2025 Project: Mesos Issue Type: Bug Components: stout Environment: Ubuntu 14.04 with graphical interface Reporter: Joris Van Remoortere Assignee: Joris Van Remoortere Priority: Minor Reparenting does not always assign pid 1 (/sbin/init). If there is a user init such as init --user with some other pid, this will be the new parent. Modify os_tests to check up the parent tree, and succeed if there is a path to pid 1 without zombies along the way. This is not the cleanest fix, but I'm having trouble finding a way to find the appropriate init to check for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1250) ReservationAllocatorTest.ResourcesReturned flaky - repeated_field.h:824 CHECK failed: (index) < (size())
[
https://issues.apache.org/jira/browse/MESOS-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192827#comment-14192827
]
Cody Maloney commented on MESOS-1250:
-
Just hit this today accompanied by a segfault on the Mesosphere buildbot.
Definitely doesn't seem to be frequent.
{noformat:title=Check}
[libprotobuf FATAL
../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src/google/protobuf/repeated_field.h:824]
CHECK failed: (index) < (size()):
../../src/tests/allocator_tests.cpp:753: Failure
Actual function call count doesn't match EXPECT_CALL(allocator, slaveAdded(_,
_, _))...
Expected: to be called twice
Actual: called once - unsatisfied and active
unknown file: Failure
C++ exception with description "CHECK failed: (index) < (size()): " thrown in
the test body.
{noformat}
{noformat:title=Log}
[ RUN ] ReservationAllocatorTest.ResourcesReturned
[libprotobuf FATAL
../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src/google/protobuf/repeated_field.h:824]
CHECK failed: (index) < (size()):
../../src/tests/allocator_tests.cpp:753: Failure
Actual function call count doesn't match EXPECT_CALL(allocator, slaveAdded(_,
_, _))...
Expected: to be called twice
Actual: called once - unsatisfied and active
unknown file: Failure
C++ exception with description "CHECK failed: (index) < (size()): " thrown in
the test body.
*** Aborted at 1414800164 (unix time) try "date -d @1414800164" if you are
using GNU date ***
PC: @ 0x2b1ec26c05c8 (unknown)
*** SIGSEGV (@0x0) received by PID 28529 (TID 0x2b1ebd74e100) from PID 0; stack
trace: ***
@ 0x2b1ec2e35340 (unknown)
@ 0x2b1ec26c05c8 (unknown)
@ 0x8fffe3 process::UPID::UPID()
@ 0x902ebe process::ProcessBase::self()
@ 0x90303f process::terminate()
@ 0x90b127
mesos::internal::master::allocator::Allocator::~Allocator()
@ 0x90b1aa
mesos::internal::master::allocator::Allocator::~Allocator()
@ 0xe0fdcc process::Owned<>::Data::~Data()
@ 0xe13dfc std::_Sp_counted_ptr<>::_M_dispose()
@ 0x935a1a std::_Sp_counted_base<>::_M_release()
@ 0x916e5b std::__shared_count<>::~__shared_count()
@ 0x90f8f6 std::__shared_ptr<>::~__shared_ptr()
@ 0x90f910 std::shared_ptr<>::~shared_ptr()
@ 0x90f92a process::Owned<>::~Owned()
@ 0x91010c
mesos::internal::tests::Cluster::Masters::Master::~Master()
@ 0x980eb8 std::pair<>::~pair()
@ 0x980ee2 std::_Rb_tree_node<>::~_Rb_tree_node()
@ 0x980f00 __gnu_cxx::new_allocator<>::destroy<>()
@ 0x9687a1 std::_Rb_tree<>::_M_destroy_node()
@ 0x943d21 std::_Rb_tree<>::_M_erase()
@ 0x92555c std::_Rb_tree<>::~_Rb_tree()
@ 0x90fdea std::map<>::~map()
@ 0x910047 mesos::internal::tests::Cluster::Masters::shutdown()
@ 0xdf3eaa mesos::internal::tests::MesosTest::ShutdownMasters()
@ 0xdf3e73 mesos::internal::tests::MesosTest::Shutdown()
@ 0xdf16ad mesos::internal::tests::MesosTest::TearDown()
@ 0x10d4d04
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x10cfe5a
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x10b81b4 testing::Test::Run()
@ 0x10b888e testing::TestInfo::Run()
@ 0x10b8e16 testing::TestCase::Run()
@ 0x10bdae0 testing::internal::UnitTestImpl::RunAllTests()
make[4]: *** [check-local] Segmentation fault (core dumped)
{noformat}
> ReservationAllocatorTest.ResourcesReturned flaky - repeated_field.h:824 CHECK
> failed: (index) < (size())
>
>
> Key: MESOS-1250
> URL: https://issues.apache.org/jira/browse/MESOS-1250
> Project: Mesos
> Issue Type: Bug
>Reporter: Yan Xu
>
> {noformat:title=The CHECK failure}
> [libprotobuf FATAL
> ../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src/google/protobuf/repeated_field.h:824]
> CHECK failed: (index) < (size()):
> {noformat}
> {noformat:title=Full log}
> [ RUN ] ReservationAllocatorTest.ResourcesReturned
> I0425 18:24:35.375020 23940 leveldb.cpp:174] Opened db in 80.11386ms
> I0425 18:24:35.385205 23940 leveldb.cpp:181] Compacted db in 10.16346ms
> I0425 18:24:35.385226 23940 leveldb.cpp:196] Created db iterator in 3534ns
> I0425 18:24:35.385233 23940 leveldb.cpp:202] Seeked to beginning of db in
> 513ns
> I0425 18:24:35.385239 23940 leveldb.cpp:271] Iterated through 0 keys in the
> db in 200ns
> I0425 18:24:35.385251 23940 replica.cpp:729] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0425 18:24:35.385484 23963 recover.cpp:425]
[jira] [Commented] (MESOS-1981) Create docs/modules.md to record module API changes
[ https://issues.apache.org/jira/browse/MESOS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192728#comment-14192728 ] Kapil Arya commented on MESOS-1981: --- RR: https://reviews.apache.org/r/27453/ > Create docs/modules.md to record module API changes > --- > > Key: MESOS-1981 > URL: https://issues.apache.org/jira/browse/MESOS-1981 > Project: Mesos > Issue Type: Bug >Reporter: Kapil Arya >Assignee: Kapil Arya > > The docs/modules.md file keep a history of all module API changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-2019) Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept.
[ https://issues.apache.org/jira/browse/MESOS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191286#comment-14191286 ] Evelina Dumitrescu edited comment on MESOS-2019 at 10/31/14 8:31 PM: - https://reviews.apache.org/r/27446 https://reviews.apache.org/r/27447 was (Author: evelinad): https://reviews.apache.org/r/27413/ > Rename the Node class in Endpoint and replace the ip and port pairs from the > UPID class and process namespace with this concept. > - > > Key: MESOS-2019 > URL: https://issues.apache.org/jira/browse/MESOS-2019 > Project: Mesos > Issue Type: Improvement > Components: framework >Reporter: Evelina Dumitrescu >Assignee: Evelina Dumitrescu >Priority: Minor > > The Node class abstracts the endpoint notion: it defines the association of > the ip and port for a connection. A node defines more the host(which can have > multiple active endpoints). > At the moment, the Node class is used to keep a mapping from a socket to the > ip & port pair in the process namespace. > I want to propose to rename this class in Endpoint and also extend its use by > replacing the ip & port fields from the UPID class and process namespace > with this type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2017) Segfault with "Pure virtual method called" when tests fail
[
https://issues.apache.org/jira/browse/MESOS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192420#comment-14192420
]
Yan Xu commented on MESOS-2017:
---
[~dhamon] right. So I was looking for recent changes that could potentially
alter the destruction ordering.
Recent such segfaults always follow a failed test and happen to many different
tests and different objects (libprocess Processes). The earliest apache CI
builds that exhibit this symptom I found was:
Oct 13: Enabled whitespace/semicolon rule for cpplint.
Tracing back a few commits I saw this [~jvanremoortere]'s
[commit|https://github.com/apache/mesos/commit/29a82c97c74ff72c2542bf554066ac76daa02664]
that could potentially change the ordering so I was asking but I am not sure
thus far.
I could spend some time after this week to investigate further.
> Segfault with "Pure virtual method called" when tests fail
> --
>
> Key: MESOS-2017
> URL: https://issues.apache.org/jira/browse/MESOS-2017
> Project: Mesos
> Issue Type: Bug
> Components: test
>Affects Versions: 0.21.0
>Reporter: Yan Xu
>
> The most recent one:
> {noformat:title=DRFAllocatorTest.DRFAllocatorProcess}
> [ RUN ] DRFAllocatorTest.DRFAllocatorProcess
> Using temporary directory '/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j'
> I1030 05:55:06.934813 24459 leveldb.cpp:176] Opened db in 3.175202ms
> I1030 05:55:06.935925 24459 leveldb.cpp:183] Compacted db in 1.077924ms
> I1030 05:55:06.935976 24459 leveldb.cpp:198] Created db iterator in 16460ns
> I1030 05:55:06.935995 24459 leveldb.cpp:204] Seeked to beginning of db in
> 2018ns
> I1030 05:55:06.936005 24459 leveldb.cpp:273] Iterated through 0 keys in the
> db in 335ns
> I1030 05:55:06.936039 24459 replica.cpp:741] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1030 05:55:06.936705 24480 recover.cpp:437] Starting replica recovery
> I1030 05:55:06.937023 24480 recover.cpp:463] Replica is in EMPTY status
> I1030 05:55:06.938158 24475 replica.cpp:638] Replica in EMPTY status received
> a broadcasted recover request
> I1030 05:55:06.938859 24482 recover.cpp:188] Received a recover response from
> a replica in EMPTY status
> I1030 05:55:06.939486 24474 recover.cpp:554] Updating replica status to
> STARTING
> I1030 05:55:06.940249 24489 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 591981ns
> I1030 05:55:06.940274 24489 replica.cpp:320] Persisted replica status to
> STARTING
> I1030 05:55:06.940752 24481 recover.cpp:463] Replica is in STARTING status
> I1030 05:55:06.940820 24489 master.cpp:312] Master
> 20141030-055506-3142697795-40429-24459 (pomona.apache.org) started on
> 67.195.81.187:40429
> I1030 05:55:06.940871 24489 master.cpp:358] Master only allowing
> authenticated frameworks to register
> I1030 05:55:06.940891 24489 master.cpp:363] Master only allowing
> authenticated slaves to register
> I1030 05:55:06.940908 24489 credentials.hpp:36] Loading credentials for
> authentication from
> '/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j/credentials'
> I1030 05:55:06.941215 24489 master.cpp:392] Authorization enabled
> I1030 05:55:06.941751 24475 master.cpp:120] No whitelist given. Advertising
> offers for all slaves
> I1030 05:55:06.942227 24474 replica.cpp:638] Replica in STARTING status
> received a broadcasted recover request
> I1030 05:55:06.942401 24476 hierarchical_allocator_process.hpp:299]
> Initializing hierarchical allocator process with master :
> master@67.195.81.187:40429
> I1030 05:55:06.942895 24483 recover.cpp:188] Received a recover response from
> a replica in STARTING status
> I1030 05:55:06.943035 24474 master.cpp:1242] The newly elected leader is
> master@67.195.81.187:40429 with id 20141030-055506-3142697795-40429-24459
> I1030 05:55:06.943063 24474 master.cpp:1255] Elected as the leading master!
> I1030 05:55:06.943079 24474 master.cpp:1073] Recovering from registrar
> I1030 05:55:06.943313 24480 registrar.cpp:313] Recovering registrar
> I1030 05:55:06.943455 24475 recover.cpp:554] Updating replica status to VOTING
> I1030 05:55:06.944144 24474 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 536365ns
> I1030 05:55:06.944172 24474 replica.cpp:320] Persisted replica status to
> VOTING
> I1030 05:55:06.944355 24489 recover.cpp:568] Successfully joined the Paxos
> group
> I1030 05:55:06.944576 24489 recover.cpp:452] Recover process terminated
> I1030 05:55:06.945155 24486 log.cpp:656] Attempting to start the writer
> I1030 05:55:06.947013 24473 replica.cpp:474] Replica received implicit
> promise request with proposal 1
> I1030 05:55:06.947854 24473 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 806463ns
> I1030 05:55:06.947883 24473 replica.cpp:342] Persisted promised to 1
> I1030
[jira] [Commented] (MESOS-2024) mesos debian packaging should work on a java 8 install without java7
[ https://issues.apache.org/jira/browse/MESOS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192288#comment-14192288 ] Steven Schlansker commented on MESOS-2024: -- Hm, this might actually be a Mesosphere issue (Mesos should really take the packaging into the main build!) Maybe this PR addresses the issue? https://github.com/mesosphere/mesos-deb-packaging/pull/24 > mesos debian packaging should work on a java 8 install without java7 > > > Key: MESOS-2024 > URL: https://issues.apache.org/jira/browse/MESOS-2024 > Project: Mesos > Issue Type: Improvement > Components: build >Affects Versions: 0.20.1 >Reporter: Steven Schlansker > > The mesos .deb file: > root@myhost:~# dpkg-query -s mesos > Version: 0.20.1-1.0.ubuntu1404 > Depends: java7-runtime-headless | java6-runtime-headless, libcurl3 > Recommends: zookeeper, zookeeperd, zookeeper-bin > We run java8, but installing the mesos package always drags in java7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2021) Mesos will not execute on ARM CPU based System
[
https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192272#comment-14192272
]
Till Toenshoff commented on MESOS-2021:
---
Thanks for testing and reporting this Axel.
Currently we are actively supporting 64bit x86 CPUs only. However, your input
is super valuable and the more you can report on specific ARM issues, and the
more you can fix them or hint fixes, the better :)
> Mesos will not execute on ARM CPU based System
> --
>
> Key: MESOS-2021
> URL: https://issues.apache.org/jira/browse/MESOS-2021
> Project: Mesos
> Issue Type: Bug
> Components: cli, general
>Affects Versions: 0.20.1
> Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP
> Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree)
> GNU/Linux
>Reporter: Axel Etcheverry
>Priority: Blocker
>
> Configuration : ../configure --disable-java
> {noformat}
> c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
> --work_dir=/var/lib/mesos
> I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
> I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
> F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
> leveldb::BytewiseComparator()->Compare(one, two) < 0
> *** Check failure stack trace: ***
> @ 0xb63db678 google::LogMessage::Fail()
> @ 0xb63dd428 google::LogMessage::SendToLog()
> @ 0xb63db294 google::LogMessage::Flush()
> @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
> @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
> @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
> @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0xb6337ad4 mesos::internal::log::Replica::Replica()
> @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
> @ 0xb62cabc8 mesos::internal::log::Log::Log()
> @0x41818 main
> @ 0xb51965f8 (unknown)
> Aborted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2021) Mesos will not execute on ARM CPU based System
[
https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Toenshoff updated MESOS-2021:
--
Summary: Mesos will not execute on ARM CPU based System (was: Mesos will
not execute)
> Mesos will not execute on ARM CPU based System
> --
>
> Key: MESOS-2021
> URL: https://issues.apache.org/jira/browse/MESOS-2021
> Project: Mesos
> Issue Type: Bug
> Components: cli, general
>Affects Versions: 0.20.1
> Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP
> Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree)
> GNU/Linux
>Reporter: Axel Etcheverry
>Priority: Blocker
>
> Configuration : ../configure --disable-java
> {noformat}
> c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
> --work_dir=/var/lib/mesos
> I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
> I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
> F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
> leveldb::BytewiseComparator()->Compare(one, two) < 0
> *** Check failure stack trace: ***
> @ 0xb63db678 google::LogMessage::Fail()
> @ 0xb63dd428 google::LogMessage::SendToLog()
> @ 0xb63db294 google::LogMessage::Flush()
> @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
> @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
> @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
> @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0xb6337ad4 mesos::internal::log::Replica::Replica()
> @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
> @ 0xb62cabc8 mesos::internal::log::Log::Log()
> @0x41818 main
> @ 0xb51965f8 (unknown)
> Aborted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2024) mesos debian packaging should work on a java 8 install without java7
[ https://issues.apache.org/jira/browse/MESOS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated MESOS-2024: - Summary: mesos debian packaging should work on a java 8 install without java7 (was: mesos debian packaging should work on a java 8 install) > mesos debian packaging should work on a java 8 install without java7 > > > Key: MESOS-2024 > URL: https://issues.apache.org/jira/browse/MESOS-2024 > Project: Mesos > Issue Type: Improvement > Components: build >Affects Versions: 0.20.1 >Reporter: Steven Schlansker > > The mesos .deb file: > root@myhost:~# dpkg-query -s mesos > Version: 0.20.1-1.0.ubuntu1404 > Depends: java7-runtime-headless | java6-runtime-headless, libcurl3 > Recommends: zookeeper, zookeeperd, zookeeper-bin > We run java8, but installing the mesos package always drags in java7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2024) mesos debian packaging should work on a java 8 install
Steven Schlansker created MESOS-2024: Summary: mesos debian packaging should work on a java 8 install Key: MESOS-2024 URL: https://issues.apache.org/jira/browse/MESOS-2024 Project: Mesos Issue Type: Improvement Components: build Affects Versions: 0.20.1 Reporter: Steven Schlansker The mesos .deb file: root@myhost:~# dpkg-query -s mesos Version: 0.20.1-1.0.ubuntu1404 Depends: java7-runtime-headless | java6-runtime-headless, libcurl3 Recommends: zookeeper, zookeeperd, zookeeper-bin We run java8, but installing the mesos package always drags in java7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2023) mesos-execute should allow setting environment variables
Steven Schlansker created MESOS-2023: Summary: mesos-execute should allow setting environment variables Key: MESOS-2023 URL: https://issues.apache.org/jira/browse/MESOS-2023 Project: Mesos Issue Type: Improvement Affects Versions: 0.20.1 Reporter: Steven Schlansker mesos-execute does not allow setting various properties of the 'CommandInfo' protobuf. Most notably, being able to set environment variables and URIs would be very useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2021) Mesos will not execute
[
https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Axel Etcheverry updated MESOS-2021:
---
Description:
Configuration : ../configure --disable-java
{noformat}
c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
--work_dir=/var/lib/mesos
I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
leveldb::BytewiseComparator()->Compare(one, two) < 0
*** Check failure stack trace: ***
@ 0xb63db678 google::LogMessage::Fail()
@ 0xb63dd428 google::LogMessage::SendToLog()
@ 0xb63db294 google::LogMessage::Flush()
@ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
@ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
@ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
@ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
@ 0xb6337ad4 mesos::internal::log::Replica::Replica()
@ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
@ 0xb62cabc8 mesos::internal::log::Log::Log()
@0x41818 main
@ 0xb51965f8 (unknown)
Aborted
{noformat}
was:
Configuration : ../configure --disable-java
---
{noformat}
c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
--work_dir=/var/lib/mesos
I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
leveldb::BytewiseComparator()->Compare(one, two) < 0
*** Check failure stack trace: ***
@ 0xb63db678 google::LogMessage::Fail()
@ 0xb63dd428 google::LogMessage::SendToLog()
@ 0xb63db294 google::LogMessage::Flush()
@ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
@ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
@ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
@ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
@ 0xb6337ad4 mesos::internal::log::Replica::Replica()
@ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
@ 0xb62cabc8 mesos::internal::log::Log::Log()
@0x41818 main
@ 0xb51965f8 (unknown)
Aborted
{noformat}
> Mesos will not execute
> --
>
> Key: MESOS-2021
> URL: https://issues.apache.org/jira/browse/MESOS-2021
> Project: Mesos
> Issue Type: Bug
> Components: cli, general
>Affects Versions: 0.20.1
> Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP
> Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree)
> GNU/Linux
>Reporter: Axel Etcheverry
>Priority: Blocker
>
> Configuration : ../configure --disable-java
> {noformat}
> c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
> --work_dir=/var/lib/mesos
> I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
> I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
> F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
> leveldb::BytewiseComparator()->Compare(one, two) < 0
> *** Check failure stack trace: ***
> @ 0xb63db678 google::LogMessage::Fail()
> @ 0xb63dd428 google::LogMessage::SendToLog()
> @ 0xb63db294 google::LogMessage::Flush()
> @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
> @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
> @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
> @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0xb6337ad4 mesos::internal::log::Replica::Replica()
> @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
> @ 0xb62cabc8 mesos::internal::log::Log::Log()
> @0x41818 main
> @ 0xb51965f8 (unknown)
> Aborted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2021) Mesos will not execute
[
https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Axel Etcheverry updated MESOS-2021:
---
Description:
Configuration : ../configure --disable-java
---
{noformat}
c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
--work_dir=/var/lib/mesos
I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
leveldb::BytewiseComparator()->Compare(one, two) < 0
*** Check failure stack trace: ***
@ 0xb63db678 google::LogMessage::Fail()
@ 0xb63dd428 google::LogMessage::SendToLog()
@ 0xb63db294 google::LogMessage::Flush()
@ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
@ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
@ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
@ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
@ 0xb6337ad4 mesos::internal::log::Replica::Replica()
@ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
@ 0xb62cabc8 mesos::internal::log::Log::Log()
@0x41818 main
@ 0xb51965f8 (unknown)
Aborted
{noformat}
was:
Configuration : ../configure --disable-java
---
c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
--work_dir=/var/lib/mesos
I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
leveldb::BytewiseComparator()->Compare(one, two) < 0
*** Check failure stack trace: ***
@ 0xb63db678 google::LogMessage::Fail()
@ 0xb63dd428 google::LogMessage::SendToLog()
@ 0xb63db294 google::LogMessage::Flush()
@ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
@ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
@ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
@ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
@ 0xb6337ad4 mesos::internal::log::Replica::Replica()
@ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
@ 0xb62cabc8 mesos::internal::log::Log::Log()
@0x41818 main
@ 0xb51965f8 (unknown)
Aborted
> Mesos will not execute
> --
>
> Key: MESOS-2021
> URL: https://issues.apache.org/jira/browse/MESOS-2021
> Project: Mesos
> Issue Type: Bug
> Components: cli, general
>Affects Versions: 0.20.1
> Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP
> Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree)
> GNU/Linux
>Reporter: Axel Etcheverry
>Priority: Blocker
>
> Configuration : ../configure --disable-java
> ---
> {noformat}
> c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1
> --work_dir=/var/lib/mesos
> I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
> I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
> F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed:
> leveldb::BytewiseComparator()->Compare(one, two) < 0
> *** Check failure stack trace: ***
> @ 0xb63db678 google::LogMessage::Fail()
> @ 0xb63dd428 google::LogMessage::SendToLog()
> @ 0xb63db294 google::LogMessage::Flush()
> @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal()
> @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore()
> @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore()
> @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0xb6337ad4 mesos::internal::log::Replica::Replica()
> @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess()
> @ 0xb62cabc8 mesos::internal::log::Log::Log()
> @0x41818 main
> @ 0xb51965f8 (unknown)
> Aborted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2021) Mesos will not execute
[ https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Axel Etcheverry updated MESOS-2021: --- Description: Configuration : ../configure --disable-java --- c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: leveldb::BytewiseComparator()->Compare(one, two) < 0 *** Check failure stack trace: *** @ 0xb63db678 google::LogMessage::Fail() @ 0xb63dd428 google::LogMessage::SendToLog() @ 0xb63db294 google::LogMessage::Flush() @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() @ 0xb6337ad4 mesos::internal::log::Replica::Replica() @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() @ 0xb62cabc8 mesos::internal::log::Log::Log() @0x41818 main @ 0xb51965f8 (unknown) Aborted was: c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: leveldb::BytewiseComparator()->Compare(one, two) < 0 *** Check failure stack trace: *** @ 0xb63db678 google::LogMessage::Fail() @ 0xb63dd428 google::LogMessage::SendToLog() @ 0xb63db294 google::LogMessage::Flush() @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() @ 0xb6337ad4 mesos::internal::log::Replica::Replica() @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() @ 0xb62cabc8 mesos::internal::log::Log::Log() @0x41818 main @ 0xb51965f8 (unknown) Aborted > Mesos will not execute > -- > > Key: MESOS-2021 > URL: https://issues.apache.org/jira/browse/MESOS-2021 > Project: Mesos > Issue Type: Bug > Components: cli, general >Affects Versions: 0.20.1 > Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP > Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) > GNU/Linux >Reporter: Axel Etcheverry >Priority: Blocker > > Configuration : ../configure --disable-java > --- > c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 > --work_dir=/var/lib/mesos > I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root > I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 > F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: > leveldb::BytewiseComparator()->Compare(one, two) < 0 > *** Check failure stack trace: *** > @ 0xb63db678 google::LogMessage::Fail() > @ 0xb63dd428 google::LogMessage::SendToLog() > @ 0xb63db294 google::LogMessage::Flush() > @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() > @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() > @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() > @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() > @ 0xb6337ad4 mesos::internal::log::Replica::Replica() > @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() > @ 0xb62cabc8 mesos::internal::log::Log::Log() > @0x41818 main > @ 0xb51965f8 (unknown) > Aborted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2021) Mesos will not execute
[ https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191756#comment-14191756 ] Axel Etcheverry commented on MESOS-2021: You can test on http://labs.online.net/, the service is in private beta, but I can send you an invitation. > Mesos will not execute > -- > > Key: MESOS-2021 > URL: https://issues.apache.org/jira/browse/MESOS-2021 > Project: Mesos > Issue Type: Bug > Components: cli, general >Affects Versions: 0.20.1 > Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP > Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) > GNU/Linux >Reporter: Axel Etcheverry >Priority: Blocker > > c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 > --work_dir=/var/lib/mesos > I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root > I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 > F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: > leveldb::BytewiseComparator()->Compare(one, two) < 0 > *** Check failure stack trace: *** > @ 0xb63db678 google::LogMessage::Fail() > @ 0xb63dd428 google::LogMessage::SendToLog() > @ 0xb63db294 google::LogMessage::Flush() > @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() > @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() > @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() > @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() > @ 0xb6337ad4 mesos::internal::log::Replica::Replica() > @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() > @ 0xb62cabc8 mesos::internal::log::Log::Log() > @0x41818 main > @ 0xb51965f8 (unknown) > Aborted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2021) Mesos will not execute
[ https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191750#comment-14191750 ] Axel Etcheverry commented on MESOS-2021: Hi Alexander, I build Mesos on ARM (via tar.gz). > Mesos will not execute > -- > > Key: MESOS-2021 > URL: https://issues.apache.org/jira/browse/MESOS-2021 > Project: Mesos > Issue Type: Bug > Components: cli, general >Affects Versions: 0.20.1 > Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP > Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) > GNU/Linux >Reporter: Axel Etcheverry >Priority: Blocker > > c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 > --work_dir=/var/lib/mesos > I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root > I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 > F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: > leveldb::BytewiseComparator()->Compare(one, two) < 0 > *** Check failure stack trace: *** > @ 0xb63db678 google::LogMessage::Fail() > @ 0xb63dd428 google::LogMessage::SendToLog() > @ 0xb63db294 google::LogMessage::Flush() > @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() > @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() > @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() > @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() > @ 0xb6337ad4 mesos::internal::log::Replica::Replica() > @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() > @ 0xb62cabc8 mesos::internal::log::Log::Log() > @0x41818 main > @ 0xb51965f8 (unknown) > Aborted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2021) Mesos will not execute
[ https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191703#comment-14191703 ] Alexander Rukletsov commented on MESOS-2021: Do you try to run Mesos on ARM architecture? Have you built Mesos for ARM or do you use binaries compiled for x86_64? > Mesos will not execute > -- > > Key: MESOS-2021 > URL: https://issues.apache.org/jira/browse/MESOS-2021 > Project: Mesos > Issue Type: Bug > Components: cli, general >Affects Versions: 0.20.1 > Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP > Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) > GNU/Linux >Reporter: Axel Etcheverry >Priority: Blocker > > c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 > --work_dir=/var/lib/mesos > I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root > I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 > F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: > leveldb::BytewiseComparator()->Compare(one, two) < 0 > *** Check failure stack trace: *** > @ 0xb63db678 google::LogMessage::Fail() > @ 0xb63dd428 google::LogMessage::SendToLog() > @ 0xb63db294 google::LogMessage::Flush() > @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() > @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() > @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() > @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() > @ 0xb6337ad4 mesos::internal::log::Replica::Replica() > @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() > @ 0xb62cabc8 mesos::internal::log::Log::Log() > @0x41818 main > @ 0xb51965f8 (unknown) > Aborted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2022) Mesos does not compile on ARM architecture
Axel Etcheverry created MESOS-2022: -- Summary: Mesos does not compile on ARM architecture Key: MESOS-2022 URL: https://issues.apache.org/jira/browse/MESOS-2022 Project: Mesos Issue Type: Bug Components: build Affects Versions: 0.20.1 Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) GNU/Linux Reporter: Axel Etcheverry Priority: Blocker Hi, The compilation is blocked by ZooKeeper <=3.4.6, fixed by >=3.5. the patch for ZooKeeper 3.4.6 : https://gist.github.com/euskadi31/2e5a2f9e9d7e94a621e0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2021) Mesos will not execute
Axel Etcheverry created MESOS-2021: -- Summary: Mesos will not execute Key: MESOS-2021 URL: https://issues.apache.org/jira/browse/MESOS-2021 Project: Mesos Issue Type: Bug Components: cli, general Affects Versions: 0.20.1 Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) GNU/Linux Reporter: Axel Etcheverry Priority: Blocker c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1 F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: leveldb::BytewiseComparator()->Compare(one, two) < 0 *** Check failure stack trace: *** @ 0xb63db678 google::LogMessage::Fail() @ 0xb63dd428 google::LogMessage::SendToLog() @ 0xb63db294 google::LogMessage::Flush() @ 0xb63ddbc4 google::LogMessageFatal::~LogMessageFatal() @ 0xb62c8fb0 mesos::internal::log::LevelDBStorage::restore() @ 0xb6337198 mesos::internal::log::ReplicaProcess::restore() @ 0xb6337920 mesos::internal::log::ReplicaProcess::ReplicaProcess() @ 0xb6337ad4 mesos::internal::log::Replica::Replica() @ 0xb62ca948 mesos::internal::log::LogProcess::LogProcess() @ 0xb62cabc8 mesos::internal::log::Log::Log() @0x41818 main @ 0xb51965f8 (unknown) Aborted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2020) Silent failures for docker containers
[
https://issues.apache.org/jira/browse/MESOS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191622#comment-14191622
]
Ian Babrou commented on MESOS-2020:
---
Same happens when docker container is not found in the registry.
> Silent failures for docker containers
> -
>
> Key: MESOS-2020
> URL: https://issues.apache.org/jira/browse/MESOS-2020
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Affects Versions: 0.20.1
> Environment: mesos-slaves running in docker
>Reporter: Ian Babrou
>
> I tried to start container that cannot actually start for some reason, like
> this (from slave logs):
> {"log":"I1031 08:58:02.69295860 slave.cpp:1112] Launching task
> topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799 for framework
> 20141003-172543-3892422848-5050-1-\n","stream":"stderr","time":"2014-10-31T08:58:02.692986684Z"}
> {"log":"I1031 08:58:02.69369660 slave.cpp:1222] Queuing task
> 'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799' for executor
> topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799 of framework
> '20141003-172543-3892422848-5050-1-\n","stream":"stderr","time":"2014-10-31T08:58:02.693734418Z"}
> {"log":"I1031 08:58:02.69561264 docker.cpp:743] Starting container
> '02a786c9-556c-4ed9-80d2-1850a49030fe' for task
> 'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799' (and executor
> 'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799') of framework
> '20141003-172543-3892422848-5050-1-'\n","stream":"stderr","time":"2014-10-31T08:58:02.6956675Z"}
> {"log":"E1031 08:58:05.27290265 slave.cpp:2485] Container
> '02a786c9-556c-4ed9-80d2-1850a49030fe' for executor
> 'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799' of framework
> '20141003-172543-3892422848-5050-1-' failed to start: Failed to 'docker
> run -d -c 204 -m 67108864 -e PORT=31459 -e PORT0=31459 -e PORTS=31459 -e
> HOST=web544 -e MESOS_SANDBOX=/mnt/mesos/sandbox -v
> /var/lib/mesos/slave/slaves/20141028-073834-3909200064-5050-1-75/frameworks/20141003-172543-3892422848-5050-1-/executors/topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799/runs/02a786c9-556c-4ed9-80d2-1850a49030fe:/mnt/mesos/sandbox
> --net host --name mesos-02a786c9-556c-4ed9-80d2-1850a49030fe
> docker.core.tf/demo:1': exit status = exited with status 1 stderr =
> 2014/10/31 08:58:04 Error response from daemon: Cannot start container
> 05666763bff98ad70f35968add3923018a9d457a1f4e9dab0981936841093d2f: exec:
> \"/server.js\": permission
> denied\n","stream":"stderr","time":"2014-10-31T08:58:05.273016253Z"}
> But when I go to task sandbox from mesos ui, stdout and stderr are empty.
> Marathon keeps scheduling tasks, but they all silently fail, this is very
> misleading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-2020) Silent failures for docker containers
Ian Babrou created MESOS-2020:
-
Summary: Silent failures for docker containers
Key: MESOS-2020
URL: https://issues.apache.org/jira/browse/MESOS-2020
Project: Mesos
Issue Type: Bug
Components: slave
Affects Versions: 0.20.1
Environment: mesos-slaves running in docker
Reporter: Ian Babrou
I tried to start container that cannot actually start for some reason, like
this (from slave logs):
{"log":"I1031 08:58:02.69295860 slave.cpp:1112] Launching task
topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799 for framework
20141003-172543-3892422848-5050-1-\n","stream":"stderr","time":"2014-10-31T08:58:02.692986684Z"}
{"log":"I1031 08:58:02.69369660 slave.cpp:1222] Queuing task
'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799' for executor
topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799 of framework
'20141003-172543-3892422848-5050-1-\n","stream":"stderr","time":"2014-10-31T08:58:02.693734418Z"}
{"log":"I1031 08:58:02.69561264 docker.cpp:743] Starting container
'02a786c9-556c-4ed9-80d2-1850a49030fe' for task
'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799' (and executor
'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799') of framework
'20141003-172543-3892422848-5050-1-'\n","stream":"stderr","time":"2014-10-31T08:58:02.6956675Z"}
{"log":"E1031 08:58:05.27290265 slave.cpp:2485] Container
'02a786c9-556c-4ed9-80d2-1850a49030fe' for executor
'topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799' of framework
'20141003-172543-3892422848-5050-1-' failed to start: Failed to 'docker run
-d -c 204 -m 67108864 -e PORT=31459 -e PORT0=31459 -e PORTS=31459 -e
HOST=web544 -e MESOS_SANDBOX=/mnt/mesos/sandbox -v
/var/lib/mesos/slave/slaves/20141028-073834-3909200064-5050-1-75/frameworks/20141003-172543-3892422848-5050-1-/executors/topface_demo.055a8f8f-60dc-11e4-b4ad-56847afe9799/runs/02a786c9-556c-4ed9-80d2-1850a49030fe:/mnt/mesos/sandbox
--net host --name mesos-02a786c9-556c-4ed9-80d2-1850a49030fe
docker.core.tf/demo:1': exit status = exited with status 1 stderr = 2014/10/31
08:58:04 Error response from daemon: Cannot start container
05666763bff98ad70f35968add3923018a9d457a1f4e9dab0981936841093d2f: exec:
\"/server.js\": permission
denied\n","stream":"stderr","time":"2014-10-31T08:58:05.273016253Z"}
But when I go to task sandbox from mesos ui, stdout and stderr are empty.
Marathon keeps scheduling tasks, but they all silently fail, this is very
misleading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (MESOS-1414) Status updates should not be sent from the slave until it is registered.
[ https://issues.apache.org/jira/browse/MESOS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B resolved MESOS-1414. --- Resolution: Fixed Fix Version/s: 0.21.0 Assignee: Vinod Kone (was: Craig Hansen-Sturm) Target Version/s: 0.21.0 commit 65c3c3639b385d880dbfe10bc4f652655695c8b3 Author: Vinod Kone Date: Fri Oct 17 15:26:52 2014 -0700 Added pause() and resume() to status update manager. Review: https://reviews.apache.org/r/26957 commit e64dda411bc83963179c92ae71caefa8d21b54b4 Author: Vinod Kone Date: Wed Oct 15 18:22:46 2014 -0700 Updated status update manager to forward updates via slave. Review: https://reviews.apache.org/r/26846 > Status updates should not be sent from the slave until it is registered. > > > Key: MESOS-1414 > URL: https://issues.apache.org/jira/browse/MESOS-1414 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 >Reporter: Benjamin Mahler >Assignee: Vinod Kone > Fix For: 0.21.0 > > > Currently, status updates are sent from the slave once a master is detected, > instead of waiting for the slave to be registered. > The master currently drops updates that arrive while the slave is not > activated, so this is harmless but causes an unnecessary amount of dropped > messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
