You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by xiaokun <xi...@gmail.com> on 2015/06/19 12:24:17 UTC
mesos-slave service cannot be started when change default
containerizers from mesos to docker
Hi,
I changed default containerizers method for mesos. with below command,
echo 'docker,mesos' > /etc/mesos-slave/containerizers
But it fails in several machines in my cluster.
Machine os is rhel7.1
Here is the log.
After I restart the machine all works well.
Jun 19 06:07:20 mesos-slave1 systemd: Failed to set cpu.shares on
/system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
No such file or directory
Jun 19 06:07:20 mesos-slave1 systemd: Failed to set blkio.weight on
/system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
No such file or directory
Jun 19 06:07:20 mesos-slave1 systemd: Failed to set memory.limit_in_bytes
on
/system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
No such file or directory
Jun 19 06:07:20 mesos-slave1 systemd: Stopping Mesos Slave...
Jun 19 06:07:20 mesos-slave1 systemd: Starting Mesos Slave...
Jun 19 06:07:20 mesos-slave1 systemd: Started Mesos Slave.
Jun 19 06:07:20 mesos-slave1 systemd: Failed to set cpu.shares on
/system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
No such file or directory
Jun 19 06:07:20 mesos-slave1 systemd: Failed to set blkio.weight on
/system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
No such file or directory
Jun 19 06:07:20 mesos-slave1 systemd: Failed to set memory.limit_in_bytes
on
/system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
No such file or directory
Re: mesos-slave service cannot be started when change default
containerizers from mesos to docker
Posted by xiaokun <xi...@gmail.com>.
It happened when i try to restart slave to make it works.
2015-06-19 18:30 GMT+08:00 haosdent <ha...@gmail.com>:
> The error appeared after you restart the slave? Or appeared when you
> change the config and without restart the slave?
>
> On Fri, Jun 19, 2015 at 6:24 PM, xiaokun <xi...@gmail.com> wrote:
>
>> Hi,
>> I changed default containerizers method for mesos. with below command,
>> echo 'docker,mesos' > /etc/mesos-slave/containerizers
>> But it fails in several machines in my cluster.
>> Machine os is rhel7.1
>> Here is the log.
>> After I restart the machine all works well.
>>
>> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set cpu.shares on
>> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
>> No such file or directory
>> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set blkio.weight on
>> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
>> No such file or directory
>> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set memory.limit_in_bytes
>> on
>> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
>> No such file or directory
>> Jun 19 06:07:20 mesos-slave1 systemd: Stopping Mesos Slave...
>> Jun 19 06:07:20 mesos-slave1 systemd: Starting Mesos Slave...
>> Jun 19 06:07:20 mesos-slave1 systemd: Started Mesos Slave.
>> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set cpu.shares on
>> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
>> No such file or directory
>> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set blkio.weight on
>> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
>> No such file or directory
>> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set memory.limit_in_bytes
>> on
>> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
>> No such file or directory
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: mesos-slave service cannot be started when change default
containerizers from mesos to docker
Posted by haosdent <ha...@gmail.com>.
The error appeared after you restart the slave? Or appeared when you change
the config and without restart the slave?
On Fri, Jun 19, 2015 at 6:24 PM, xiaokun <xi...@gmail.com> wrote:
> Hi,
> I changed default containerizers method for mesos. with below command,
> echo 'docker,mesos' > /etc/mesos-slave/containerizers
> But it fails in several machines in my cluster.
> Machine os is rhel7.1
> Here is the log.
> After I restart the machine all works well.
>
> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set cpu.shares on
> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
> No such file or directory
> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set blkio.weight on
> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
> No such file or directory
> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set memory.limit_in_bytes
> on
> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
> No such file or directory
> Jun 19 06:07:20 mesos-slave1 systemd: Stopping Mesos Slave...
> Jun 19 06:07:20 mesos-slave1 systemd: Starting Mesos Slave...
> Jun 19 06:07:20 mesos-slave1 systemd: Started Mesos Slave.
> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set cpu.shares on
> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
> No such file or directory
> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set blkio.weight on
> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
> No such file or directory
> Jun 19 06:07:20 mesos-slave1 systemd: Failed to set memory.limit_in_bytes
> on
> /system.slice/docker-8184c827bb035be10b140518eb811e0493e7445b19f4676d8526f61df5536363.scope:
> No such file or directory
>
--
Best Regards,
Haosdent Huang