Created 07-18-2017 06:52 PM
I found that many commands will fail with the following permission denied error with Cloudera Manager 5.12
++ printf '! -name %s ' cloudera-config.sh httpfs.sh hue.sh impala.sh sqoop.sh supervisor.conf '*.log' hdfs.keytab '*jceks' + find /run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format -type f '!' -path '/run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format/logs/*' '!' -name cloudera-config.sh '!' -name httpfs.sh '!' -name hue.sh '!' -name impala.sh '!' -name sqoop.sh '!' -name supervisor.conf '!' -name '*.log' '!' -name hdfs.keytab '!' -name '*jceks' -exec perl -pi -e 's#{{CMF_CONF_DIR}}#/run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format#g' '{}' ';' Can't open /run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format/config.zip: Permission denied. Can't open /run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format/proc.json: Permission denied.+ make_scripts_executable + find /run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format -regex '.*\.\(py\|sh\)$' -exec chmod u+x '{}' ';' + '[' DATANODE_MAX_LOCKED_MEMORY '!=' '' ']' + ulimit -l + export HADOOP_IDENT_STRING=hdfs + HADOOP_IDENT_STRING=hdfs + '[' -n '' ']' + '[' mkdir '!=' format-namenode ']' + acquire_kerberos_tgt hdfs.keytab + '[' -z hdfs.keytab ']' + '[' -n '' ']' + '[' validate-writable-empty-dirs = format-namenode ']' + '[' file-operation = format-namenode ']' + '[' bootstrap = format-namenode ']' + '[' failover = format-namenode ']' + '[' transition-to-active = format-namenode ']' + '[' initializeSharedEdits = format-namenode ']' + '[' initialize-znode = format-namenode ']' + '[' format-namenode = format-namenode ']' + '[' -z /dfs/nn ']' + for dfsdir in '$DFS_STORAGE_DIRS' + '[' -e /dfs/nn ']' + '[' '!' -d /dfs/nn ']' + CLUSTER_ARGS= + '[' 2 -eq 2 ']' + CLUSTER_ARGS='-clusterId cluster8' + '[' 3 = 5 ']' + '[' -3 = 5 ']' + exec /usr/lib/hadoop-hdfs/bin/hdfs --config /run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format namenode -format -clusterId cluster8 -nonInteractive /usr/lib64/cmf/service/hdfs/hdfs.sh: line 273: /usr/lib/hadoop-hdfs/bin/hdfs: No such file or directory
Seems this is a problem caused by a bug fix since 5.9
Did anyone encounter this in recent versions?
[root@c53 ~]# ls -l /var/run/cloudera-scm-agent/process/77-hdfs-NAMENODE-format/ total 88 -rwxr----- 1 hdfs hdfs 2149 Jul 19 09:40 cloudera_manager_agent_fencer.py -rw-r----- 1 hdfs hdfs 30 Jul 19 09:40 cloudera_manager_agent_fencer_secret_key.txt -rw-r----- 1 hdfs hdfs 353 Jul 19 09:40 cloudera-monitor.properties -rw-r----- 1 hdfs hdfs 316 Jul 19 09:40 cloudera-stack-monitor.properties -rw------- 1 root root 8868 Jul 19 09:40 config.zip -rw-r----- 1 hdfs hdfs 3460 Jul 19 09:40 core-site.xml -rw-r----- 1 hdfs hdfs 12 Jul 19 09:40 dfs_hosts_allow.txt -rw-r----- 1 hdfs hdfs 0 Jul 19 09:40 dfs_hosts_exclude.txt -rw-r----- 1 hdfs hdfs 1388 Jul 19 09:40 event-filter-rules.json -rw-r--r-- 1 hdfs hdfs 4 Jul 19 09:40 exit_code -rw-r----- 1 hdfs hdfs 0 Jul 19 09:40 hadoop-metrics2.properties -rw-r----- 1 hdfs hdfs 98 Jul 19 09:40 hadoop-policy.xml -rw------- 1 hdfs hdfs 0 Jul 19 09:40 hdfs.keytab -rw-r----- 1 hdfs hdfs 4872 Jul 19 09:40 hdfs-site.xml -rw-r----- 1 hdfs hdfs 0 Jul 19 09:40 http-auth-signature-secret -rw-r----- 1 hdfs hdfs 2246 Jul 19 09:40 log4j.properties drwxr-x--x 2 hdfs hdfs 80 Jul 19 09:40 logs -rw-r----- 1 hdfs hdfs 2470 Jul 19 09:40 navigator.client.properties -rw------- 1 root root 3879 Jul 19 09:40 proc.json -rw-r----- 1 hdfs hdfs 315 Jul 19 09:40 ssl-client.xml -rw-r----- 1 hdfs hdfs 98 Jul 19 09:40 ssl-server.xml -rw------- 1 root root 3463 Jul 19 09:40 supervisor.conf -rw-r----- 1 hdfs hdfs 187 Jul 19 09:40 topology.map -rwxr----- 1 hdfs hdfs 1549 Jul 19 09:40 topology.py