When I activate the openmdao virtualenv in a qsub session, it appears to only activate on one of my nodes. What could account for this strange behavior? Why are processors on non-primary nodes unable to load the virtualenv?

$ qsub -V -I -l nodes=2:ppn=24

$ cd openmdao-0.10.3.2/

$ . bin/activate

$ mpirun -np 24 python -c "import openmdao"

# no errors

$ mpirun -np 30 python -c "import openmdao"

Traceback (most recent call last):

  File "<string>", line 1, in <module>

Traceback (most recent call last):

  File "<string>", line 1, in <module>

Traceback (most recent call last):

  File "<string>", line 1, in <module>

Traceback (most recent call last):

  File "<string>", line 1, in <module>

Traceback (most recent call last):

  File "<string>", line 1, in <module>

Traceback (most recent call last):

  File "<string>", line 1, in <module>

ImportError: No module named openmdao

ImportError: No module named openmdao

ImportError: No module named openmdao

ImportError: No module named openmdao

ImportError: No module named openmdao

ImportError: No module named openmdao

-------------------------------------------------------

Primary job  terminated normally, but 1 process returned

a non-zero exit code.. Per user-direction, the job has been aborted.

-------------------------------------------------------

--------------------------------------------------------------------------

mpirun detected that one or more processes exited with non-zero status, thus causing

the job to be terminated. The first process to do so was:

  Process name: [[44999,1],28]

  Exit code:    1

--------------------------------------------------------------------------

asked 26 Feb '16, 17:34

kilojoules's gravatar image

kilojoules
31112

edited 26 Feb '16, 17:36


We're not actively supporting 0.13 anymore. This isn't something we can support strongly at the moment. We have developed a robust HPC capability in version 1.5.x though, i highly suggest that you begin to migrate over to that.

However, this sounds like a virtual env problem. are you able to create any other virtualenv's and have it work that way? It could also be related to a path problem, if you need to have it source a .bashrc file before activating the virtual env for some reason.

link

answered 26 Feb '16, 17:45

admin's gravatar image

admin ♦♦
203413

edited 26 Feb '16, 17:45

To those who come across this problem - the trick is to activate openmdao THEN start qsub, then again activate openmdao within qsub

link

answered 22 Mar '16, 13:57

kilojoules's gravatar image

kilojoules
31112

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×5
×4
×2

Asked: 26 Feb '16, 17:34

Seen: 1,252 times

Last updated: 22 Mar '16, 13:57

powered by OSQA