Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Issue with accessing Hue file manager

Highlighted

Issue with accessing Hue file manager

New Contributor

Hi,

 

I am trying to access file manager in Hue the system shows the following error:

 

 

Cannot access: /user/cloudera. The HDFS REST service is not available. Note: You are a Hue admin but not a HDFS superuser (which is "hdfs").

('Connection aborted.', error(111, 'Connection refused'))

The terminal is also showing the error

 

[cloudera@quickstart ~]$ hdfs dfs -put testfile.txt
put: Call From quickstart.cloudera/127.0.0.1 to quickstart.cloudera:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused

 

 

Please tell me step by step procedure for removing this error from my system.

 

Thanks,

Sonia

5 REPLIES 5
Highlighted

Re: Issue with accessing Hue file manager

Master Collaborator
Sounds like the HDFS NameNode service has stopped. I'd run 'sudo hadoop-hdfs-namenode restart', and 'sudo hadoop-hdfs-namenode status' to check it. Also check hadoop-hdfs-datanode to be safe. If the problem continues, check the logs in /var/log/hadoop-hdfs for any errors.

Re: Issue with accessing Hue file manager

New Contributor

Hi Sean,

 

Thanks for the reply.

 

I am new to Hadoop and do not have programming background. Please tell me step by step process on how to access namenode and what to do to solve this issue.

 

Thank you,

Sonia

Highlighted

Re: Issue with accessing Hue file manager

Master Collaborator

There's an icon of a black command prompt at the top of the screen. Clicking that will open a terminal. You'll need to enter the commands above in that window. Run 'sudo service hadoop-hdfs-namenode restart', and then when it's done, confirm that it is running successfully with 'sudo service hadoop-hdfs-namenode status'. I would then run 'sudo service hadoop-hdfs-datanode status' to confirm the DataNode is also running. If it's not, also restart that with 'sudo service hadoop-hdfs-datanode restart'. Alternatively, rebooting the VM causes all services to restart in the proper order - so assuming your current problem is just due to some little hiccup, that would also fix the problem. '

Highlighted

Re: Issue with accessing Hue file manager

New Contributor

Hi Sean,

 

I tried running the commands, I get these replies:

 

[cloudera@quickstart ~]$ sudo service hadoop-hdfs-namenode restart
no namenode to stop
Stopped Hadoop namenode:                                   [  OK  ]
starting namenode, logging to /var/log/hadoop-hdfs/hadoop-hdfs-namenode-quickstart.cloudera.out
log4j:ERROR Could not find value for key log4j.appender.RFA
log4j:ERROR Could not instantiate appender named "RFA".
Failed to start Hadoop namenode. Return value: 1           [FAILED]
[cloudera@quickstart ~]$ sudo service hadoop-hdfs-namenode status
Hadoop namenode is dead and pid file exists                [FAILED]

 

 

Highlighted

Re: Issue with accessing Hue file manager

Master Collaborator
No idea what's causing those messages to show up: there's no 'RFA' appender
in any service that Hadoop should be reading configuration from in the VM
and I've never seen this before. Have you done anything to modify any of
the configuration? I'd look into the log files in /var/log/hadoop-hdfs to
see if you can find other error messages that indicate what's gone wrong,
or perhaps start with a new instance of the VM.

Don't have an account?
Coming from Hortonworks? Activate your account here