metron-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Allen <n...@nickallen.org>
Subject Re: errors
Date Wed, 13 Jul 2016 21:35:13 GMT
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?
>
>
>
> [image: cid:image001.png@01D1DCF2.1EC10E60]
>
>
>
> *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