hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Radar Da lei <r...@pivotal.io>
Subject Re: Issue : hawq init cluster
Date Wed, 22 Mar 2017 02:37:51 GMT
Hi Ketan,

>From the log, seems like a failure of 'hawq scp' command or a 'scp'
command. Please make sure you have set password-less ssh, you can verify it
by run a simple scp command between your nodes without input any password.


Regards,
Radar

On Tue, Mar 21, 2017 at 11:24 PM, Kyle Dunn <kdunn@pivotal.io> wrote:

> 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message