mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stavros Kontopoulos (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine
Date Fri, 22 Apr 2016 20:10:13 GMT

    [ 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] 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 1111ns
> 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 371121ns
> I1022 18:42:26.857841   140 replica.cpp:323] Persisted replica status to VOTING
> I1022 18:42:26.857895   140 recover.cpp:580] Successfully joined the Paxos group
> I1022 18:42:26.857928   140 recover.cpp:464] Recover process terminated
> I1022 18:42:26.862455   137 master.cpp:1603] The newly elected leader is master@172.17.0.14:5050
with id a3f39818-1bda-4710-b96b-2a60ed4d12b8
> I1022 18:42:26.862498   137 master.cpp:1616] Elected as the leading master!
> I1022 18:42:26.862511   137 master.cpp:1376] Recovering from registrar
> I1022 18:42:26.862560   137 registrar.cpp:309] Recovering registrar
> Failed to create a containerizer: Could not create MesosContainerizer: Failed to create
launcher: Failed to create Linux launcher: Failed to mount cgroups hierarchy at '/sys/fs/cgroup/freezer':
'freezer' is already attached to another hierarchy
> {noformat}
> The setup worked with mesos 0.24.0.
> The Dockerfile is here: https://github.com/mesosphere/marathon/blob/mv/mesos_0.25/Dockerfile
> {noformat}
> root@a06e4b4eb776:/marathon# ls /sys/fs/cgroup/
> root@a06e4b4eb776:/marathon# 
> {noformat}
> {noformat}
> root@a06e4b4eb776:/marathon# cat /proc/mounts 
> none / aufs rw,relatime,si=6e7ac87f36042e03,dio,dirperm1 0 0
> proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> tmpfs /dev tmpfs rw,nosuid,mode=755 0 0
> devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
> shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0
> mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
> sysfs /sys sysfs ro,nosuid,nodev,noexec,relatime 0 0
> /dev/sda1 /etc/resolv.conf ext4 rw,relatime,data=ordered 0 0
> /dev/sda1 /etc/hostname ext4 rw,relatime,data=ordered 0 0
> /dev/sda1 /etc/hosts ext4 rw,relatime,data=ordered 0 0
> devpts /dev/console devpts rw,relatime,mode=600,ptmxmode=000 0 0
> proc /proc/bus proc ro,nosuid,nodev,noexec,relatime 0 0
> proc /proc/fs proc ro,nosuid,nodev,noexec,relatime 0 0
> proc /proc/irq proc ro,nosuid,nodev,noexec,relatime 0 0
> proc /proc/sys proc ro,nosuid,nodev,noexec,relatime 0 0
> proc /proc/sysrq-trigger proc ro,nosuid,nodev,noexec,relatime 0 0
> tmpfs /proc/kcore tmpfs rw,nosuid,mode=755 0 0
> tmpfs /proc/timer_stats tmpfs rw,nosuid,mode=755 0 0
> {noformat}
> [~bernd-mesos] Can you please assign to the correct person?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message