Member since
12-17-2017
9
Posts
10
Kudos Received
0
Solutions
08-02-2018
10:52 AM
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)
... View more
07-27-2018
09:13 AM
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"
... View more
07-17-2018
06:54 AM
7 Kudos
[ 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
... View more
07-17-2018
06:53 AM
1 Kudo
[ 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
... View more
04-20-2018
10:16 AM
@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
... View more
04-20-2018
10:08 AM
Kerberos is not active, but problem is in OS user I guess.
... View more
03-05-2018
11:01 AM
1 Kudo
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.
... View more
12-17-2017
03:00 PM
${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.
... View more
12-17-2017
02:57 PM
1 Kudo
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
... View more
Labels:
- Labels:
-
Apache Pig
-
Apache Tez