You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by BW <we...@apache.org> on 2015/04/21 01:04:08 UTC

RADix Vagrant provisioning

Hey Rishi, had the following below problems on RADix Vagrant provisioning:

The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
things got better; ended up with errors in section 2 below.  (Also, suggest
adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
provision.sh where the tar occurs)

1. *******************************
==> oodt_radix_vm: tar (child):
==> oodt_radix_vm:
distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
Cannot open
==> oodt_radix_vm: : No such file or directory
==> oodt_radix_vm: tar (child):
==> oodt_radix_vm: Error is not recoverable: exiting now
==> oodt_radix_vm: tar:
==> oodt_radix_vm: Child returned status 2
==> oodt_radix_vm: tar:
==> oodt_radix_vm: Error is not recoverable: exiting now
==> oodt_radix_vm: /tmp/vagrant-shell: line 67: cd: /usr/local/oodt/bin: No
such file or directory
==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
directory
********************************
2.

*==> oodt_radix_vm: tar: option requires an argument -- 'C'*

*==> oodt_radix_vm: Try `tar --help' or `tar --usage' for more information.*

*==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
directory*


*-Thanks*

*BW*

Re: RADix Vagrant provisioning

Posted by BW <bw...@mysoftcloud.com>.
No mysoftcloud... created, will get back with more log data.

On Tuesday, April 21, 2015, Verma, Rishi (398M) <Ri...@jpl.nasa.gov>
wrote:

> Hi BW,
>
> That’s should be consistent with my thinking below. The OODT build failed,
> the tar didn’t get created, and the tar extraction step you documented
> below didn’t work.
>
> My question is, why did the OODT build (which creates the tar) fail. Need
> to see the log output to determine (after you manually run “mvn clean
> package”, following my steps below).
>
> Rishi
>
> On Apr 20, 2015, at 6:41 PM, BW <webb@apache.org <javascript:;>> wrote:
>
> > It's not getting far enough to do the tar.
> >
> > On Monday, April 20, 2015, Verma, Rishi (398M) <Rishi.Verma@jpl.nasa.gov
> <javascript:;>>
> > wrote:
> >
> >> Hi BW,
> >>
> >> Looks like the OODT build process within the VM didn’t succeed (i.e.
> >> failed on line 63 within
> >>
> https://github.com/apache/oodt/blob/trunk/vagrant/radix/vagrant/provision.sh
> >> )
> >>
> >> Would you mind logging into the VM and building your mysoftcloud-myoodt
> >> project manually and sharing the error?
> >>
> >> i.e.
> >> $ vagrant ssh
> >> $ cd /usr/local/src/mysoftcloud-myoodt
> >> $ mvn clean package
> >>
> >> Rishi
> >>
> >> On Apr 20, 2015, at 4:04 PM, BW <webb@apache.org <javascript:;>
> <javascript:;>> wrote:
> >>
> >>> Hey Rishi, had the following below problems on RADix Vagrant
> >> provisioning:
> >>>
> >>> The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
> >>> things got better; ended up with errors in section 2 below.  (Also,
> >> suggest
> >>> adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
> >>> provision.sh where the tar occurs)
> >>>
> >>> 1. *******************************
> >>> ==> oodt_radix_vm: tar (child):
> >>> ==> oodt_radix_vm:
> >>>
> >>
> distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
> >>> Cannot open
> >>> ==> oodt_radix_vm: : No such file or directory
> >>> ==> oodt_radix_vm: tar (child):
> >>> ==> oodt_radix_vm: Error is not recoverable: exiting now
> >>> ==> oodt_radix_vm: tar:
> >>> ==> oodt_radix_vm: Child returned status 2
> >>> ==> oodt_radix_vm: tar:
> >>> ==> oodt_radix_vm: Error is not recoverable: exiting now
> >>> ==> oodt_radix_vm: /tmp/vagrant-shell: line 67: cd:
> /usr/local/oodt/bin:
> >> No
> >>> such file or directory
> >>> ==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
> >>> directory
> >>> ********************************
> >>> 2.
> >>>
> >>> *==> oodt_radix_vm: tar: option requires an argument -- 'C'*
> >>>
> >>> *==> oodt_radix_vm: Try `tar --help' or `tar --usage' for more
> >> information.*
> >>>
> >>> *==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file
> or
> >>> directory*
> >>>
> >>>
> >>> *-Thanks*
> >>>
> >>> *BW*
> >>
> >> ---
> >> Rishi Verma
> >> NASA Jet Propulsion Laboratory
> >> California Institute of Technology
> >>
> >>
>
> ---
> Rishi Verma
> NASA Jet Propulsion Laboratory
> California Institute of Technology
>
>

