Facing the same problem   [root@hdp1 data]# systemctl status hadoop-hdfs-namenode ● hadoop-hdfs-namenode.service - LSB: Hadoop namenode Loaded: loaded (/etc/rc.d/init.d/hadoop-hdfs-namenode; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2019-03-28 11:50:58 UTC; 3h 8min ago Docs: man:systemd-sysv-generator(8) Process: 3230 ExecStart=/etc/rc.d/init.d/hadoop-hdfs-namenode start (code=exited, status=1/FAILURE) Mar 28 11:50:49 hdp1 systemd[1]: Starting LSB: Hadoop namenode... Mar 28 11:50:49 hdp1 su[3235]: (to hdfs) root on none Mar 28 11:50:49 hdp1 hadoop-hdfs-namenode[3230]: starting namenode, logging to /var/log/hadoop-hdfs/hadoop-hdfs-namenode-hdp1.out Mar 28 11:50:58 hdp1 hadoop-hdfs-namenode[3230]: Failed to start Hadoop namenode. Return value: 1[FAILED] Mar 28 11:50:58 hdp1 systemd[1]: hadoop-hdfs-namenode.service: control process exited, code=exited status=1 Mar 28 11:50:58 hdp1 systemd[1]: Failed to start LSB: Hadoop namenode. Mar 28 11:50:58 hdp1 systemd[1]: Unit hadoop-hdfs-namenode.service entered failed state. Mar 28 11:50:58 hdp1 systemd[1]: hadoop-hdfs-namenode.service failed. [root@hdp1 data]# systemctl start hadoop-hdfs-namenode Job for hadoop-hdfs-namenode.service failed because the control process exited with error code. See "systemctl status hadoop-hdfs-namenode.service" and "journalctl -xe" for details. ... View more