You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

使用Cloudera Manager 5部署HDFS后,无法访问http://localhost:50070/求助

Hey there, let's troubleshoot this HDFS web UI issue step by step. I've dealt with similar problems when setting up Cloudera Manager 5 before, so here are the most common fixes to try:

Troubleshooting HDFS Web UI (Port 50070) Access Issues in Cloudera Manager 5

1. First, confirm the NameNode service is running

  • Log into your Cloudera Manager dashboard (typically at http://<your-cm-host>:7180)
  • Navigate to the HDFS service page and check the Status of the NameNode role. If it's stopped or in a degraded state, restart it directly from the dashboard.
  • You can also verify via command line on the NameNode host:
    sudo service hadoop-hdfs-namenode status
    
    If it's not running, start it with:
    sudo service hadoop-hdfs-namenode start
    

2. Check if port 50070 is actually listening

Sometimes the service is up but fails to bind to the correct port. Run this on the NameNode host to confirm:

netstat -tulpn | grep 50070

You should see an entry marked LISTEN linked to the NameNode process. If nothing shows up, double-check the HDFS config in Cloudera Manager:

  • Go to HDFS service > Configuration > Search for dfs.namenode.http-address
  • Make sure the value is set to <your-namenode-host>:50070 (if you're accessing from another machine, avoid using localhost here; if you're on the same host, confirm localhost resolves correctly)

3. Rule out firewall/network blocks

  • If accessing from a remote machine, ensure the NameNode host's firewall allows inbound traffic on 50070:
    For RHEL/CentOS systems:
    sudo firewall-cmd --add-port=50070/tcp --permanent
    sudo firewall-cmd --reload
    
    For Ubuntu/Debian:
    sudo ufw allow 50070/tcp
    sudo ufw reload
    
  • If on the same host but getting "connection refused", run ping localhost to confirm it resolves to 127.0.0.1 or your machine's valid IP.

4. Dig into NameNode logs for errors

If the service shows as running but the UI is unreachable, logs will tell you why. In Cloudera Manager:

  • Go to HDFS service > Instances > Click the NameNode role > Logs
  • Look for errors about the HTTP server failing to start, port conflicts, or permission issues.
  • You can also view the log file directly on the host (usually at /var/log/hadoop-hdfs/hadoop-hdfs-namenode-<hostname>.log)

5. Check for proxy interference

Sometimes Cloudera Manager's proxy settings can block UI access:

  • Go to Cloudera Manager > Administration > Settings > Search for "proxy"
  • Ensure no unintended proxy configurations are interfering with the HDFS UI access

If none of these steps fix the issue, share the output of the netstat command and any error snippets from the NameNode logs, and we can dig deeper!

内容的提问来源于stack exchange,提问作者Bata Omou

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.26 09:53:16