question Re: FAILED to start HDFS Namenode in Support Questions

question Re: FAILED to start HDFS Namenode in Support Questions https://community.cloudera.com/t5/Support-Questions/FAILED-to-start-HDFS-Namenode/m-p/48600#M52126 Since the exception is <PRE>2016-09-23 10:33:39,098 WARN org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Encountered exception loading fsimage java.io.FileNotFoundException: /dfs/nn/current/VERSION (Permission denied) at java.io.RandomAccessFile.open(Native Method)</PRE>the NameNode cannot start due to an inability to load fsimage.  fsimage cannot be loaded since there is no VERSION file (hdfs user cannot see it). I would check permissions on your HDFS local disk directories on the NameNode.  To resolve the issue in the exception, make sure that the VERSION file is owned by "hdfs" user... like this: -rw-r--r-- 1 hdfs hdfs 172 Nov 7 14:37 /dfs/nn/current/VERSION I hope that is the only issue; fixing this may lead to other issues due to permissions if something happened.If the owner of the file is shown as a number, that would indicate the OS cannot resolve the file's owner id with a user.   Fri, 16 Dec 2016 16:47:13 GMT bgooley 2016-12-16T16:47:13Z