[ 
https://issues.apache.org/jira/browse/MYRIAD-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928476#comment-15928476
 ] 

Sarjeet Singh commented on MYRIAD-252:
--------------------------------------

>> E0316 15:32:03.124871 12039 shell.hpp:107] Command 'hadoop version 2>&1' 
>> failed; this is the output:
sh: hadoop: command not found
Failed to fetch 'hdfs://csv-dcos02:9000/dist/hadoop-myriad.tgz': Failed to 
create HDFS client: Failed to execute 'hadoop version 2>&1'; the command was 
either not found or exited with a non-zero exit status: 127

@Hongtaosun, can you check the following:
1. Is hadoop installed on all mesos agents?
2. Can you run hadoop commands from agent machines? (also try "/bin/sh hadoop" 
command)
3. Can you check if HADOOP_HOME is set or you have hadoop bin location in PATH 
environment variable?

> chown: cannot access 
> '/sys/fs/cgroup/cpu/mesos/330e5ca9-b8ba-4e30-822a-817f7c905891': No such file 
> or directory
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: MYRIAD-252
>                 URL: https://issues.apache.org/jira/browse/MYRIAD-252
>             Project: Myriad
>          Issue Type: Bug
>            Reporter: yangjunfeng
>
> I have configured myriad these days and some probloms shown below:
> 14:49:45.216470 23824 fetcher.cpp:409] Fetching URI 
> 'hdfs://188.188.0.189:9000/usr/hadoop-2.7.3.tgz'
> I0123 14:49:45.216486 23824 fetcher.cpp:250] Fetching directly into the 
> sandbox directory
> I0123 14:49:45.216532 23824 fetcher.cpp:187] Fetching URI 
> 'hdfs://188.188.0.189:9000/usr/hadoop-2.7.3.tgz'
> I0123 14:49:45.851863 23824 fetcher.cpp:109] Downloading resource with Hadoop 
> client from 'hdfs://188.188.0.189:9000/usr/hadoop-2.7.3.tgz' to 
> '/var/lib/mesos/slaves/3337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/frameworks/1ff6c07d-a86c-400e-abac-e9618a5504db-0014/executors/myriad_executor1ff6c07d-a86c-400e-abac-e9618a5504db-00141ff6c07d-a86c-400e-abac-e9618a5504db-O93123337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/runs/330e5ca9-b8ba-4e30-822a-817f7c905891/hadoop-2.7.3.tgz'
> I0123 14:49:50.121711 23824 fetcher.cpp:547] Fetched 
> 'hdfs://188.188.0.189:9000/usr/hadoop-2.7.3.tgz' to 
> '/var/lib/mesos/slaves/3337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/frameworks/1ff6c07d-a86c-400e-abac-e9618a5504db-0014/executors/myriad_executor1ff6c07d-a86c-400e-abac-e9618a5504db-00141ff6c07d-a86c-400e-abac-e9618a5504db-O93123337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/runs/330e5ca9-b8ba-4e30-822a-817f7c905891/hadoop-2.7.3.tgz'
> I0123 14:49:50.121835 23824 fetcher.cpp:409] Fetching URI 
> 'http://188.188.0.189:8088/conf'
> I0123 14:49:50.121855 23824 fetcher.cpp:250] Fetching directly into the 
> sandbox directory
> I0123 14:49:50.121888 23824 fetcher.cpp:187] Fetching URI 
> 'http://188.188.0.189:8088/conf'
> I0123 14:49:50.121911 23824 fetcher.cpp:134] Downloading resource from 
> 'http://188.188.0.189:8088/conf' to 
> '/var/lib/mesos/slaves/3337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/frameworks/1ff6c07d-a86c-400e-abac-e9618a5504db-0014/executors/myriad_executor1ff6c07d-a86c-400e-abac-e9618a5504db-00141ff6c07d-a86c-400e-abac-e9618a5504db-O93123337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/runs/330e5ca9-b8ba-4e30-822a-817f7c905891/conf'
> W0123 14:49:50.139974 23824 fetcher.cpp:289] Copying instead of extracting 
> resource from URI with 'extract' flag, because it does not seem to be an 
> archive: http://188.188.0.189:8088/conf
> I0123 14:49:50.140010 23824 fetcher.cpp:547] Fetched 
> 'http://188.188.0.189:8088/conf' to 
> '/var/lib/mesos/slaves/3337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/frameworks/1ff6c07d-a86c-400e-abac-e9618a5504db-0014/executors/myriad_executor1ff6c07d-a86c-400e-abac-e9618a5504db-00141ff6c07d-a86c-400e-abac-e9618a5504db-O93123337a77d-41ff-4d1c-b9ce-6b0c971e7ba1-S2/runs/330e5ca9-b8ba-4e30-822a-817f7c905891/conf'
> chown: cannot access 
> '/sys/fs/cgroup/cpu/mesos/330e5ca9-b8ba-4e30-822a-817f7c905891': No such file 
> or directory
> env: /bin/yarn: No such file or directory
> How can I fix this problom?
> Thanks very much!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to