[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 9:18 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but what if i have
systemd, the flag --launcher...will not work.
With 16.04 that might be an issue...
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but what if i have
systemd, the flag --launcher...will not work.
With 16.04 that is an issue...
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 8:09 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but what if i have
systemd, the flag --launcher...will not work
and with 16.04 that is an issue...
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but the what if i
have systemd the flag --launcher...does not work
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I102
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 8:09 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but what if i have
systemd, the flag --launcher...will not work.
With 16.04 that is an issue...
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but what if i have
systemd, the flag --launcher...will not work
and with 16.04 that is an issue...
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacte
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 8:08 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
It is because 15.04 does not use upstart. I verified it by falling back:
apt-get install upstart-sysv... then everything worked... but the what if i
have systemd the flag --launcher...does not work
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas? Is it because 15.04 does not use upstart?
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.c
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 8:06 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas? Is it because 15.04 does not use upstart?
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 7:54 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141 recover.cpp:449] Starting replica recov
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 7:54 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
{code:|borderStyle=solid}
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
{code}
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141 recover.cpp:449] Starting replica recovery
> I1022 18:42:26.853862 14
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254514#comment-15254514
]
Stavros Kontopoulos edited comment on MESOS-3793 at 4/22/16 7:34 PM:
-
Still see the issue with mesos 0.28.1 using this image
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
was (Author: skonto):
Still see the issue with mesos 0.28.1 using this images
https://hub.docker.com/r/osrg/dind-ubuntu-vivid/
and installing mesos as follows:
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
DISTRO=$(lsb_release -is | tr '[:upper:]' '[:lower:]') && \
CODENAME=$(lsb_release -cs) && \
echo $CODENAME && \
echo $DISTRO && \
echo "deb http://repos.mesosphere.io/${DISTRO} ${CODENAME} main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
apt-get -y update && \
VERSION=$(apt-cache madison mesos | head -1 | awk '{ print $3 }') && \
MARATHON_VERSION=$(apt-cache madison marathon | head -1 | awk '{ print $3
}') && \
apt-get -y install mesos=$VERSION && \
apt-get install marathon=$MARATHON_VERSION && \
rm -rf /var/lib/apt/lists/*
When i run:
root@stavrospc:/# /usr/sbin/mesos-slave --master=172.17.0.1:5050
--ip=172.17.0.1 --launcher=posix
I0422 19:33:32.743777 24201 logging.cpp:188] INFO level logging started!
I0422 19:33:32.743979 24201 main.cpp:223] Build: 2016-04-14 15:43:15 by root
I0422 19:33:32.743996 24201 main.cpp:225] Version: 0.28.1
I0422 19:33:32.744005 24201 main.cpp:228] Git tag: 0.28.1
I0422 19:33:32.744014 24201 main.cpp:232] Git SHA:
555db235a34afbb9fb49940376cc33a66f1f85f0
I0422 19:33:32.746184 24201 systemd.cpp:236] systemd version `219` detected
I0422 19:33:32.746215 24201 main.cpp:240] Inializing systemd state
Failed to initialize systemd: Failed to locate systemd runtime directory:
/run/systemd/system
root@stavrospc:/# ls /usr/lib/libm*
/usr/lib/libmesos-0.28.1.so /usr/lib/libmesos.la /usr/lib/libmesos.so
Any ideas?
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141 recover.cpp:449] Starting replica recovery
> I1022 18:42:26.853862 141 recover.cpp:475] Replica is in
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013127#comment-15013127
]
Matthias Veit edited comment on MESOS-3793 at 11/19/15 8:29 AM:
Hey Jojy,
don't know if this is related to the docker linux host os. I tried several
different ones all with the same result. Also on Ubuntu 14.04.
Steps to reproduce:
{noformat}
$> docker run -it java:8-jdk /bin/bash
$> apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
echo "deb http://repos.mesosphere.io/debian jessie main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
echo "deb http://dl.bintray.com/sbt/debian /" | tee -a
/etc/apt/sources.list.d/sbt.list && \
apt-get update && \
apt-get install --no-install-recommends -y --force-yes
mesos=0.25.0-0.2.70.debian81
$> mesos local
{noformat}
After doing this, you should see the very same result.
Just to be clear - this problem happens with 100% guarantee.
I do not supply any other options, env vars etc. to that process.
This is the exact same command chain used for Marathon integration tests.
was (Author: aquamatthias):
Hey Jojy,
don't know if this is related to the docker linux host os. I tried several
different ones all with the same result. Also on Ubuntu 14.04.
Steps to reproduce:
{noformat}
$> docker run -it java:8-jdk /bin/bash
$> apt-key adv --keyserver keyserver.ubuntu.com --recv E56151BF && \
echo "deb http://repos.mesosphere.io/debian jessie main" | tee
/etc/apt/sources.list.d/mesosphere.list && \
echo "deb http://dl.bintray.com/sbt/debian /" | tee -a
/etc/apt/sources.list.d/sbt.list && \
apt-get update && \
apt-get install --no-install-recommends -y --force-yes
mesos=0.25.0-0.2.70.debian81
$> mesos local
{noformat}
After doing this, you should see the very same result.
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141 recover.cpp:449] Starting replica recovery
> I1022 18:42:26.853862 141 recover.cpp:475] Replica is in EMPTY status
> I1022 18:42:26.854751 138 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I1022 18:42:26.854856 140 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I1022 18:42:26.855002 140 recover.cpp:566] Updating replica status to
> STARTING
> I1022 18:42:26.855655 138 master.cpp:376] Master
> a3f39818-1bda-4710-b96b-2a60ed4d12b8 (a06e4b4eb776) started on
> 172.17.0.14:5050
> I1022 18:42:26.855680 138 master.cpp:378] Flags at startup:
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="false" --authenticate_slaves="false"
> --authenticators="crammd5" --authorizers="local" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_slave_ping_timeouts="5" --quiet="false"
> --recovery_slave_removal_limit="100%" --registry="replicated_log"
> --registry_fetch_timeout="1mins" --registry_store_timeout="5secs"
> --registry_strict="false" --root_submissions="true"
> --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
> --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui"
> --work_dir="/tmp/mesos/local/AK0XpG" --zk_session_timeout="10secs"
> I1022 18:42:26.855790 138 master.cpp:425] Master allowing unauthenticated
> frameworks to register
> I1022 18:42:26.855803 138 master.cpp:430] Master allowing unauthenticated
> slaves to register
> I1022 18:42:26.855815 138 master.cpp:467] Using default 'crammd5'
> authenticator
> W1022 18:42:26.855829 138 authenticator.cpp:505] No credentia
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011785#comment-15011785
]
Jie Yu edited comment on MESOS-3793 at 11/18/15 7:52 PM:
-
Is it possible to add MESOS_LAUNCHER=posix to the startup script? An
alternative is change mesos-local logic to use posix launcher if the user does
not specify the launcher.
There is some recent change that tries to use linux launcher whenever possible
(running under linux with root permission). Previously, posix launcher is
always used for local cluster.
Since mesos local might create multiple slaves on the same host, we should
always use posix launcher (linux launcher does not work if there're multiple
slaves running on the same host).
was (Author: jieyu):
Is it possible to add MESOS_LAUNCHER=posix to the startup script?
There is some recent change that tries to use linux launcher whenever possible
(running under linux with root permission). Previously, posix launcher is
always used for local cluster.
Since mesos local might create multiple slaves on the same host, we should
always use posix launcher (linux launcher does not work if there're multiple
slaves running on the same host).
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141 recover.cpp:449] Starting replica recovery
> I1022 18:42:26.853862 141 recover.cpp:475] Replica is in EMPTY status
> I1022 18:42:26.854751 138 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I1022 18:42:26.854856 140 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I1022 18:42:26.855002 140 recover.cpp:566] Updating replica status to
> STARTING
> I1022 18:42:26.855655 138 master.cpp:376] Master
> a3f39818-1bda-4710-b96b-2a60ed4d12b8 (a06e4b4eb776) started on
> 172.17.0.14:5050
> I1022 18:42:26.855680 138 master.cpp:378] Flags at startup:
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="false" --authenticate_slaves="false"
> --authenticators="crammd5" --authorizers="local" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_slave_ping_timeouts="5" --quiet="false"
> --recovery_slave_removal_limit="100%" --registry="replicated_log"
> --registry_fetch_timeout="1mins" --registry_store_timeout="5secs"
> --registry_strict="false" --root_submissions="true"
> --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
> --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui"
> --work_dir="/tmp/mesos/local/AK0XpG" --zk_session_timeout="10secs"
> I1022 18:42:26.855790 138 master.cpp:425] Master allowing unauthenticated
> frameworks to register
> I1022 18:42:26.855803 138 master.cpp:430] Master allowing unauthenticated
> slaves to register
> I1022 18:42:26.855815 138 master.cpp:467] Using default 'crammd5'
> authenticator
> W1022 18:42:26.855829 138 authenticator.cpp:505] No credentials provided,
> authentication requests will be refused
> I1022 18:42:26.855840 138 authenticator.cpp:512] Initializing server SASL
> I1022 18:42:26.856442 136 containerizer.cpp:143] Using isolation:
> posix/cpu,posix/mem,filesystem/posix
> I1022 18:42:26.856943 140 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 1.888185ms
> I1022 18:42:26.856987 140 replica.cpp:323] Persisted replica status to
> STARTING
> I1022 18:42:26.857115 140 recover.cpp:475] Replica is in STARTING status
> I1022 18:42:26.857270 140 replica.cpp:641] Replica in STARTING status
> received a broadcasted recover r
[jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
[
https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011785#comment-15011785
]
Jie Yu edited comment on MESOS-3793 at 11/18/15 7:43 PM:
-
Is it possible to add MESOS_LAUNCHER=posix to the startup script?
There is some recent change that tries to use linux launcher whenever possible
(running under linux with root permission). Previously, posix launcher is
always used for local cluster.
Since mesos local might create multiple slaves on the same host, we should
always use posix launcher (linux launcher does not work if there're multiple
slaves running on the same host).
was (Author: jieyu):
Is it possible to add MESOS_LAUNCHER=posix to the startup script?
There is some recent change that tries to use linux launcher whenever possible
(running under linux with root permission). Previously, posix launcher is
always used for local cluster.
> Cannot start mesos local on a Debian GNU/Linux 8 docker machine
> ---
>
> Key: MESOS-3793
> URL: https://issues.apache.org/jira/browse/MESOS-3793
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
> Environment: Debian GNU/Linux 8 docker machine
>Reporter: Matthias Veit
>Assignee: Jojy Varghese
> Labels: mesosphere
>
> We updated the mesos version to 0.25.0 in our Marathon docker image, that
> runs our integration tests.
> We use mesos local for those tests. This fails with this message:
> {noformat}
> root@a06e4b4eb776:/marathon# mesos local
> I1022 18:42:26.852485 136 leveldb.cpp:176] Opened db in 6.103258ms
> I1022 18:42:26.853302 136 leveldb.cpp:183] Compacted db in 765740ns
> I1022 18:42:26.853343 136 leveldb.cpp:198] Created db iterator in 9001ns
> I1022 18:42:26.853355 136 leveldb.cpp:204] Seeked to beginning of db in
> 1287ns
> I1022 18:42:26.853366 136 leveldb.cpp:273] Iterated through 0 keys in the
> db in ns
> I1022 18:42:26.853406 136 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1022 18:42:26.853775 141 recover.cpp:449] Starting replica recovery
> I1022 18:42:26.853862 141 recover.cpp:475] Replica is in EMPTY status
> I1022 18:42:26.854751 138 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I1022 18:42:26.854856 140 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I1022 18:42:26.855002 140 recover.cpp:566] Updating replica status to
> STARTING
> I1022 18:42:26.855655 138 master.cpp:376] Master
> a3f39818-1bda-4710-b96b-2a60ed4d12b8 (a06e4b4eb776) started on
> 172.17.0.14:5050
> I1022 18:42:26.855680 138 master.cpp:378] Flags at startup:
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="false" --authenticate_slaves="false"
> --authenticators="crammd5" --authorizers="local" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_slave_ping_timeouts="5" --quiet="false"
> --recovery_slave_removal_limit="100%" --registry="replicated_log"
> --registry_fetch_timeout="1mins" --registry_store_timeout="5secs"
> --registry_strict="false" --root_submissions="true"
> --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
> --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui"
> --work_dir="/tmp/mesos/local/AK0XpG" --zk_session_timeout="10secs"
> I1022 18:42:26.855790 138 master.cpp:425] Master allowing unauthenticated
> frameworks to register
> I1022 18:42:26.855803 138 master.cpp:430] Master allowing unauthenticated
> slaves to register
> I1022 18:42:26.855815 138 master.cpp:467] Using default 'crammd5'
> authenticator
> W1022 18:42:26.855829 138 authenticator.cpp:505] No credentials provided,
> authentication requests will be refused
> I1022 18:42:26.855840 138 authenticator.cpp:512] Initializing server SASL
> I1022 18:42:26.856442 136 containerizer.cpp:143] Using isolation:
> posix/cpu,posix/mem,filesystem/posix
> I1022 18:42:26.856943 140 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 1.888185ms
> I1022 18:42:26.856987 140 replica.cpp:323] Persisted replica status to
> STARTING
> I1022 18:42:26.857115 140 recover.cpp:475] Replica is in STARTING status
> I1022 18:42:26.857270 140 replica.cpp:641] Replica in STARTING status
> received a broadcasted recover request
> I1022 18:42:26.857312 140 recover.cpp:195] Received a recover response from
> a replica in STARTING status
> I1022 18:42:26.857368 140 recover.cpp:566] Updating replica status to VOTING
> I1022 18:42:26.857781 140 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 371
