The problem was with the FSImage file (the last one), which was corrupted and didn't allow the hdfs namenode service to start. To understand if you have my same issue: List the services and examin which one are failing. HDFS namenode probably will be there with a FAILED status Look for the open ports: 50070 (or the one you put in the conf file inside /etc/hdfs/conf... ) won't be open, hence all the services that connect to namenode receive a "Connection Refused" error. Hbase will give a "znode == null" error look for the namenode logs under /var/logs/hdfs/ *namenode*.out and look where the FSImage files are Go there: if you have one FIImage file only, as far as I know, you're screwed. If you have more than one: deleted the last one, restart the service and let the hdfs rebuild the correct FSImage from the Edit file either restart the machine or restart all of the services as specified on the Cloudera docs. Hope this will save you time.
... View more
