metron-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Lyle <dlyle65...@gmail.com>
Subject Re: errors
Date Thu, 14 Jul 2016 11:54:14 GMT
Hi Tejaswi.

It looks to me like you're have a series of issues working against you.

1) The current error- that's a likely result of elasticsearch not being up
when the Ansible deployment script is checking the index status. That's
probably caused by:
2) You're running on the Sandbox. It looks like you're installing HDP on
top of HDP in the sandbox. There's no room for the services to run, they'll
likely keep crashing. That's probably a result of:
3) You're running on Windows. We don't currently have a good way of doing
that.

I don't have time to fully test it out, but you may be able to get away
with something like the following:

1) Stand up a CentOS 6.x based VM and make sure it is DNS addressable from
your host.
2) Follow the procedure here:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65144361
*    EXCEPT - *use the following ansible-playbook command instead of the
one in the wiki to install HDP and Metron:
     ansible-playbook -i
/root/incubator-metron/metron-deployment/inventory/$INSTALL_CONF_DIRECTORY
metron_full_install.yml --skip-tags="solr" -u *ssh_user* -k
     where: *ssh_user *is a user you've set up on your vm that has sudo. It
will prompt you for a password, that will be the password for the
*ssh_user* you
set up on your vm.

Because you're using Windows, you're a bit of a test pilot, so thanks for
taking that on, having a working Windows version of the deployment will be
really helpful down the road. I'm looking forward to seeing your progress.

Thanks!

-D...



On Wed, Jul 13, 2016 at 5:43 PM, Tejaswi Palacharla <
Tejaswi.Palacharla@sstech.us> wrote:

> I am using ansible 2.0.0.2 only.
>
>
>
>
>
> Can u please help.
>
>
>
> *From:* Nick Allen [mailto:nick@nickallen.org]
> *Sent:* Wednesday, July 13, 2016 4:35 PM
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> You are probably using a version of Ansible that does not work with
> Metron.  You need to use Ansible 2.0.0.2.
>
>
>
> On Wed, Jul 13, 2016 at 5:06 PM, Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> Can u please check this error and I have followed the steps from
> https://github.com/apache/incubator-metron/tree/master/metron-deployment/vagrant/full-dev-platform
> .
>
> I am not able to figure out what is going wrong.
>
> Please help
>
>
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Wednesday, July 13, 2016 10:43 AM
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> Did you happen to read the error message?  I'm not sure I'm going to be
> able to provide more detail than what the error message does.
>
>
>
> Jon
>
>
>
> On Wed, Jul 13, 2016 at 11:40 AM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> Is it visible now. How to solve the issue?
>
>
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Wednesday, July 13, 2016 10:33 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> That is unreadable for me.  Can you send the text?
>
>
>
> Jon
>
>
>
> On Wed, Jul 13, 2016 at 10:39 AM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> After running vagrant up –provision I am not able to connect to ambary and
> I get the following error.
>
> I am not able to solve the issue and can you please check it and explain
> me what to do next.
>
>
>
> *From:* Tejaswi Palacharla
> *Sent:* Tuesday, July 12, 2016 1:49 PM
> *To:* 'user@metron.incubator.apache.org' <user@metron.incubator.apache.org
> >
> *Subject:* RE: errors
>
>
>
> Done with vagrant up now after going into vagrant ssh I get vagrant@node1
>
> What steps should I follow after that?
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com <zeolla@gmail.com>]
>
> *Sent:* Tuesday, July 12, 2016 12:59 PM
> *To:*
>
> user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> Hmm, not sure.  My first thought would be to
> increase config.vm.boot_timeout like it mentions to some high number.  If
> it still hits it, then it may be worth further investigation.  It may be
> that the VM you provisioned is just very small/slow.
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 1:15 PM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
>
>
>
>
> This is the error
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 12:07 PM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> Can you please provide the text?  That resolution is tough for me to read.
>
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 12:53 PM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> I have got this error if I use this commands.  Wat to do next?
>
>
>
>
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
>
> *Sent:* Tuesday, July 12, 2016 11:35 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> Looks much better now.  Try a vagrant halt then vagrant up.
>
>
>
> On Tue, Jul 12, 2016, 12:27 Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> I made the changes and it shows a different error.  Can u check it once?
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
>
> *Sent:* Tuesday, July 12, 2016 11:07 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> I haven't used workstation in a while but I think it is a setting on your
> VM under processor.  Here's a link to how to do it on workstation 8 -
> http://vmwaremine.com/2012/02/03/enable-hardware-virtualization-in-vmware-workstation-8/
>
>
>
> On Tue, Jul 12, 2016 at 12:03 PM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> Vmware workstation 12. Can u give me the steps if possible?
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 10:57 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> If your sandbox machine is a VM, then you need to configure VM nesting at
> the hypervisor level before it will be available within the guest (even
> within the BIOS).  What virtualization product are you using to run your
> sandbox (KVM, VMWare, VirtualBox, etc.)?
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 11:52 AM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> I tried going into bios and changing but virtualization is not present.
>
>
>
> Can u explain me what to do?
>
> Or there any other methods other than this?
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 10:41 AM
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> It looks like you're trying to run the full-dev-platform from within a
> VM.  To do this, you need to configure VM nesting (i.e. you need to enable
> the x86 virtualization commands on your sandbox machine).  For how to do
> this with VMWare see https://communities.vmware.com/docs/DOC-8970, for
> more general details regarding x86 virtualization see
> https://en.wikipedia.org/wiki/X86_virtualization.
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 11:35 AM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> Tried to install everything on Horton work sandbox.
>
> Installed ansible, python, vagrant, vbox.
>
> When giving vagrant up we get the following error.
>
>
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
>
>
>
>
> --
>
> Nick Allen <nick@nickallen.org>
>

Mime
View raw message