Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Cloudmanager execution (Path A)

avatar
Explorer

Hi community,

 

I'm doing my first Path A installation, downloaded the cloudera manager binairy, sent it to a folder on my target server, changed the rights doing chmod u+x. And when I want to start doing "./cloudera-manager-installer.bin", I got the following message :

 

"Cloudera Manager 5
NOTICE: The umask 0077 is too restrictive. It must be 0022 at most for this installer to work.
[hit enter]"

 

Has anybody went to this? I tried other rights combinations without success.

 

I need to setup this small cluster for my development team.

 

Any help would be appreciated!

1 ACCEPTED SOLUTION

avatar
Explorer

My directory issue was due to write rights not present on /usr/shar and not enough place in /opt.

View solution in original post

5 REPLIES 5

avatar
Explorer

Addtional information on my case :

 

[root@sd061572-app-01 binaires]# chmod u+x cloudera-manager-installer.bin
[root@sd061572-app-01 binaires]# whoami
root
[root@sd061572-app-01 binaires]# ls -l
total 500
-rwxr--r-- 1 admcap admcap 510587 May 29 15:16 cloudera-manager-installer.bin
[root@sd061572-app-01 binaires]# ./cloudera-manager-installer.bin
Cloudera Manager 5
NOTICE: The umask 0077 is too restrictive. It must be 0022 at most for this installer to work.
[hit enter]

Incomplete installation. We will revert any changes we made.

[root@sd061572-app-01 binaires]#

avatar
If you run the umask command, I'm guessing it'll say 0077 instead of 0022. You need it to be 0022.

http://en.wikipedia.org/wiki/Umask

avatar
Explorer

Thank you, it went fine, I'm stuck with directory creation for Java, trying to look at this...

avatar
Explorer

I searched for the cause of "NOTICE: Directory creation failed" at the beginning of Path Installation using root. Didn't find any explanation. Any idea?

avatar
Explorer

My directory issue was due to write rights not present on /usr/shar and not enough place in /opt.