Closed andre-merzky closed 10 years ago
Andre - @drelu will definitely have a better answer than me, but as you already probably know, the bootstrap is failing.
My only question was - are you trying to bootstrap (i.e. is the target) a non-traditional resource?
If it is your localhost (and you need to get up and running before AL has a chance to look at this), put your BigJob executable in the virtualenv $HOME/.bigjob/python instead of $HOME/.bigjob. BigJob only tries to bootstrap itself onto resources where it does not detect a bigjob in $HOME/.bigjob/python. I don't know if this is entirely making sense. What I am trying to say is instead of:
virtualenv $HOME/.bigjob source $HOME/.bigjob/bin/activate
you say: virtualenv $HOME/.bigjob/python source $HOME/.bigjob/python/bin/activate
In the meantime, I will have a look at the bootstrap script. Also, if you're submitting to a different target host, then my previous comments are irrelevant. Also I am not trying to comment on the "correctness" of things, I am just providing a viable workaround for the localhost scenario.
Melissa, thanks for the quick reply!
I indeed try on localhost at the moment -- thus a very traditional resource ;)
I am not sure I understood your workaround though, I'm afraid. I am nowhere doing source $HOME/.bigjob/bin/activate
-- so not sure where to replace that. A virtualenv in $HOME/.bigjob/python
seems to exist, and can be sourced -- but I am using a different VE for my stuff. So, do I need to source this one? Also, what do you mean with put your BigJob executable in the virtualenv $HOME/.bigjob/python instead of $HOME/.bigjob
-- the only other thing in $HOME/.bigjob
, besides python/
, is bigjob-bootstrap.py
-- is that what you mean?
Thanks!
Best, Andre.
Hi Andre, The bootstrap script 1. attempts to use BigJob in your PYTHONPATH, if not found then in 2. $HOME/.bigjob/python and if not found there it is attempting to download it via the bootstrap script, which seems to fail here:
python bigjob-bootstrap.py <$PATH>
In your system level Python, what version of setuptools, distribute and virtualenv do you have?
Thanks,
Andre
On Wed, Nov 20, 2013 at 1:59 AM, Andre Merzky notifications@github.comwrote:
Melissa, thanks for the quick reply!
I indeed try on localhost at the moment -- thus a very traditional resource ;)
I am not sure I understood your workaround though, I'm afraid. I am nowhere doing source $HOME/.bigjob/bin/activate -- so not sure where to replace that. A virtualenv in $HOME/.bigjob/python seems to exist, and can be sourced -- but I am using a different VE for my stuff. So, do I need to source this one? Also, what do you mean with put your BigJob executable in the virtualenv $HOME/.bigjob/python instead of $HOME/.bigjob-- the only other thing in $HOME/.bigjob, besides python/, is bigjob-bootstrap.py -- is that what you mean?
Thanks!
Best, Andre.
— Reply to this email directly or view it on GitHubhttps://github.com/saga-project/BigJob/issues/164#issuecomment-28867556 .
Thanks! :)
On agent startup, I see in the error log:
What does it mean? What can I do about it?
Thanks, Andre.