Hi Pierre-

I ran the first line:
sudo apt-get ...

Then reran the sandbox.sh script and it looks like I'm past the task that 
was crashing. But the provisioning hasn't finished, so I'm not home free 
yet. 

I wouldn't think those two upgrade commands for numpy and scipy would do 
anything. Those are upgrading the OS versions of the packages, while the 
Ansible task was installing numpy and scipy into venvs in 
/edx/app/edxapp/venvs/*

For my deployment, the versions installed in the venvs (edxapp and 
edxapp-sandbox) are:
scipy==0.14.0
numpy==1.6.2

Regardless, something in that apt-get command fixed my situation. 

Thanks for your help!

On Tuesday, August 2, 2016 at 2:04:49 PM UTC-4, Pierre Mailhot wrote:
>
> TJ, that fixed it for me.
>
> Ned, you may want to consider upgrading numpy and scipy as part of the 
> upgrade from Dogwood to Eucalyptus.
> My quick fix installed numpy-1.11.1 and scipy-0.18.0.
>
> On Tuesday, August 2, 2016 at 1:24:13 PM UTC-4, Pierre Mailhot wrote:
>>
>> Hey TJ,
>>
>> I have tried a second time and got the same error.
>>
>> So since it looked like a numpy / scipy issue, I decided to try another 
>> route.
>>
>> I tried this base on what I found on 
>> http://stackoverflow.com/questions/19693302/numpy-install-under-ubuntu-12-04-causes-python-importerror
>>
>> sudo apt-get install python-numpy python-scipy libblas-dev liblapack-dev 
>> gfortran python-dev
>> sudo pip install numpy --upgrade
>> sudo pip install scipy --upgrade
>>
>>
>> I then restarted the installation script. It takes a long time to install 
>> on the m3.large instance I am using right now, but I will be updating you 
>> soon if it works or not...
>>
>> On Monday, August 1, 2016 at 4:11:21 PM UTC-4, TJ Keemon wrote:
>>>
>>> Hey Pierre-
>>>
>>> I think we're working through the same problem as you, but we attempted 
>>> to install on GCloud. Here's the full error that we saw:
>>> https://gist.github.com/tkeemon/868f320dc94a4ed825aee84047c0501f
>>>
>>> Ned-
>>>
>>> Do you want us to keep this discussion here or should we spin it off 
>>> into another thread? 
>>>
>>> -TJ
>>>
>>> On Thursday, July 28, 2016 at 3:41:27 PM UTC-4, Pierre Mailhot wrote:
>>>>
>>>> In order to check if the problems I encountered after the upgrade are 
>>>> with the rebase of my branch/fork or general to 
>>>> *open-release/eucalyptus/1rc1* , I tried installing a fresh copy on a 
>>>> new ubuntu 12.04 EC2 instance using the instructions from 
>>>> https://openedx.atlassian.net/wiki/display/OpenOPS/Native+Open+edX+Ubuntu+12.04+64+bit+Installation
>>>>
>>>> Let's jusy say it complained heavily when it reached the following task:
>>>>
>>>> TASK: [edxapp | code sandbox | Install sandbox requirements into 
>>>> sandbox venv] *** 
>>>>
>>>>
>>>> Looks like atlas, numpy and scipy problems. I haven't encountered those 
>>>> in a while...
>>>>
>>>> On Friday, July 22, 2016 at 6:27:28 PM UTC-4, Ned Batchelder wrote:
>>>>>
>>>>> Hello Open edX adopters,
>>>>>
>>>>> The next Open edX release will be Eucalyptus. We have a prerelease 
>>>>> available now for limited use. Eucalyptus 1 RC 1 is the first release 
>>>>> candidate of the first Eucalyptus release (we've changed the numbering 
>>>>> scheme slightly since Dogwood).
>>>>>
>>>>> This prerelease is only available for fullstack and native installs.  
>>>>> Devstack is not yet supported.  An overview of the installation options 
>>>>> is 
>>>>> here: 
>>>>> https://openedx.atlassian.net/wiki/display/OpenOPS/Open+edX+Installation+Options
>>>>>
>>>>> If you want to try this pre-release, please do not do it on a live 
>>>>> machine, or risk live data with it.  The OPENEDX_RELEASE tag name to use 
>>>>> is 
>>>>> *open-release/eucalyptus/1rc1* .  If you want to upgrade from a 
>>>>> previous install, the existing instructions work, but the migrate.sh 
>>>>> script 
>>>>> has been renamed to upgrade.sh to better match its function.
>>>>>
>>>>> Before we release a real Eucalyptus, we will be adding a few more 
>>>>> fixes, and want to hear from you if you discover problems with this 
>>>>> pre-release.  We even want to hear if you don't encounter problems! :)
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --Ned.
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/09ece890-ca0b-46b0-8019-780c0ef23325%40googlegroups.com.

Reply via email to