About prashant_band

prashant_band · ‎08-02-2018

This is permission issue for postgresql user, I faced this issue on docker environment, I managed it by using Mariadb as Database for Ambari. You need to manage user and permission very carefully with Postgresql. (Using mariadb its easy)

prashant_band · ‎07-27-2018

After installing Ambari, reboot your server(OS) and wait for loading all its services. Then try installing again, but still you may face same problem when Installation is in progress. So right now the solution we found is restarting "ambari-server" and "ambari-agent"

prashant_band · ‎07-17-2018

[ RESOLVED ] Gone through same issue only when we are using oVirt Virtualization For our cluster deployment. Only following solution resolved the problem (Thanks to @bing lv and @Deven Fan: By adding below config in [security] section of vi /etc/ambari-agent/conf/ambari-agent.ini force_https_protocol=PROTOCOL_TLSv1_2 vi /etc/python/cert-verification.cfg [https] verify=disable

prashant_band · ‎07-17-2018

[ RESOLVED ] Gone through same issue only when we are using oVirt Virtualization For our cluster deployment. Only following solution resolved the problem (Thanks to @bing lv and @Deven Fan: By adding below config in [security] section of vi /etc/ambari-agent/conf/ambari-agent.ini force_https_protocol=PROTOCOL_TLSv1_2 vi /etc/python/cert-verification.cfg [https] verify=disable

prashant_band · ‎04-20-2018

@All I used temporary solution by creating cron job, no admin require everytime to remove directory: File: rmstaging.sh su - hdfs -c 'hdfs dfs -ls /tmp/yarn' > /dev/null 2>&1 if [ $? == 0 ] then su - hdfs -c 'hdfs dfs -rmdir /tmp/yarn/staging/.tez' > /dev/null 2>&1 su - hdfs -c 'hdfs dfs -rmdir /tmp/yarn/staging' > /dev/null 2>&1 su - hdfs -c 'hdfs dfs -rmdir /tmp/yarn' > /dev/null 2>&1 fi

prashant_band · ‎04-20-2018

Kerberos is not active, but problem is in OS user I guess.

prashant_band · ‎03-05-2018

Not yet, but I have written shell script which clears the staging directory created by any user. It is not a complete solution but my multiple users can now run Jobs without need of admin to clear staging directory every time.

prashant_band · ‎12-17-2017

${user.name} is replaced with "yarn" which is not a current user who submits the jot. This path or /user/${user.name}/.staging didnt worked for me please help.

prashant_band · ‎12-17-2017

job.txt No staging directory work correctly after setting for these two paths: DEFAULT /tmp/${user.name}/staging NEW /user/${user.name}/.staging ${user.name} is replaced with "yarn" which is not a current user who is executing a Pig Job. In my case ${user.name} should be replaced with "training" user to get correct permission ERROR org.apache.pig.backend.hadoop.executionengine.tez.TezSessionManager - Exception while waiting for Tez client to be ready org.apache.tez.dag.api.TezUncheckedException: org.apache.hadoop.security.AccessControlException: Permission denied: user=training, access=WRITE, inode="/user/yarn/.staging":hdfs:hdfs:drwxr-xr-x

Online	Offline
Last Visited	‎08-12-2018 01:12 PM

Date Registered	‎12-17-2017 02:28 PM
Last Visited	‎08-12-2018 01:12 PM
Total Messages Posted	9
Total Kudos Received	9

Re: ambari server setup faild

Re: Ambari 2.7 web hangs at first step installa...

Re: Openssl error upon host registration

Re: OpenSSL compatibility

Re: Pig on Tez fails due to Permission denied on s...

Re: Pig on Tez fails due to Permission denied on s...

Re: Pig on Tez fails due to Permission denied on s...

Re: Pig on Tez fails in multi user cluster

Pig on Tez fails due to Permission denied on stagi...