Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8E7F18866 for ; Tue, 29 Dec 2015 11:49:50 +0000 (UTC) Received: (qmail 29477 invoked by uid 500); 29 Dec 2015 11:49:50 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 29436 invoked by uid 500); 29 Dec 2015 11:49:50 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 29426 invoked by uid 99); 29 Dec 2015 11:49:50 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Dec 2015 11:49:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 00953C0442 for ; Tue, 29 Dec 2015 11:49:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qImoNEJZpNdO for ; Tue, 29 Dec 2015 11:49:39 +0000 (UTC) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id E37AA20185 for ; Tue, 29 Dec 2015 11:49:38 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id o11so163482026qge.2 for ; Tue, 29 Dec 2015 03:49:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=C88ImPARBxS3CVfjzM/Zoo5/khnTKeVRyEXvntOFdE0=; b=SG9ws9y8Fp8p8i54XE0WLawmREMRI7FuvHUtfap/EWws6uMNu76zoSXO0jkT4as3+y T+zUSW4tjzu1rg0bUxZxntcihgWHIoNJh3MekipYwacJqswrCQcYFApYVsFb/6yyzQne JiEVGEDikiyM+jsMpefQ5JzhssWzDW8/H8zsXMIFkdyyOHQYuvPu+MewXSQT/ohToCN5 DIl4Z5J1RYBHGB/wvDlcBbQN0rvaSeqTpvUZsZZcMk/KF+ZyjMy5AaUCsBb7ntbOjFQ/ X2MwcJPvQTCiFGKrosdPlz5PWZ0BAWLujrY9JkmN6h+iaSFsfRZXu32v7gMrZqeizodw dk2w== X-Received: by 10.140.29.131 with SMTP id b3mr75935749qgb.50.1451389772051; Tue, 29 Dec 2015 03:49:32 -0800 (PST) Received: from [192.168.1.108] (cpe-67-253-81-92.maine.res.rr.com. [67.253.81.92]) by smtp.gmail.com with ESMTPSA id d62sm28927687qga.41.2015.12.29.03.49.31 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 29 Dec 2015 03:49:31 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: upgradeHelper question From: Brian Jeltema In-Reply-To: Date: Tue, 29 Dec 2015 06:49:29 -0500 Cc: Tommy McNeese Content-Transfer-Encoding: quoted-printable Message-Id: <4FE237CB-581B-48A7-B6B5-B38EA7A24194@gmail.com> References: <39D311FE-093E-45E2-8A84-D2B317A29D7C@gmail.com> To: "user@ambari.apache.org" X-Mailer: Apple Mail (2.3096.5) Yes, I used the JSON catalog file and followed the procedure in the = docs. These problems have all been resolved. The primary fix seems to have been doing a =E2=80=98yum clean=E2=80=99 on all of the cluster nodes. = The cluster upgrade is complete with all services green and no alerts. Brian > On Dec 29, 2015, at 3:00 AM, Alejandro Fernandez = wrote: >=20 > Hi Brian, >=20 > Did you use the UpgradeCatalog_2.1_to_2.2.json file? >=20 > python upgradeHelper.py --hostname $HOSTNAME --user $USERNAME = --password > $PASSWORD --clustername $CLUSTERNAME --fromStack=3D2.1 --toStack=3D2.2.x= > --upgradeCatalog=3DUpgradeCatalog_2.1_to_2.2.x.json update-configs >=20 >=20 > As described in > = http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.2.0/bk_upgrading_hdp_m= a > nually/content/ch_upgrade_2_1.html >=20 > = http://docs.hortonworks.com/HDPDocuments/Ambari-2.0.1.0/bk_upgrading_Ambar= i > /content/_upgrading_the_hdp_stack_from_21_to_22.html >=20 >=20 > Do you have a backup of the Ambari DB? >=20 > Thanks, > Alejandro >=20 > On 12/19/15, 7:07 AM, "Brian Jeltema" wrote: >=20 >> I=C2=B9m trying to upgrade from the HDP 2.1 to HDP 2.2 stack. = Somewhere, I >> must have made a mistake >> because some configurations seem to be wrong (for instance, the wrong >> class name for the timeline server, >> and when I try to start region servers they complain that JAVA_HOME = is >> undefined and they cannot find the JDK). >>=20 >> I tried rerunning the upgradeHelper.py update-configs command a = second >> time, but=20 >> it fails with lots of verification errors. Can this script only be = run >> once? How do I >> determine if my configurations are the correct ones? >>=20 >> Thanks. >>=20 >> Brian >=20 >=20