Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2731 | 04-27-2020 03:48 AM | |
| 5289 | 04-26-2020 06:18 PM | |
| 4459 | 04-26-2020 06:05 PM | |
| 3584 | 04-13-2020 08:53 PM | |
| 5386 | 03-31-2020 02:10 AM |
02-27-2018
12:56 PM
@Michael Bronson Yes that should be fine.
... View more
02-27-2018
11:25 AM
1 Kudo
@Michael Bronson Unlike "ambari-server upgrade" command , unfortunately there is no "downgrade" command available. . For Downgrading ambari all you need is to have the Database Dump of the previous version. (I mean if you want to downgrade to Ambari 2.5 then you should have the DB dump of the state where ambari server version was 2.5) AND "/etc/ambari-server/conf" and "/etc/ambari-agent/conf" directories backups, Sothat you do not need to configure SSL/LDAP/Kerberos ...etc setups again. Backup the current config & DB: Please collect a latest ambari DB dump of the upgraded version (for safety) and keep a backup of "/etc/ambari-server/conf" and "/etc/ambari-agent/conf" directories. . Ambari server can be downgraded as following: 1. Stop the ambari-server # ambari-server stop 2. Stop all the ambari-agents on all hosts. # ambari-agent stop 3. Download the ambari.repo of the downgraded version on all agent hosts and ambari server host. Example: # wget -nv http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.4.2.0/ambari.repo -O /etc/yum.repos.d/ambari.repo 4. Then take a backup of "/etc/ambari-server/conf" and "/etc/ambari-agent/conf" directories (for backup). 5. Erase the ambari Binaries from Ambari Server and Ambari Agent hosts like (basically cleaning up the Ambari Server and agent binaries) yum remove ambari-server ambari-agent
rm -f /usr/sbin/ambari*
rm -f /usr/lib/python2.6/site-packages/ambari_commons
rm -f /usr/lib/python2.6/site-packages/ambari_server
rm -rf /usr/lib/python2.6/site-packages/resource_management
rm -rf /usr/lib/python2.6/site-packages/ambari_jinja2
rm -f /usr/lib/python2.7/site-packages/ambari_commons
rm -f /usr/lib/python2.7/site-packages/ambari_server
rm -rf /usr/lib/python2.7/site-packages/resource_management
rm -rf /usr/lib/python2.7/site-packages/ambari_jinja2
rm -rf /var/lib/ambari-server
rm -rf /var/lib/ambari-agent/
rm -rf /usr/lib/ambari-agent/
rm -rf /usr/lib/ambari-server/ 6. Perform yum cleanup # yum clean all 7. Import the OLD Database Dump of previous ambari version to the Database. (for example ambari 2.4.2 DB dump) # su postgres -c 'psql -c "drop database ambari" '
# su postgres -c 'psql -c "create database ambari" '
# su postgres -c 'psql -f ./ambari_old_242.sql -d ambari' 8. Install ambari-server and ambari agents (agent on all hosts) # yum install ambari-server ambari-agent -y (On Ambari Server)
# yum install ambari-agent -y (On all cluster nodes) 9. Run the ambari setup to point to the same Database where we imported the old DB dump. (OR) restore the previously saved Ambari 2.4.2 "/etc/ambari-server/conf" and "/etc/ambari-agent/conf" directories backups. # ambari-server setup --databasehost=standaloneambari1.example.com --databasename=ambari --databaseusername=ambari --postgresschema=ambari --databasepassword=bigdata --databaseport=5432 --database=postgres -s
10. Start ambari agents and ambari server. # ambari-server start
# ambari-agent start . NOTE: If you have setup LDAP or Kerberos for ambari server then you will have to runt he ambari-server setup-security option manually or get the specific properties from the Upgraded configs. In case of SSL configuration you will need to have the old SSL keystore/certificates or will need to recreate that config. (OR) restore the previously saved Ambari 2.4.2 "/etc/ambari-server/conf" and "/etc/ambari-agent/conf" directories backups. . NOTE: these above steps will take care of Ambari Downgrade, Which is not recommended until unless there is no other option. The above steps will just take care of Downgrading the ambari server, But it might cause a Ambari Metrics Collector Data loss (Because there is no standard way of downgrading the dependent components like Ambari Infra, Ambari Metrics Collector...) So better do not downgrade until there is no other option. .
... View more
02-27-2018
04:59 AM
1 Kudo
@L V As you got message like "Keystore was tampered with, or password was incorrect." which indicates that you might have entered incorrect storepassword while importing the ambari server keystore to knox keystore. You can verify the "gatewar.jks" by listing the certificates present in it. Please try "-list" command to see if ambari server certificate is imported to the knox truststore or not? # /usr/jdk64/jdk1.8.0_112/bin/keytool -list -v -keystore /var/lib/knox/data-2.6.4.0-91/security/keystores/gateway.jks
Enter keystore password: admin
.
... View more
02-27-2018
02:39 AM
@L V By any chance are you specifying the HTTPS protocol in the Knox topology for the Ambari Server URL (like. https://$AMBARI_HOST:8080) . Please check if you are running your ambari server on HTTPS ? If yes then please import the Ambari Server's certificate to the Knox keystore.
... View more
02-27-2018
01:30 AM
@L V The above Snippet is also not complete. We need to see the complete error from where it begin ... till end of this stack trace to understand which API is causing this error. Also please let us know if you have configured truststore in ambari server? Is this snippet appearing in the "ambari-server.log" ? When exactly are we getting this error? While Accessing any specific view (Like Capacity Scheduler View)? Or while accessing ambari UI ? Is your ambari server listening on SSL port ?
... View more
02-27-2018
01:23 AM
@L V In which log do you see this error now? Can you please share the complete log snippet so that we will know what's wrong? When are you getting this error ? Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target In general this error indicates that the truststore is not configured and it does not have the imported certificate. If you notice the above error on ambari server log then please check if you have configured truststore for ambari? https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.3/bk_ambari-security/content/set_up_truststore_for_ambari_server.html .
... View more
02-26-2018
11:39 PM
@Swaapnika Guntaka Good to know that your current issue is resolved. It will be great if you can mark this HCC thread as answered by clicking the "Accept" link on the correct answer, that way other HCC users can quickly find the solution when they encounter same error. . Regarding your JDK issue, Can you please clarify what do you mean by "Somehow my jdk got corrupted" ? how do you find that JDK got corrupted? Do you see any JDK crash report like (hs_err_pid" ...) Or do you see any other JDK level errors?
... View more
02-26-2018
11:10 PM
@Amira khalifa As this issue is resolved and it was because of the classname issue of the driver class, hence can you please mark this HCC thread as Answered by clicking on the "Accept" button that way the mentioned troubleshooting steps can be useful for other HCC users to quickly find/troubleshoot the issue when they see similar issue.
... View more
02-26-2018
11:07 PM
@Swaapnika Guntaka As the error is coming from the following piece of code: https://github.com/apache/hadoop/blob/release-2.7.3-RC1/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/SecretManager.java#L146-L147 Which is using Java "KeyGenerarot" to generate "HmacSHA1" tokens: https://docs.oracle.com/javase/7/docs/api/javax/crypto/KeyGenerator.html So it looks like your JDK is not having the JCE packages installed. Can you please check if recently your JDK is upgraded (Or if the JAVA_HOME) is changed which does not have the JCE installed? You can find the detailed information about JCE: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.3/bk_ambari-security/content/distribute_and_install_the_jce.html .
... View more
02-26-2018
10:32 PM
3 Kudos
@Michael Bronson Looks like due to some reason at yum level the "hadoop_" packages of 2.6.4.0-91 was not installed properly. You might want to try manually installing the "2.6.4.0-91" version of package on your own like following (please make sure that you are specifying the version in the below command as "2_6_4_0_91" ) # yum remove hadoop_2_6_4_0_91* zookeeper_2_6_4_0_91* . Also please perform a yum clean all and check if there are any pending old transactions present on the host? If Yes, then please clear then as mentioned in : https://community.hortonworks.com/questions/175762/how-to-resolve-incomplete-yum-transactions-when-pe.html?childToView=175766#comment-175766 . After that you can try from ambari UI.
... View more