About Karasten

Karasten · ‎06-06-2014

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

Karasten · ‎05-29-2014

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?

Karasten · ‎05-29-2014

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

Karasten · ‎05-29-2014

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]#

Karasten · ‎05-29-2014

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!

Online	Offline
Last Visited	‎08-06-2014 05:36 AM

Member Since	‎05-29-2014 05:49 AM
Last Visited	‎08-06-2014 05:36 AM
Posts	10

Cloudera Community

Re: Cloudmanager execution (Path A)

Re: Cloudmanager execution (Path A)

Re: Cloudmanager execution (Path A)

Re: Cloudmanager execution (Path A)

Re: Cloudmanager execution (Path A)

Cloudmanager execution (Path A)