Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
References: <BMXPR01MB0870B277E7BEC9109A04AB3DEB3D0@BMXPR01MB0870.INDPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <BMXPR01MB0870B277E7BEC9109A04AB3DEB3D0@BMXPR01MB0870.INDPRD01.PROD.OUTLOOK.COM>
From: Kyle Dunn <kdunn@pivotal.io>
Date: Tue, 21 Mar 2017 15:24:15 +0000
Message-ID: <CADvk=GaLOXg3+6Xd6w9RrQZwWq=X=a=bE22sx6kB-pKxpc-PrQ@mail.gmail.com>
Subject: Re: Issue : hawq init cluster
To: dev@hawq.incubator.apache.org, ketan_kunde@persistent.com
Content-Type: multipart/alternative; boundary=94eb2c1120c03a45ee054b3f3d45
archived-at: Tue, 21 Mar 2017 15:24:31 -0000

--94eb2c1120c03a45ee054b3f3d45
Content-Type: text/plain; charset=UTF-8

Re-sending to Ketan + dev list.

Hi *Ketan* -

Usually when I've encountered this issue it was one (or a combination) of
the following:

- residual "postgres" processes from a previous initdb attempt
- non-empty /data/hawq_{default,data}/ directory
- non-empty /data/hawq/{master,segment} directories

Usually a "pkill -11 -f silent" will take care of the first, the others are
handled by just emptying those directories and ru-running init.


-Kyle

On Tue, Mar 21, 2017 at 12:27 AM Ketan Kunde <ketan_kunde@persistent.com>
wrote:

> Hi ,
>
> I have built hawq on rhel 7.1 platform with s390x processor.
> I have tested hdfs to work fine before initializing hawq.
> I have also verified my ssh connection by sshing to the localhost.
>
> When is start initializing  hawq I get the below error.
>
>
> 20170321:01:57:54:087176 hawq_init:ecos0013:ketan-[ERROR]:-sync
> hawq-site.xml failed.
> 20170321:01:57:54:087176 hawq_init:ecos0013:ketan-[ERROR]:-Set
> default_hash_table_bucket_number failed
>
> Some inputs , pointers to resolve the above would be very helpful.
>
> Regards
> Ketan Kunde
>
>
>
>
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which is
> the property of Persistent Systems Ltd. It is intended only for the use of
> the individual or entity to which it is addressed. If you are not the
> intended recipient, you are not authorized to read, retain, copy, print,
> distribute or use this message. If you have received this communication in
> error, please notify the sender and delete all copies of this message.
> Persistent Systems Ltd. does not accept any liability for virus infected
> mails.
>
> --
*Kyle Dunn | Data Engineering | Pivotal*
Direct: 303.905.3171 <3039053171> | Email: kdunn@pivotal.io

--94eb2c1120c03a45ee054b3f3d45--