Member since
05-22-2017
56
Posts
12
Kudos Received
2
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1488 | 11-29-2021 01:52 AM |
11-29-2021
01:52 AM
1 Kudo
Yes, you need to add one user at a time, You cannot add multiple users in a single JSON file.
... View more
11-17-2021
07:20 AM
Please try the below steps, this can happen if /tmp mount point is mounted with noexec option... - Create a new directory under any directory(ex /data/tmp) with exec permission and to test provide 777 permissions for newly created dir.
- Update the config in zeppelin config as below and restart the zeppelin.
CM UI --> Zeppelin --> Config --> "Zeppelin Server Advanced Configuration Snippet (Safety Valve) for zeppelin-conf/zeppelin-env.sh" --> Add export ZEPPELIN_JAVA_OPTS="-Djava.io.tmpdir=<directory name>"
example: export ZEPPELIN_JAVA_OPTS="-Djava.io.tmpdir=/data/tmp"
- Save changes and restart zeppelin server and verify the login
... View more
08-20-2019
03:25 AM
1 Kudo
Hi, We don't share personal information like contacts, As you are facing Ambari Server issue and Agents issue is resolved, Please open a new question for Ambari Server, Also, check the Ambari Server logs you see some exceptions, attach those exceptions.
... View more
10-05-2017
01:06 PM
2 Kudos
Cloudbreak contains mini KNOX which is not managed by Ambari. Below are the steps to replace Self Signed Certificate with CA Signed Certificates Step 1: Remove below two entries from /usr/hdp/current/knox-server/conf/gateway-site.xml and save it. <property>
<name>gateway.signing.keystore.name</name>
<value>signing.jks</value>
</property>
<property>
<name>gateway.signing.key.alias</name>
<value>signing-identity</value>
</property> Step 2: Take a backup of original configuration: [~]$ cd /usr/hdp/current/knox-server/data/security/keystores/
[~]$ mkdir backup
[~]$ mv __gateway-credentials.jceks gateway.jks backup/ Step 3: Create a keystore in PKCS12 format from your private key file, certificate, Intermediate certificate and root certificate [~]$ openssl pkcs12 -export -out corp_cert_chain.pfx -inkey <private-key>.key -in <cert.cer> -certfile <root_intermediate>.cer -certfile <root_ca>.cer Step 4: Regenerate Master Key. Use the same password for master key and keystore. # rm -rf /usr/hdp/current/knox-server/data/security/master
# ls -l /usr/hdp/current/knox-server/data/security/master
# /usr/hdp/current/knox-server/bin/knoxcli.sh create-master Step 5: Generate Knox keystore [~]$ cp corp_cert_chain.pfx /usr/hdp/current/knox-server/data/security/keystores/
[~]$ cd /usr/hdp/current/knox-server/data/security/keystores/
[~]$ keytool -importkeystore -srckeystore corp_cert_chain.pfx -srcstoretype pkcs12 -destkeystore
gateway.jks -deststoretype jks -srcstorepass <src-keystore-password> -deststorepass <knox-master-secret> -destkeypass <knox-master-secret> Step 6: Replace the alias of keystore keytool -changealias -alias "1" -destalias "gateway-identity" -keypass keypass -keystore gateway.jks-storepass storepass Step 7: Store the keystore password in jceks file [~]$ /usr/hdp/current/knox-server/bin/knoxcli.sh create-alias gateway-identity-passphrase
--value <knox-master-secret> Step 8: Restart Knox, you should see the below-highlighted lines in your knox logs [~]$ tail –f /var/log/knox/gateway.log
... View more
Labels:
08-13-2018
08:10 AM
The correct way is add following context to default.xml <param>
<name>SOLR</name>
<value>maxFailoverAttempts=3;failoverSleep=1000;enabled=true</value>
</param>
<service>
<role>SOLR</role>
<url>http://<solr_host1>:8886/solr</url>
<url>http://<solr_host2>:8886/solr</url>
</service> and use below URL for access Solr UI: https://<knox_host>:8443/gateway/default/solr/index.html#/
... View more
04-10-2019
04:03 AM
same issue with me please suggest some solution. @benoit moisan did you find any solution??? Please guide me.
... View more