You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2015/11/18 20:04:10 UTC

[jira] [Updated] (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:all-tabpanel ]

Anand Mazumdar updated MESOS-3793:
----------------------------------
    Target Version/s: 0.26.0

> 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 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)