Re: RADix Vagrant provisioning

Posted by "Verma, Rishi (398M)" <Ri...@jpl.nasa.gov>.
Hi BW,

That’s should be consistent with my thinking below. The OODT build failed, the tar didn’t get created, and the tar extraction step you documented below didn’t work.

My question is, why did the OODT build (which creates the tar) fail. Need to see the log output to determine (after you manually run “mvn clean package”, following my steps below).

Rishi

On Apr 20, 2015, at 6:41 PM, BW <we...@apache.org> wrote:

> It's not getting far enough to do the tar.
> 
> On Monday, April 20, 2015, Verma, Rishi (398M) <Ri...@jpl.nasa.gov>
> wrote:
> 
>> Hi BW,
>> 
>> Looks like the OODT build process within the VM didn’t succeed (i.e.
>> failed on line 63 within
>> https://github.com/apache/oodt/blob/trunk/vagrant/radix/vagrant/provision.sh
>> )
>> 
>> Would you mind logging into the VM and building your mysoftcloud-myoodt
>> project manually and sharing the error?
>> 
>> i.e.
>> $ vagrant ssh
>> $ cd /usr/local/src/mysoftcloud-myoodt
>> $ mvn clean package
>> 
>> Rishi
>> 
>> On Apr 20, 2015, at 4:04 PM, BW <webb@apache.org <javascript:;>> wrote:
>> 
>>> Hey Rishi, had the following below problems on RADix Vagrant
>> provisioning:
>>> 
>>> The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
>>> things got better; ended up with errors in section 2 below.  (Also,
>> suggest
>>> adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
>>> provision.sh where the tar occurs)
>>> 
>>> 1. *******************************
>>> ==> oodt_radix_vm: tar (child):
>>> ==> oodt_radix_vm:
>>> 
>> distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
>>> Cannot open
>>> ==> oodt_radix_vm: : No such file or directory
>>> ==> oodt_radix_vm: tar (child):
>>> ==> oodt_radix_vm: Error is not recoverable: exiting now
>>> ==> oodt_radix_vm: tar:
>>> ==> oodt_radix_vm: Child returned status 2
>>> ==> oodt_radix_vm: tar:
>>> ==> oodt_radix_vm: Error is not recoverable: exiting now
>>> ==> oodt_radix_vm: /tmp/vagrant-shell: line 67: cd: /usr/local/oodt/bin:
>> No
>>> such file or directory
>>> ==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
>>> directory
>>> ********************************
>>> 2.
>>> 
>>> *==> oodt_radix_vm: tar: option requires an argument -- 'C'*
>>> 
>>> *==> oodt_radix_vm: Try `tar --help' or `tar --usage' for more
>> information.*
>>> 
>>> *==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
>>> directory*
>>> 
>>> 
>>> *-Thanks*
>>> 
>>> *BW*
>> 
>> ---
>> Rishi Verma
>> NASA Jet Propulsion Laboratory
>> California Institute of Technology
>> 
>> 

---
Rishi Verma
NASA Jet Propulsion Laboratory
California Institute of Technology


Re: RADix Vagrant provisioning

Posted by BW <we...@apache.org>.
It's not getting far enough to do the tar.

On Monday, April 20, 2015, Verma, Rishi (398M) <Ri...@jpl.nasa.gov>
wrote:

