Went to add back a node that was removed for maintenance, it stalled out on the CDH parcel, after succeeding on the other two parcels. The log shows "HTTP Error 404: Not Found" for a file that is clearly in the indicated location, with the same permissions as the two files that succeeded. restarting the client (stop wait start) results in a message about "There is already an active download" and then starts in again with the 404s.
There doesn't seem to be any way to stop it either. Tried rebooting the node as well.
Okay then, How about this: Does anyone know what path it's checking on the name node when I see this?
Failed to retrieve/store URL: https://<hostname>:<port>/cmf/parcel/download/CDH-6.3.3-1.cdh6.3.3.p0.1796617-el7.parcel.torrent -> /opt/cloudera/parcel-cache/CDH-6.3.3-1.cdh6.3.3.p0.1796617-el7.parcel.torrent HTTP Error 404: Not Found
Originally looking in /opt/cloudera/parcel-cache/ which has the file, noticed that /opt/cloudera/parcel-repo/ does not have the file
@Seedy There could be various reasons. You have to see the full agent logs. However to start with this issue I would suggest few sanity checks.
1)Resolve network issue related to firewall restrictions in accessing the repo files
2)Correct permissions on /opt/cloudera/ directories
3)Check and change the ownership.
$chown cloudera-scm:cloudera-scm /opt/cloudera/parcel-repo/*
4)Re - add the hosts from Cloudera Manager
However most importantly you have to see if you can download the parcels manually on the node under this dir. Please follow the below page for detailed overview.