- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Starting_service
- Labels:
-
Apache Hadoop
-
HDFS
Created on ‎09-11-2013 08:21 AM - edited ‎09-16-2022 01:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
At the time of starting individual roles we faced following exception:
+ exec /usr/lib/hadoop-hdfs/bin/hdfs --config /run/cloudera-scm-agent/process/18-hdfs-NAMENODE namenode /usr/lib/cmf/service/hdfs/hdfs.sh: line 360: /usr/lib/hadoop-hdfs/bin/hdfs: No such file or directory Can anyone help me please.
Thanks in advance.
Created ‎09-17-2013 09:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Nag.
Did you, by any chance recently switch over to using "Parcels" for your CDH cluster? If you upgraded to parcels, you also must go back and remove all the old CDH RPMs manually and also update your symlinks to the new parcels locations. It's one of the last steps in the upgrade doc and easy to overlook. If CM still has it's symlinks pointed to the old locations for CDH commands in /usr/lib, those won't be there if the RPMs were removed. You should be able to update your symlinks by restarting the cloudera agents on all machines:
service cloudera-scm-agent restart
HTH,
Clint
Created ‎09-17-2013 09:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Nag.
Did you, by any chance recently switch over to using "Parcels" for your CDH cluster? If you upgraded to parcels, you also must go back and remove all the old CDH RPMs manually and also update your symlinks to the new parcels locations. It's one of the last steps in the upgrade doc and easy to overlook. If CM still has it's symlinks pointed to the old locations for CDH commands in /usr/lib, those won't be there if the RPMs were removed. You should be able to update your symlinks by restarting the cloudera agents on all machines:
service cloudera-scm-agent restart
HTH,
Clint
Created ‎09-19-2013 12:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is helpful to me.You are appreciated.
Thanks for your help.