> Hi BW,
>
> Looks like the OODT build process within the VM didn’t succeed (i.e.
> failed on line 63 within
> https://github.com/apache/oodt/blob/trunk/vagrant/radix/vagrant/provision.sh
> )
>
> Would you mind logging into the VM and building your mysoftcloud-myoodt
> project manually and sharing the error?
>
> i.e.
> $ vagrant ssh
> $ cd /usr/local/src/mysoftcloud-myoodt
> $ mvn clean package
>
> Rishi
>
> On Apr 20, 2015, at 4:04 PM, BW <webb@apache.org <javascript:;>> wrote:
>
> > Hey Rishi, had the following below problems on RADix Vagrant
> provisioning:
> >
> > The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
> > things got better; ended up with errors in section 2 below.  (Also,
> suggest
> > adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
> > provision.sh where the tar occurs)
> >
> > 1. *******************************
> > ==> oodt_radix_vm: tar (child):
> > ==> oodt_radix_vm:
> >
> distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
> > Cannot open
> > ==> oodt_radix_vm: : No such file or directory
> > ==> oodt_radix_vm: tar (child):
> > ==> oodt_radix_vm: Error is not recoverable: exiting now
> > ==> oodt_radix_vm: tar:
> > ==> oodt_radix_vm: Child returned status 2
> > ==> oodt_radix_vm: tar:
> > ==> oodt_radix_vm: Error is not recoverable: exiting now
> > ==> oodt_radix_vm: /tmp/vagrant-shell: line 67: cd: /usr/local/oodt/bin:
> No
> > such file or directory
> > ==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
> > directory
> > ********************************
> > 2.
> >
> > *==> oodt_radix_vm: tar: option requires an argument -- 'C'*
> >
> > *==> oodt_radix_vm: Try `tar --help' or `tar --usage' for more
> information.*
> >
> > *==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
> > directory*
> >
> >
> > *-Thanks*
> >
> > *BW*
>
> ---
> Rishi Verma
> NASA Jet Propulsion Laboratory
> California Institute of Technology
>
>

Re: RADix Vagrant provisioning

Posted by "Verma, Rishi (398M)" <Ri...@jpl.nasa.gov>.
Hi BW,

Looks like the OODT build process within the VM didn’t succeed (i.e. failed on line 63 within https://github.com/apache/oodt/blob/trunk/vagrant/radix/vagrant/provision.sh)

Would you mind logging into the VM and building your mysoftcloud-myoodt project manually and sharing the error?

i.e.
$ vagrant ssh
$ cd /usr/local/src/mysoftcloud-myoodt
$ mvn clean package

Rishi

On Apr 20, 2015, at 4:04 PM, BW <we...@apache.org> wrote:

> Hey Rishi, had the following below problems on RADix Vagrant provisioning:
> 
> The git clone I just pulled had 0.7-SNAPSHOT; I changed it to 0.8.1 and
> things got better; ended up with errors in section 2 below.  (Also, suggest
> adding PRODUCT_ARTIFACT_ID_VERSION to env.sh and using it in the
> provision.sh where the tar occurs)
> 
> 1. *******************************
> ==> oodt_radix_vm: tar (child):
> ==> oodt_radix_vm:
> distribution/target/mysoftcloud-myoodt-distribution-1.0-bin.tar.gz-distribution-*-bin.tar.gz:
> Cannot open
> ==> oodt_radix_vm: : No such file or directory
> ==> oodt_radix_vm: tar (child):
> ==> oodt_radix_vm: Error is not recoverable: exiting now
> ==> oodt_radix_vm: tar:
> ==> oodt_radix_vm: Child returned status 2
> ==> oodt_radix_vm: tar:
> ==> oodt_radix_vm: Error is not recoverable: exiting now
> ==> oodt_radix_vm: /tmp/vagrant-shell: line 67: cd: /usr/local/oodt/bin: No
> such file or directory
> ==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
> directory
> ********************************
> 2.
> 
> *==> oodt_radix_vm: tar: option requires an argument -- 'C'*
> 
> *==> oodt_radix_vm: Try `tar --help' or `tar --usage' for more information.*
> 
> *==> oodt_radix_vm: /tmp/vagrant-shell: line 68: ./oodt: No such file or
> directory*
> 
> 
> *-Thanks*
> 
> *BW*

---
Rishi Verma
NASA Jet Propulsion Laboratory
California Institute of Technology