Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 07079200CEB for ; Sat, 12 Aug 2017 16:21:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 058C8165085; Sat, 12 Aug 2017 14:21:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 24FB2162989 for ; Sat, 12 Aug 2017 16:21:27 +0200 (CEST) Received: (qmail 87240 invoked by uid 500); 12 Aug 2017 14:21:27 -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 87230 invoked by uid 99); 12 Aug 2017 14:21:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Aug 2017 14:21:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A9ED0C00E2 for ; Sat, 12 Aug 2017 14:21:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 8MVX8WrSoajE for ; Sat, 12 Aug 2017 14:21:23 +0000 (UTC) Received: from us-smtp-delivery-102.mimecast.com (us-smtp-delivery-102.mimecast.com [63.128.21.102]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id D92835F523 for ; Sat, 12 Aug 2017 14:21:22 +0000 (UTC) Received: from CAS080-CO-3.exch080.serverpod.net (cas080-co-3.exch080.serverdata.net [199.193.204.150]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-62-HXna7_tDOcaJJLYbzzPDtQ-1; Sat, 12 Aug 2017 10:21:11 -0400 Received: from MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) by MBX080-W1-CO-5.exch080.serverpod.net (10.224.117.136) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Sat, 12 Aug 2017 07:21:07 -0700 Received: from MBX080-W4-CO-1.exch080.serverpod.net ([10.224.117.101]) by mbx080-w4-co-1.exch080.serverpod.net ([10.224.117.101]) with mapi id 15.00.1178.000; Sat, 12 Aug 2017 07:21:07 -0700 From: Sumit Mohanty To: "dev@ambari.apache.org" , Sandor Magyari CC: "user@ambari.apache.org" Subject: Re: Ambari upgrade 2.5.1.0 issue - database consistency issues for topology Thread-Topic: Ambari upgrade 2.5.1.0 issue - database consistency issues for topology Thread-Index: AQHTEtPDmvjQ0YEnGU6Aoqp55VKWYqJ/klXOgAB+jYCAALM1qw== Date: Sat, 12 Aug 2017 14:21:06 +0000 Message-ID: <1502547666261.69778@hortonworks.com> References: <1502481456392.11776@hortonworks.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-source-routing-agent: Processed MIME-Version: 1.0 X-MC-Unique: HXna7_tDOcaJJLYbzzPDtQ-1 Content-Type: multipart/alternative; boundary="_000_150254766626169778hortonworkscom_" archived-at: Sat, 12 Aug 2017 14:21:29 -0000 --_000_150254766626169778hortonworkscom_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable The error is: 2017-08-11 17:31:34,665 ERROR - Your topology request hierarchy is not comp= lete for each row in topology_host_request should exist at least one row in= topology_host_task, topology_logical_task. This looks like https://issues.apache.org/jira/browse/AMBARI-19929? The fix will prevent the inconsistency but meanwhile you need to delete som= e rows manually. If you are ok, can you open an Apache Ambari JIRA with the log file as atta= chment. Someone will be able to add instructions for cleaning up the DB. Th= at way it remains searchable for others. thanks Sumit ________________________________ From: Anandha L Ranganathan Sent: Friday, August 11, 2017 1:29 PM To: dev@ambari.apache.org Cc: user@ambari.apache.org Subject: Re: Ambari upgrade 2.5.1.0 issue - database consistency issues for= topology Sumit, Please find the attached database-check logs. On Fri, Aug 11, 2017 at 12:57 PM, Sumit Mohanty > wrote: Anandha, can you share the content of /var/log/ambari-server/ambari-server-= check-database.log thanks Sumit ________________________________ From: Anandha L Ranganathan > Sent: Friday, August 11, 2017 11:57 AM To: user@ambari.apache.org; dev@ambari.apach= e.org Subject: Ambari upgrade 2.5.1.0 issue - database consistency issues for top= ology I am trying to upgrade from ambari-2.2.1 to ambari-2.5.1. During upgrade it= didn't throw any error and it completed successfully. 1. INFO: Updating Ambari Server properties in ambari.properties ... 2. INFO: Updating Ambari Server properties in ambari-env.sh ... 3. WARNING: Original file ambari-env.sh kept 4. INFO: Fixing database objects owner 5. Ambari Server configured for Embedded Postgres. Confirm you have made= a backup of the Ambari Server database [y/n] (y)? y 6. INFO: Upgrading database schema 7. INFO: Return code from schema upgrade command, retcode =3D 0 8. INFO: Schema upgrade completed 9. Adjusting ambari-server permissions and ownership... 10. Ambari Server 'upgrade' completed successfully. 11. 12. After upgrade , I restarted the ambari-server and it throws this error. 1. [root@usw2dxdpmn02 yum.repos.d]# ambari-server restart 2. Using python /usr/bin/python 3. Restarting ambari-server 4. Waiting for server stop... 5. Ambari Server stopped 6. Ambari Server running with administrator privileges. 7. Organizing resource files at /var/lib/ambari-server/resources... 8. Ambari database consistency check started... 9. Server PID at: /var/run/ambari-server/ambari-server.pid 10. Server out at: /var/log/ambari-server/ambari-server.out 11. Server log at: /var/log/ambari-server/ambari-server.log 12. Waiting for server start........................ 13. DB configs consistency check failed. Run "ambari-server start --skip-= database-check" to skip. You may try --auto-fix-database flag to attempt to= fix issues automatically. If you use this "--skip-database-check" option, = do not make any changes to your cluster topology or perform a cluster upgra= de until you correct the database consistency issues. See /var/log/ambari-s= erver/ambari-server-check-database.log for more details on the consistency = issues. 14. ERROR: Exiting with exit code -1. 15. REASON: Ambari Server java process has stopped. Please check the logs= for more information. 16. 17. 18. I am able to restart ambari-server with --skip-database-check. What is the = reason for this error and how do I fix it? --_000_150254766626169778hortonworkscom_ Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable

The error is:


2017-08-11 17:31:34,665 ERROR - Your topology request hierarchy is not c= omplete for each row in topology_host_request should exist at least one row= in topology_host_task, topology_logical_task.


This looks like https://issues.apache.org/jira/browse/AMBARI-19929​


The fix will prevent the inconsistency but meanwhile you need to delete = some rows manually.


If you are ok, can you open an Apache Ambari JIRA with the log file as a= ttachment. Someone will be able to add instructions for cleaning up th= e DB. That way it remains searchable for others.


thanks

Sumit

From: Anandha L Ranganathan= <analog.sony@gmail.com>
Sent: Friday, August 11, 2017 1:29 PM
To: dev@ambari.apache.org
Cc: user@ambari.apache.org
Subject: Re: Ambari upgrade 2.5.1.0 issue - database consistency iss= ues for topology
 
Sumit,

Please find the attached database-check  logs.

On Fri, Aug 11, 2017 at 12:57 PM, Sumit Mohanty = <smohanty@= hortonworks.com> wrote:
Anandha, can you share the content of /var/log/ambari-server/ambari-se= rver-check-database.log

thanks
Sumit
________________________________
From: Anandha L Ranganathan <an= alog.sony@gmail.com>
Sent: Friday, August 11, 2017 11:57 AM
To: user@ambari.apache.org; <= a href=3D"mailto:dev@ambari.apache.org"> dev@ambari.apache.org
Subject: Ambari upgrade 2.5.1.0 issue - database consistency issues for top= ology


I am trying to upgrade from ambari-2.2.1 to ambari-2.5.1. During upgrade it= didn't throw any error and it completed successfully.

  1.  INFO: Updating Ambari Server properties in ambari.pr= operties ...
  2.  INFO: Updating Ambari Server properties in ambari-env.sh ..= .
  3.  WARNING: Original file ambari-env.sh kept
  4.  INFO: Fixing database objects owner
  5.  Ambari Server configured for Embedded Postgres. Confirm you= have made a backup of the Ambari Server database [y/n] (y)? y
  6.  INFO: Upgrading database schema
  7.  INFO: Return code from schema upgrade command, retcode =3D = 0
  8.  INFO: Schema upgrade completed
  9.  Adjusting ambari-server permissions and ownership...
  10. Ambari Server 'upgrade' completed successfully.
  11.
  12.

After upgrade , I restarted the ambari-server and it throws this error.

  1.  [root@usw2dxdpmn02 yum.repos.d]# ambari-server resta= rt
  2.  Using python  /usr/bin/python
  3.  Restarting ambari-server
  4.  Waiting for server stop...
  5.  Ambari Server stopped
  6.  Ambari Server running with administrator privileges.
  7.  Organizing resource files at /var/lib/ambari-server/re= sources...
  8.  Ambari database consistency check started...
  9.  Server PID at: /var/run/ambari-server/ambari-server.pi= d
  10. Server out at: /var/log/ambari-server/ambari-server.out
  11. Server log at: /var/log/ambari-server/ambari-server.log
  12. Waiting for server start........................
  13. DB configs consistency check failed. Run "ambari-server sta= rt --skip-database-check" to skip. You may try --auto-fix-database fla= g to attempt to fix issues automatically. If you use this "--skip-data= base-check" option, do not make any changes to your cluster topology or perform a cluster upgrade until you correct the databa= se consistency issues. See /var/log/ambari-server/ambari-server-check-= database.log for more details on the consistency issues.
  14. ERROR: Exiting with exit code -1.
  15. REASON: Ambari Server java process has stopped. Please check the= logs for more information.
  16.
  17.
  18.

I am able to restart ambari-server with --skip-database-check. What is the = reason for this error and how do I fix it?


--_000_150254766626169778hortonworkscom_--