[jira] [Commented] (MESOS-7209) Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on windows
[ https://issues.apache.org/jira/browse/MESOS-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896816#comment-15896816 ] Karen Huang commented on MESOS-7209: I found this issue is due to the vaialbe %PreferredToolArchitecture%. In the generated ensure_tool_arch.vxproj file, there are code as below: IF NOT %PreferredToolArchitecture% == "x64" ( echo "ERROR: Environment variable 'PreferredToolArchitecture' must be set to 'x64', see MESOS-6720 for details" 12 EXIT 1 ) The vaiable %PreferredToolArchitecture% has no quotes. So its value (x64) isn't equal to "x64". If you change the code as below: IF NOT "%PreferredToolArchitecture%" == "x64" ( echo "ERROR: Environment variable 'PreferredToolArchitecture' must be set to 'x64', see MESOS-6720 for details" 12 EXIT 1 ) The project will be built successfully. > Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on > windows > - > > Key: MESOS-7209 > URL: https://issues.apache.org/jira/browse/MESOS-7209 > Project: Mesos > Issue Type: Bug > Environment: Windows 10 (64bit) + VS2015 Update 3 >Reporter: Karen Huang > > I try to build mesos with Debug|x64 configuration on Windows. It failed to > build due to error MSB6006: "cmd.exe" exited with code > 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported > when build ensure_tool_arch.vcxproj project. > Here is repro steps: > 1. git clone -c core.autocrlf=true https://github.com/apache/mesos > F:\mesos\src > 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src > 3. set PreferredToolArchitecture=x64 > 4. bootstrap.bat > 5. mkdir build_x64 && pushd build_x64 > 6. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 > -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" > 7. msbuild Mesos.sln /p:Configuration=Debug /p:Platform=x64 /m /t:Rebuild > Error message: > CustomBuild: > Building Custom Rule F:/mesos/src/CMakeLists.txt > CMake does not need to re-run because > F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. > ( was unexpected at this time. > 43>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): > error MSB6006: "cmd.exe" exited with code 255. > [F:\mesos\build_x64\ensure_tool_arch.vcxproj] > If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The > error info is as bleow: > 2>-- Rebuild All started: Project: ensure_tool_arch, Configuration: Debug > x64 -- > 2> Building Custom Rule D:/Mesos/src/CMakeLists.txt > 2> CMake does not need to re-run because > D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. > 2> ( was unexpected at this time. > 2>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): > error MSB6006: "cmd.exe" exited with code 255. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MESOS-7209) Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on windows
[ https://issues.apache.org/jira/browse/MESOS-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Huang updated MESOS-7209: --- Description: I try to build mesos with Debug|x64 configuration on Windows. It failed to build due to error MSB6006: "cmd.exe" exited with code 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported when build ensure_tool_arch.vcxproj project. Here is repro steps: 1. git clone -c core.autocrlf=true https://github.com/apache/mesos F:\mesos\src 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src 3. set PreferredToolArchitecture=x64 4. bootstrap.bat 5. mkdir build_x64 && pushd build_x64 6. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" 7. msbuild Mesos.sln /p:Configuration=Debug /p:Platform=x64 /m /t:Rebuild Error message: CustomBuild: Building Custom Rule F:/mesos/src/CMakeLists.txt CMake does not need to re-run because F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. ( was unexpected at this time. 43>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. [F:\mesos\build_x64\ensure_tool_arch.vcxproj] If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The error info is as bleow: 2>-- Rebuild All started: Project: ensure_tool_arch, Configuration: Debug x64 -- 2> Building Custom Rule D:/Mesos/src/CMakeLists.txt 2> CMake does not need to re-run because D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. 2> ( was unexpected at this time. 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. was: I try to build mesos with Debug|x64 configuration on Windows. It failed to build due to error MSB6006: "cmd.exe" exited with code 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported when build ensure_tool_arch.vcxproj project. Here is repro steps: 1. git clone -c core.autocrlf=true https://github.com/apache/mesos F:\mesos\src 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src 3. bootstrap.bat 4. mkdir build_x64 && pushd build_x64 5. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" 6. msbuild Mesos.sln /p:Configuration=Debug /p:PreferredToolArchitecture=x64 /m /t:Rebuild Error message: CustomBuild: Building Custom Rule F:/mesos/src/CMakeLists.txt CMake does not need to re-run because F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. ( was unexpected at this time. 43>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. [F:\mesos\build_x64\ensure_tool_arch.vcxproj] If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The error info is as bleow: 2>-- Rebuild All started: Project: ensure_tool_arch, Configuration: Debug x64 -- 2> Building Custom Rule D:/Mesos/src/CMakeLists.txt 2> CMake does not need to re-run because D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. 2> ( was unexpected at this time. 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. > Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on > windows > - > > Key: MESOS-7209 > URL: https://issues.apache.org/jira/browse/MESOS-7209 > Project: Mesos > Issue Type: Bug > Environment: Windows 10 (64bit) + VS2015 Update 3 >Reporter: Karen Huang > > I try to build mesos with Debug|x64 configuration on Windows. It failed to > build due to error MSB6006: "cmd.exe" exited with code > 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported > when build ensure_tool_arch.vcxproj project. > Here is repro steps: > 1. git clone -c core.autocrlf=true https://github.com/apache/mesos > F:\mesos\src > 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src > 3. set PreferredToolArchitecture=x64 > 4. bootstrap.bat > 5. mkdir build_x64 && pushd build_x64 > 6. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 > -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" > 7. msbuild Mesos.sln /p:Configuration=Debug /p:Platform=x64 /m /t:Rebuild > Error message: > CustomBuild: > Building Custom Rule F:/mesos/src/CMakeLists.txt > CMake does not need to re-run because > F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. > ( was unexpected at this time. >
[jira] [Commented] (MESOS-5900) Support Unix domain socket connections in libprocess
[ https://issues.apache.org/jira/browse/MESOS-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896720#comment-15896720 ] haosdent commented on MESOS-5900: - The patch is https://reviews.apache.org/r/53460/ > Support Unix domain socket connections in libprocess > > > Key: MESOS-5900 > URL: https://issues.apache.org/jira/browse/MESOS-5900 > Project: Mesos > Issue Type: Improvement > Components: libprocess >Reporter: Neil Conway >Assignee: Benjamin Hindman > Labels: mesosphere > Fix For: 1.2.0 > > > We should consider allowing two programs on the same host using libprocess to > communicate via Unix domain sockets rather than TCP. This has a few > advantages: > * Security: remote hosts cannot connect to the Unix socket. Domain sockets > also offer additional support for > [authentication|https://docs.fedoraproject.org/en-US/Fedora_Security_Team/1/html/Defensive_Coding/sect-Defensive_Coding-Authentication-UNIX_Domain.html]. > * Performance: domain sockets are marginally faster than localhost TCP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (MESOS-7208) Persistent volume ownership is set to root when task is running with non-root user
[
https://issues.apache.org/jira/browse/MESOS-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilbert Song reassigned MESOS-7208:
---
Assignee: Gilbert Song
> Persistent volume ownership is set to root when task is running with non-root
> user
> --
>
> Key: MESOS-7208
> URL: https://issues.apache.org/jira/browse/MESOS-7208
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Nikolay Ustinov
>Assignee: Gilbert Song
>
> I’m running docker container in universal containerizer, mesos 1.1.0.
> switch_user=true, isolator=filesystem/linux,docker/runtime. Container is
> launched with marathon, “user”:”someappuser”. I’d want to use persistent
> volume, but it’s exposed to container with root user permissions even if root
> folder is created with someppuser ownership (looks like mesos do chown to
> this folder).
> here logs for my container:
> {code}
> I0305 22:51:36.414655 10175 slave.cpp:1701] Launching task
> 'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' for framework
> e9d0e39e-b67d-4142-b95d-b0987998eb92-
> I0305 22:51:36.415118 10175 paths.cpp:536] Trying to chown
> '/export/intssd/mesos-slave/workdir/slaves/85150805-a201-4b23-ab21-b332a458fc97-S10/frameworks/e9d0e39e-b67d-4142-b95d-b0987998eb92-/executors/md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a/runs/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a'
> to user 'root'
> I0305 22:51:36.422992 10175 slave.cpp:6179] Launching executor
> 'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' of framework
> e9d0e39e-b67d-4142-b95d-b0987998eb92- with resources cpus(*):0.1;
> mem(*):32 in work directory
> '/export/intssd/mesos-slave/workdir/slaves/85150805-a201-4b23-ab21-b332a458fc97-S10/frameworks/e9d0e39e-b67d-4142-b95d-b0987998eb92-/executors/md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a/runs/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a'
> I0305 22:51:36.424278 10175 slave.cpp:1987] Queued task
> 'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' for executor
> 'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' of framework
> e9d0e39e-b67d-4142-b95d-b0987998eb92-
> I0305 22:51:36.424347 10158 docker.cpp:1000] Skipping non-docker container
> I0305 22:51:36.425639 10142 containerizer.cpp:938] Starting container
> e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a for executor
> 'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' of framework
> e9d0e39e-b67d-4142-b95d-b0987998eb92-
> I0305 22:51:36.428725 10166 provisioner.cpp:294] Provisioning image rootfs
> '/export/intssd/mesos-slave/workdir/provisioner/containers/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a/backends/copy/rootfses/0e2181e9-1bf2-42d4-8cb0-ee70e466c3ae'
> for container e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a
> I0305 22:51:42.981240 10149 linux.cpp:695] Changing the ownership of the
> persistent volume at
> '/export/intssd/mesos-slave/data/volumes/roles/general_marathon_service_role/md_hdfs_journal#data#23f813aa-01dd-11e7-a012-0242ce94d92a'
> with uid 0 and gid 0
> I0305 22:51:42.986593 10136 linux_launcher.cpp:421] Launching container
> e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a and cloning with namespaces CLONE_NEWNS
> {code}
> {code}
> ls -la
> /export/intssd/mesos-slave/workdir/slaves/85150805-a201-4b23-ab21-b332a458fc97-S10/frameworks/e9d0e39e-b67d-4142-b95d-b0987998eb92-/executors/md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a/runs/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a/
> drwxr-xr-x 3 someappuser someappgroup 4096 22:51 .
> drwxr-xr-x 3 root root4096 22:51 ..
> drwxr-xr-x 2 root root4096 22:51 data
> -rw-r--r-- 1 root root 169 22:51 stderr
> -rw-r--r-- 1 root root 183012 23:00 stdout
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MESOS-7209) Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on windows
[ https://issues.apache.org/jira/browse/MESOS-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Huang updated MESOS-7209: --- Description: I try to build mesos with Debug|x64 configuration on Windows. It failed to build due to error MSB6006: "cmd.exe" exited with code 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported when build ensure_tool_arch.vcxproj project. Here is repro steps: 1. git clone -c core.autocrlf=true https://github.com/apache/mesos F:\mesos\src 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src 3. bootstrap.bat 4. mkdir build_x64 && pushd build_x64 5. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" 6. msbuild Mesos.sln /p:Configuration=Debug /p:PreferredToolArchitecture=x64 /m /t:Rebuild Error message: CustomBuild: Building Custom Rule F:/mesos/src/CMakeLists.txt CMake does not need to re-run because F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. ( was unexpected at this time. 43>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. [F:\mesos\build_x64\ensure_tool_arch.vcxproj] If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The error info is as bleow: 2>-- Rebuild All started: Project: ensure_tool_arch, Configuration: Debug x64 -- 2> Building Custom Rule D:/Mesos/src/CMakeLists.txt 2> CMake does not need to re-run because D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. 2> ( was unexpected at this time. 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. was: I try to build mesos with Debug|x64 configuration on Windows. It failed to build due to error MSB6006: "cmd.exe" exited with code 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported when build ensure_tool_arch.vcxproj project. Here is repro steps: 1. git clone -c core.autocrlf=true https://github.com/apache/mesos F:\mesos\src 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src 3. .\bootstrap.bat 4. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" 5. msbuild Mesos.sln /p:Configuration=Debug /p:PreferredToolArchitecture=x64 /m /t:Rebuild Error message: CustomBuild: Building Custom Rule F:/mesos/src/CMakeLists.txt CMake does not need to re-run because F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. ( was unexpected at this time. 43>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. [F:\mesos\build_x64\ensure_tool_arch.vcxproj] If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The error info is as bleow: 2>-- Rebuild All started: Project: ensure_tool_arch, Configuration: Debug x64 -- 2> Building Custom Rule D:/Mesos/src/CMakeLists.txt 2> CMake does not need to re-run because D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. 2> ( was unexpected at this time. 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. > Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on > windows > - > > Key: MESOS-7209 > URL: https://issues.apache.org/jira/browse/MESOS-7209 > Project: Mesos > Issue Type: Bug > Environment: Windows 10 (64bit) + VS2015 Update 3 >Reporter: Karen Huang > > I try to build mesos with Debug|x64 configuration on Windows. It failed to > build due to error MSB6006: "cmd.exe" exited with code > 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported > when build ensure_tool_arch.vcxproj project. > Here is repro steps: > 1. git clone -c core.autocrlf=true https://github.com/apache/mesos > F:\mesos\src > 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src > 3. bootstrap.bat > 4. mkdir build_x64 && pushd build_x64 > 5. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 > -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" > 6. msbuild Mesos.sln /p:Configuration=Debug /p:PreferredToolArchitecture=x64 > /m /t:Rebuild > Error message: > CustomBuild: > Building Custom Rule F:/mesos/src/CMakeLists.txt > CMake does not need to re-run because > F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. > ( was unexpected at this time. > 43>C:\Program Files >
[jira] [Created] (MESOS-7209) Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on windows
Karen Huang created MESOS-7209: -- Summary: Mesos failed to build due to error MSB6006: "cmd.exe" exited with code 255 on windows Key: MESOS-7209 URL: https://issues.apache.org/jira/browse/MESOS-7209 Project: Mesos Issue Type: Bug Environment: Windows 10 (64bit) + VS2015 Update 3 Reporter: Karen Huang I try to build mesos with Debug|x64 configuration on Windows. It failed to build due to error MSB6006: "cmd.exe" exited with code 255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported when build ensure_tool_arch.vcxproj project. Here is repro steps: 1. git clone -c core.autocrlf=true https://github.com/apache/mesos F:\mesos\src 2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src 3. .\bootstrap.bat 4. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" 5. msbuild Mesos.sln /p:Configuration=Debug /p:PreferredToolArchitecture=x64 /m /t:Rebuild Error message: CustomBuild: Building Custom Rule F:/mesos/src/CMakeLists.txt CMake does not need to re-run because F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. ( was unexpected at this time. 43>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. [F:\mesos\build_x64\ensure_tool_arch.vcxproj] If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The error info is as bleow: 2>-- Rebuild All started: Project: ensure_tool_arch, Configuration: Debug x64 -- 2> Building Custom Rule D:/Mesos/src/CMakeLists.txt 2> CMake does not need to re-run because D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date. 2> ( was unexpected at this time. 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MESOS-7208) Persistent volume ownership is set to root when task is running with non-root user
Nikolay Ustinov created MESOS-7208:
--
Summary: Persistent volume ownership is set to root when task is
running with non-root user
Key: MESOS-7208
URL: https://issues.apache.org/jira/browse/MESOS-7208
Project: Mesos
Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Nikolay Ustinov
I’m running docker container in universal containerizer, mesos 1.1.0.
switch_user=true, isolator=filesystem/linux,docker/runtime. Container is
launched with marathon, “user”:”someappuser”. I’d want to use persistent
volume, but it’s exposed to container with root user permissions even if root
folder is created with someppuser ownership (looks like mesos do chown to this
folder).
here logs for my container:
{code}
I0305 22:51:36.414655 10175 slave.cpp:1701] Launching task
'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' for framework
e9d0e39e-b67d-4142-b95d-b0987998eb92-
I0305 22:51:36.415118 10175 paths.cpp:536] Trying to chown
'/export/intssd/mesos-slave/workdir/slaves/85150805-a201-4b23-ab21-b332a458fc97-S10/frameworks/e9d0e39e-b67d-4142-b95d-b0987998eb92-/executors/md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a/runs/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a'
to user 'root'
I0305 22:51:36.422992 10175 slave.cpp:6179] Launching executor
'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' of framework
e9d0e39e-b67d-4142-b95d-b0987998eb92- with resources cpus(*):0.1; mem(*):32
in work directory
'/export/intssd/mesos-slave/workdir/slaves/85150805-a201-4b23-ab21-b332a458fc97-S10/frameworks/e9d0e39e-b67d-4142-b95d-b0987998eb92-/executors/md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a/runs/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a'
I0305 22:51:36.424278 10175 slave.cpp:1987] Queued task
'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' for executor
'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' of framework
e9d0e39e-b67d-4142-b95d-b0987998eb92-
I0305 22:51:36.424347 10158 docker.cpp:1000] Skipping non-docker container
I0305 22:51:36.425639 10142 containerizer.cpp:938] Starting container
e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a for executor
'md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a' of framework
e9d0e39e-b67d-4142-b95d-b0987998eb92-
I0305 22:51:36.428725 10166 provisioner.cpp:294] Provisioning image rootfs
'/export/intssd/mesos-slave/workdir/provisioner/containers/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a/backends/copy/rootfses/0e2181e9-1bf2-42d4-8cb0-ee70e466c3ae'
for container e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a
I0305 22:51:42.981240 10149 linux.cpp:695] Changing the ownership of the
persistent volume at
'/export/intssd/mesos-slave/data/volumes/roles/general_marathon_service_role/md_hdfs_journal#data#23f813aa-01dd-11e7-a012-0242ce94d92a'
with uid 0 and gid 0
I0305 22:51:42.986593 10136 linux_launcher.cpp:421] Launching container
e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a and cloning with namespaces CLONE_NEWNS
{code}
{code}
ls -la
/export/intssd/mesos-slave/workdir/slaves/85150805-a201-4b23-ab21-b332a458fc97-S10/frameworks/e9d0e39e-b67d-4142-b95d-b0987998eb92-/executors/md_hdfs_journal.23f813ab-01dd-11e7-a012-0242ce94d92a/runs/e978d4eb-5ec1-44ad-b50a-9ae6bfe1065a/
drwxr-xr-x 3 someappuser someappgroup 4096 22:51 .
drwxr-xr-x 3 root root4096 22:51 ..
drwxr-xr-x 2 root root4096 22:51 data
-rw-r--r-- 1 root root 169 22:51 stderr
-rw-r--r-- 1 root root 183012 23:00 stdout
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MESOS-1971) Switch cgroups_limit_swap default to true
[ https://issues.apache.org/jira/browse/MESOS-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James DeFelice updated MESOS-1971: -- Labels: mesosphere (was: ) > Switch cgroups_limit_swap default to true > - > > Key: MESOS-1971 > URL: https://issues.apache.org/jira/browse/MESOS-1971 > Project: Mesos > Issue Type: Improvement >Reporter: Anton Lindström >Priority: Minor > Labels: mesosphere > > Switch cgroups_limit_swap to true per default, see MESOS-1662 for more > information. > Thanks! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
